[ https://issues.apache.org/jira/browse/ISIS-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andi Huber resolved ISIS-3167. ------------------------------ Resolution: Resolved ManagedObject.getPojo() in the ENTITY case is now no longer free of side-effects, that means any call to it will check whether the pojo is attached or not, and re-fetch if an OID was previously memorized. In the event of such a state change the _ManagedObjectEntityHybrid behind the scenes transitions between 2 different behaviors as implemented by: _ManagedObjectEntityDetached _ManagedObjectEntityAttached I had to introduce a new EntityState: PERSISTABLE_NEW, to better reflect what's going on with DN/JDO > Comparator in @CollectionLayout(sortedBy = ...) gets passed in detached > Entities > -------------------------------------------------------------------------------- > > Key: ISIS-3167 > URL: https://issues.apache.org/jira/browse/ISIS-3167 > Project: Isis > Issue Type: Bug > Components: Isis Core > Reporter: Andi Huber > Assignee: Andi Huber > Priority: Blocker > Fix For: 2.0.0-M8 > > > eg. > @CollectionLayout(sortedBy = MyObjectComparator.class) > public List<MyObject> listAll() \{ > // .. > } > -- This message was sent by Atlassian Jira (v8.20.10#820010)