You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2015/06/17 01:19:00 UTC

[jira] [Updated] (ISIS-1150) Retire the InMemoryObjectStore

     [ https://issues.apache.org/jira/browse/ISIS-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Haywood updated ISIS-1150:
------------------------------
    Fix Version/s:     (was: 1.10.0)
                   1.9.0

> Retire the InMemoryObjectStore
> ------------------------------
>
>                 Key: ISIS-1150
>                 URL: https://issues.apache.org/jira/browse/ISIS-1150
>             Project: Isis
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: core-1.8.0
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>             Fix For: 1.9.0
>
>
> Instead, should just use the DataNucleusObjectStore (configured with in-memory HSQLDB or H2 if required).
> One important reason we should remove this objectstore is that the semantics/behaviour on the domain objects differs.  For example, using DN bidirectional associations are automatically managed; this isn't the case with the in-memory objectstore.
> Moreover, if an app becomes too big thus the integ tests become too slow, then the developer should modularize and decouple their app such that individual parts can be worked on independently.  Having an in-memory objectstore dissuades the developer from "doing the right thing".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)