[jira] [Resolved] (ISIS-733) If toggle an object twice in standalone list (for bulk action), ends up invoking action (when shouldn't) and also throwing concurrency exception

["Dan Haywood (JIRA)" <ji...@apache.org>]

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

Dan Haywood resolved ISIS-733.
------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: objectstore-jdo-1.4.0)
                   objectstore-jdo-1.4.1

> If toggle an object twice in standalone list (for bulk action), ends up invoking action (when shouldn't) and also throwing concurrency exception
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ISIS-733
>                 URL: https://issues.apache.org/jira/browse/ISIS-733
>             Project: Isis
>          Issue Type: Bug
>          Components: Objectstore: JDO
>    Affects Versions: objectstore-jdo-1.3.0
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>            Priority: Minor
>             Fix For: objectstore-jdo-1.4.1
>
>
> Problem tracked down to the way in which the Wicket viewer attempts to detect that an object has already been toggled, ultimately relying on the toString of the oidStr, which includes the Version's timestamp.
> The underlying problem is that, for each interaction, the JDO objectstore simply new's up a new Date() for the timestamp, rather than leaving as null.
> The net effect is that the check for existence of a toggled object in the Wicket viewer fails.
> Fix is for the JDO objectstore to leave the Version's timestamp as null.



--
This message was sent by Atlassian JIRA
(v6.2#6252)