This feature adds an abstract base class that provides all of the necessary sync() and fill() functionality for every persistent class in your data model, as well as automatic index-based paging into the DataCollection for large record sets.
In your concrete class, you can add your business logic to extend the default behavior by class. Commonly customized logic includes:
There is also a base class common to all persistent classes on both client and server (a MappedSuperclass) which plug the managed objects into the data management framework on each side, and provide an identity key, and version property for optimistic locking.
Using this framework does not require any generated code, just your POJOs with standard JPA annotations, the ActionScript classes to match, and that they inherit from the base entity class called BaseObject. Two metadata tags in the ActionScript class are required: