[william.drai]

Note that even if I can sound like it I'm not an Adobe salesman nor do I have any Adobe stocks :-)

[asookazian]

William Draï wrote on Dec 03, 2009 16:01:


We simply avoid LIEs in GraniteDS by using our own AMF serialization implementation that is aware of the various JPA providers internals. When our serializer detects a non loaded association (Hibernate proxy or persistent collection, EclipseLink weaved object or whatever else), it does not try to go deeper in the object graph and simply sends on the wire in AMF formats the necessary information that will allow to rebuild the proxy or association when deserializing the same object sent back from Flex. This custom serialization of JPA entities to Flex is the main reason why we started the GraniteDS project at the beginning and why we can't use BlazeDS right now because it cannot support this.

what about portability?  custom serialization sends shivers down my spine...

is there a technical demo of this?

[luxspes]

Arbi Sookazian wrote on Dec 03, 2009 18:27:


what about portability?  custom serialization sends shivers down my spine...

The serialization follows AMF, it is the standard serialization for Flash (same as in BlazeDS or in LiveCycle Data Services), so it is not custom in that regard, it is custom because in the java side it is aware of JPA entities and therefore it avoids LIEs, but from the Flex perspective it is totally standard (or at least it was last time I tried ;-) ).

is there a technical demo of this?

AFAIK you  just only need to download any of the examples for GraniteDS that integrate JPA with Flex...