Also, the log output is sent to the console by default. If you want to direct it to a file, you can use the servlet log  target instead of the console target. That will direct the log messages to your app server's log. The setting would look like this in the logging section of services-config.xml:<t...

I think you will get more response if you repost your question on the LiveCycle Designer forum. This forum is specific to LiveCycle Data Services:http://http://www.adobe.com/products/livecycle/dataservices/

Can you provide some more information about your application? For example:- For you remote SWF, did you move the SWF to a web server on a  different domain than the LCDS server to which you are communicating?If this is the case, you would need a crossdomain.xml file at the root of the domain that yo...

There are specific versions of theModeler plugins for LiveCycle Data Services 3.1 for Eclipse 3.4 and 3.5, as the download links indicate. A released version of Eclipse 3.6 was not available when these Modeler plugins were developed and released. The next releases of the Modeler and Flash Builder, c...

You could load that info from an XML file as described below. I took this from the doc.To further externalize configuration, you can pass the endpoint URL value to the client at runtime. One way to do this is by reading a configuration file with an HTTPService component at application startup. The c...

Good question. You do still need to have an endpoint configured on the server in the services-config.xml file:"When you create and assign a channel set on the client, the client requires the correct channel type and endpoint URL to contact the server. The client does not specify the endpoint class t...

You do need to configure a channel set, but you have the option of doing that in your Flex client code rather than in the services-config.xml file. Here's some information on some ways to do that:http://help.adobe.com/en_US/LiveCycleDataServicesES/3.1/Developing/WSc3ff6d0ea77859461172e0811f00f6e876-...

What aspects of LiveCycle Data Services are you using? Sounds like you are dealing with Flex SDK and Flash Builder or possible a different LiveCycle product (not LiveCycle Data Services). This forum is specific to LiveCycle Data Services.

Please provide more details about your application code and what you are trying to do.

With BlazeDS, you essentially get the Message Service, the Remoting Service, and Proxy Service: The Message Service is for publish/subscribe messaging and for pushing messages from the server to clients.The Remoting Service is for calling methods on Java objects in your web app classpath from a Flex...