[
https://issues.apache.org/jira/browse/ISIS-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641504#comment-14641504
]
ASF subversion and git services commented on ISIS-1150:
-------------------------------------------------------
Commit a466fb5074819a97da8566ac046b0bb5fb5406a5 in isis's branch
refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=a466fb5 ]
ISIS-1150: mothballed the in-memory objectstore.
In addition, cosmetic change to all the pom.xml in isis/core, removed "Core"
from name (since we don't have any separate components anymore).
> 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)
