Uploaded image for project: 'Isis'
  1. Isis
  2. 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

    Details

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              danhaywood Dan Haywood
              Reporter:
              danhaywood Dan Haywood
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: