I don't follow that explanation much... If a Composite is referenced from an Entity, it is just dropped and ignored??
Cheers Niclas On Wed, Oct 22, 2008 at 10:09 AM, Rickard Öberg (JIRA) <[EMAIL PROTECTED]> wrote: > EntityStore should store composite references as state > ------------------------------------------------------ > > Key: QI-138 > URL: http://issues.ops4j.org/jira/browse/QI-138 > Project: Qi4j > Issue Type: Bug > Affects Versions: 0.4 > Reporter: Rickard Öberg > Assignee: Rickard Öberg > > > Currently if an Entity references a Composite an EntityStore has to use plain > serialization and deserialization to persist that data. However, since the > EntityStore by definition does not have access to the composite class outside > a UnitOfWork it cannot be guaranteed that it can deserialize it properly. > > The EntityStore contract should be changed so that if a Composite is > referenced only it's state, in the form of properties and associations, is > stored. Upon reading an EntityState from an EntityStore there is then no need > for the EntityStore to fully deserialize this state, which it cannot do > anyway due to the lack of Composite classes. > > -- > This message is automatically generated by JIRA. > - > If you think it was sent incorrectly contact one of the administrators: > http://issues.ops4j.org/jira/secure/Administrators.jspa > - > For more information on JIRA, see: http://www.atlassian.com/software/jira > > > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev > _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
