Sorry, hit post too soon.I wouldn't get too worried about the [Managed] metadata, as the Data Model code generation will apply it in the right places.  Basically, it just allows the Data Management system to monitor the modifications (create/update/delete) to a collection or individual item in the w...

If you are using Model Driven Development, the Fiber model for this would look something like<entity name="Document" persistent="true">   <id name="id" type="long"/>   <property name="title" type="string"/>   <property name="chapters" type="Chapter[]" /></entity><entity name="Chapter" persistent="tr...

Looks like you need a MessageBroker in the FlexContext. Try calling FlexContext.setThreadLocalMessageBroker().See http://opensource.adobe.com/svn/opensource/blazeds/trunk/modules/core/src/flex/messaging/  Or rather the 3.x branch: http://opensource.adobe.com/svn/opensource/blazeds/branches/3.x/modul...

What context is your Java code being executed in? You need to be in the same web application as LCDS, so the MessageBrokerServlet will have created and registered the MessageBroker in the static table.  I assume also that you have not defined an identifier in the web.xml for the MessageBroker so the...

It turns out that LCDS 3.1 (and earlier) never calls the getItems() function defined in the Assembler interface.  Ooops, not good.This is tracked as bug 2664250 in our bug system and will be fixed in the next release of Data Services.  If you have a support contract, you can contact Adobe and refere...

Yes, item-class is required since without it the introspector has no way of telling what Java class an assembler might use.  In fact it is possible to write a single implementation of an Assembler that handles multiple types (or untyped!) objects.

Dustin,Without the ColdFusion based data management destination defined on the LCDS server, the destination will not show up in the RMI registry.  It is only the CF adapter code that does this.  The 'stock' LCDS adapter does not support invoking via RMI the way the CF version does.I would recommend ...

Please be sure that you are linking your AIR application with airfds.swc and not playerfds.swc.  This is how the library knows to use SQLite for offline storage and would be the reason why it is trying to use the LSO for storage.

Check the object coming back over the wire (turn on server side debugging) and ensure that the types are mapped correctly.  Double check your [RemoteClass(alias="xxxx")]  are correctly specified in your ActionScript value objects.Looks like you are using "corfu" which is LCDS 2.5 if I recall.  That ...

- Since what version of LCDS is this issue resolved?LCDS 3.0 and above.- Is their  a Jira issue for this?No, as we use an private bug tracking system for LCDS.- Is a patch available?No, sorry.  You would have to work through Adobe Technical support to get a hotfix for this, and I do not believe that...