history is persisted in the database
by means of a JPA entity bean and those objects are serialized back to the Flex client each time you enter a new name.
highly recommended to use JPA optimistic locking in a multi-tier environment (@Version annotation)
Tip
The easiest and recommended way for getting Tide enabled managed entities is to generate them from Java classes with Gas3 or the GDS Eclipse builder using
the tide="true" option.
In a typical Flex/app server/database application, an entity lives in three layers:
the Flex client
the Hibernate/JPA persistence context
the database
only invariant is the id.
id reliably links the different existing versions of the entity in the three layers