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 2013/10/25 12:00:31 UTC

[jira] [Updated] (ISIS-534) Does JDO Objectstore ever need to create DataNucleusUpdateObjectCommand commands?

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

Dan Haywood updated ISIS-534:
-----------------------------

    Fix Version/s: objectstore-jdo-1.4.0

> Does JDO Objectstore ever need to create DataNucleusUpdateObjectCommand commands?
> ---------------------------------------------------------------------------------
>
>                 Key: ISIS-534
>                 URL: https://issues.apache.org/jira/browse/ISIS-534
>             Project: Isis
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: core-1.2.0
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>             Fix For: objectstore-jdo-1.4.0, core-1.4.0
>
>
> Following on from ISIS-533, I'm not sure there's ever any reason for the DataNucleusUpdateObjectCommand to do anything, therefore for it to be created.  The Isis core can, instead, merely rely upon DN's built-in object dirtying.
> This ticket is to explore this issue and perhaps to make the objectChanged() method - that creates the Update command - into a no-op if the JDO objectstore is configured.



--
This message was sent by Atlassian JIRA
(v6.1#6144)