are you aware that you can use relative URL’s for the endpoints, too? The URL is resolved relative to the url where the Flex file was loaded from. This solves the “my flex file moved to another server” problem, without any extra complexity.

Of course, this only works if the file is access from the server.

Regards,

Allard

Problem solved! Define and initialize an unique static ChannelSet and apply it to all created remote objects.

I guess ChannelSet (or AMFChannel) is a limited System resource. So you can’t open a lot of channels simultaneously. But you can reuse the same channel for all remote objects.

That is based on my experience. I can’t justify that.

Thanks a lot Christopher!

It seems to work, but the code really doesn’t works when you open several channels at the same time. You will get a lot of “Channel disconnected” exceptions.

I think the ideas exposed here are very very useful and very they are well explained. Thanks a lot. Though users could have problems if they use your code without any correction.

Pablo.

For people who wants to use server configuration (I mean channels, endpoints and remoting destinations from BlazeDs/LCDS services-config.xml and remoting-config.xml) loaded in runtime instead of common practice with reading configs in compile time Cris…

<endpoint uri="//secret

since I define the stuff in my extra service file on my server?

thanks for any tips

I have developed an application using Flex , LCDS and J2EE. The application works very well when deployed in my local system. When I deploy the application in another system, i see that the LCDS call are not happening. What might the resolution for this issue?

Thank You

I am developing an application using LCDS and J2EE.
What are the steps required to build an application.
What all do we need?

We build locally using Flexbuilder on windows, but we cant get linux to compile any services. Any ideas???