[ https://issues.apache.org/jira/browse/ISIS-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16977278#comment-16977278 ]
ASF subversion and git services commented on ISIS-2177: ------------------------------------------------------- Commit 7ade8e2a0afdef8880dd5c11056a989b46d31a63 in isis's branch refs/heads/2177-object-manager from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=7ade8e2 ] ISIS-2177: move RepositoryServiceJdo 'metamodel' -> 'runtime' module in preparation of removing PersistenceSessionServiceInternal > Provide an ObjectManager API to decouple from JDO > ------------------------------------------------- > > Key: ISIS-2177 > URL: https://issues.apache.org/jira/browse/ISIS-2177 > Project: Isis > Issue Type: Improvement > Components: Core > Reporter: Andi Huber > Assignee: Andi Huber > Priority: Major > Fix For: 2.0.3 > > > We are implementing an ObjectManager that is an API to replace > ObjectAdapterProvider, PersistenceSession and others that are closely coupled > with JDO. > Following a chain of responsibility pattern ObjectManager is setup with a > couple of handlers for different responsibilities, these are: > 1. Object creation, newing up from a given ObjectSpecification, initializing > defaults and resolving injection points if required. > 2. Object re-creation from a given ObjectSpecification + Object-Identifier, > resolving injection points if required. > 3. Object persisting for a given ObjectSpecification and the actual Object a > pojo. Conceptually this might also include aspects of serializing > ManagedObjects into in-memory mementos. -- This message was sent by Atlassian Jira (v8.3.4#803005)