Due to the limited capabilities of the ActionScript 3 reflection API than cannot access private fields, it is necessary to create
an externalizable AS3 class (implementing flash.utils.IExternalizable and its corresponding externalizable Java class
writeExternal
In both classes you have to implement two methods
the Gas3 generator can automatically generate the writeExternal and readExternal methods.
With GraniteDS automated externalization and without any modification made to our bean, we may serialize all properties of the Person class,
private or not
In order to externalize the Person.java entity bean, we must tell GraniteDS which classes we want to externalize
with a
externalize all classes named com.myapp.entity.Person by using the org.granite.hibernate.HibernateExternalizer
you could use this declaration, but note that type in the example above
is replaced by
Tide will automatically inject shared data and correctly route events without requiring the application developer to write their own mechanism for sharing information or explicitly registering event listeners
Tide events are a simplification on the already existing Flex event framework
GraniteDS provides out-of-the-box integration with Seam 2.2 via either the RemoteObject API or the Tide API
to remotely call Seam components, and fully supports serialization of JPA entities from and to your Flex application, taking care of lazily loaded associations
allows me to switch between different endpoints - different test or production servers for instance - just by specifying the ip and port in an external properties file
don't have to specify any compiler arguments that point to the services-config.xml or messaging-config.xml files.