I'd be very interested in tracking down this exact issue ifyou have the time to send me some code that would reproduce theissue (or at least perhaps a dump of the object graph to explainthe relationship between the collections, inner and outer, and thecustom objects).You can email it to me at pfarla...

FDS 2 shipped the following versions of apache jars in/WEB-INF/lib (you can usually find this info inside a jar in the/META-INF/MANIFEST.MF file).Apache Commons HTTPClient 3.0Apache Commons Codec 1.2Apache Commons Logging 1.0.4(The other apache jars under /WEB-INF/flex/jars are not innormal the web ...

Can you show me the code that actually calls yourRemoteObject? Do you just call send()?Also, I think your MXML for the method of your RemoteObjectshould be <mx:method name="Inventory"> as this is the name ofthe CFC function you're looking to call.

The DataServiceTransaction API is the way to go. Let me askif there is a sample of this API handy and I'll get back toyou.

Just a little more info on the destination in ColdFusion's\gateway\config\flex-messaging-gateway.cfg - this is related topushing messages from ColdFusion back to the Flex MessagingService, so it is not related to either DataServices, nor thisexample.

Have you read this article or looked at the associated code(made available as a zip file)?http://www.adobe.com/devnet/flex/articles/coldfusionflex_part1.html

There isn't a more updated release of the FDS Javadoc at thistime, however I'll log a bug for you to get these classes included.As for the actual destination level API and the methods thatshould be exposed, stay tuned - we're looking into programmaticaccess to help you out here in a future release.

How did you generate or load the data in the first place? Areyou using DataService or RemoteObject? Any idea how big this objectis in terms of bytes or numbers of members of an Array, etc? Areyou using ArrayCollection or just plain old Array? Does it make adifference if you switch between the two? I...

There is a limitation with this as mx.rpc.soap.Operation seesXML as a special case from the <mx:request> syntax thatallows for binding to an xml model from the MXML interface forWebService... as such it expects the entire operation XML thatwould be pasted inside the SOAP BODY to be included here, no...

I believe you need to purchase JRun. The version of JRun embedded in FDS is only for developmentpurposes only and is not licensed for production... it does notinclude the capability to be launched as a service byitself.