You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Andi Huber (Jira)" <ji...@apache.org> on 2019/11/14 17:20:00 UTC

[jira] [Created] (ISIS-2177) Provide a ObjectManager API to decouple from JDO

Andi Huber created ISIS-2177:
--------------------------------

             Summary: Provide a 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
             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)