Uploaded image for project: 'Causeway'
  1. Causeway
  2. CAUSEWAY-534

Does JDO Objectstore ever need to create DataNucleusUpdateObjectCommand commands?

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • core-1.2.0
    • 1.10.0
    • Core
    • None

    Description

      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.

      Attachments

        Issue Links

          is part of

          Improvement - An improvement or enhancement to an existing feature or task. CAUSEWAY-1194 Remove dead code, remove support for @Aggregated, for isDirty/clearDirty/markDirty.

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              Unassigned Unassigned
              danhaywood Daniel Keir Haywood
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: