jsr-283
  1. jsr-283
  2. JSR_283-777

Set property definitions of mix:versionable to IGNORE

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: current
    • Fix Version/s: milestone 1
    • Component/s: versioning
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      777

      Description

      the spec defines a versionable node like this:

      [mix:versionable] > mix:simpleVersionable, mix:referenceable mixin

      • jcr:versionHistory (REFERENCE) mandatory protected < 'nt:versionHistory'
      • jcr:baseVersion (REFERENCE) mandatory protected IGNORE < 'nt:version'
      • jcr:predecessors (REFERENCE) mandatory protected multiple < 'nt:version'
      • jcr:mergeFailed (REFERENCE) protected multiple ABORT
      • jcr:activity (REFERENCE) protected < 'nt:activity'
      • jcr:configuration (REFERENCE) protected < 'nt:configuration'

      so when the node is checked-in the versioning properties are copied into the frozen node, although
      they are already stored in the version or the version history.

      at least for the new "jcr:activity" we should set it to IGNORE.

        Activity

        Hide
        Peeter Piegaze added a comment -

        Fixed
        jcr:predecessors and jcr:activity set to IGNORE

        Show
        Peeter Piegaze added a comment - Fixed jcr:predecessors and jcr:activity set to IGNORE
        Hide
        geoffreyclemm added a comment -

        The jcr:configuration and jcr:versionHistory should also be marked as "ignore".

        Note: for folks interested in how we got here, originally we didn't have the
        separation between a version node and a frozen node, so these properties were
        in fact copied to the nt:version node. When we introduced the frozen node, we
        redefined on-parent-version to just refer to properties copied to the frozen
        node, and we neglected to update the property definitions on the
        mix:versionable properties.

        Show
        geoffreyclemm added a comment - The jcr:configuration and jcr:versionHistory should also be marked as "ignore". Note: for folks interested in how we got here, originally we didn't have the separation between a version node and a frozen node, so these properties were in fact copied to the nt:version node. When we introduced the frozen node, we redefined on-parent-version to just refer to properties copied to the frozen node, and we neglected to update the property definitions on the mix:versionable properties.
        Hide
        Peeter Piegaze added a comment -

        Fixed in spec and in javax/jcr/nodetype/package.html

        Show
        Peeter Piegaze added a comment - Fixed in spec and in javax/jcr/nodetype/package.html

          People

          • Assignee:
            jsr-283-issues
            Reporter:
            tripod
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: