[
https://issues.apache.org/jira/browse/ISIS-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401728#comment-13401728
]
Dan Haywood commented on ISIS-234:
----------------------------------
It seems that we only ever call remapAsPersistent for root adapters, never for
aggregated entities. I suspect this means that the OIDs of these aggregated
entities cannot be trusted after the persist.
However, if the user does not do a flush (ie all persistence happens after the
action is completed), then this ought not be a problem, assuming that the
objectstore is clever enough to know how to persist an aggregated object. I'm
guessing that they could be, because - at least in theory - they have the
context of the root adapter being persisted.
~~~
If all the above is bogus, then the remapAsPersistent will probably need to be
enhanced to also walk the graph looking for aggregated entities that have a
parent OID of the root adapter initially being persisted. (It either walks the
graph, or just does a brute-force search through the ObjectManager's maps).
> Persistence by reachability of aggregated instances fails.
> ----------------------------------------------------------
>
> Key: ISIS-234
> URL: https://issues.apache.org/jira/browse/ISIS-234
> Project: Isis
> Issue Type: Bug
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: 0.3.0-incubating
>
>
> as per
> http://mail-archives.apache.org/mod_mbox/incubator-isis-dev/201206.mbox/%3C4FE3BAC2.8040001%40nakedobjects.org%3E
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
