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 2014/01/31 11:58:08 UTC

[jira] [Resolved] (ISIS-667) General tidy-up/rationalization of JDO domain service impls

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

Dan Haywood resolved ISIS-667.
------------------------------

    Resolution: Fixed

> General tidy-up/rationalization of JDO domain service impls
> -----------------------------------------------------------
>
>                 Key: ISIS-667
>                 URL: https://issues.apache.org/jira/browse/ISIS-667
>             Project: Isis
>          Issue Type: Improvement
>    Affects Versions: archetype-simple-wrj-1.3.1, archtype-quickstart-wrj-1.3.1, objectstore-jdo-1.3.0
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>             Fix For: archetype-simple-wrj-1.4.0, archetype-quickstart-wrj-1.4.0, objectstore-jdo-1.4.0
>
>
> We now have six implementations of various applib domain services by JDO objectstore:
> - auditing service
> - publishing service
> - background task service
> - interaction service
> - appsettings
> - user settings
> This ticket is to rationalize them (in particular the first four, that all share a common usage of transactionId)



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)