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

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ISIS-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14591681#comment-14591681 ] 

ASF subversion and git services commented on ISIS-1150:
-------------------------------------------------------

Commit 020be43b1041c4f433c54c9499d0815510eafcf6 in isis's branch refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=020be43 ]

ISIS-1150: migration notes for exception recognizer.

also factored the migration notes away from the release notes.


> 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)