jsr-283
  1. jsr-283
  2. JSR_283-307

Retention&Hold assigned to any node -> Clarify

    Details

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

      Operating System: All
      Platform: All

    • Issuezilla Id:
      307

      Description

      the specification points out that retention policies and holds may be applied
      to any node in the repository. while i see a potential use case for this, i
      think the specification is not sufficiently precise:

      a) there is a distinction between nodes that are 'protected' according
      to the child node definition applied and the version storage that is
      defined to be read-only.

      b) adding a mixin node type to a node is a transient write operation and
      (as far is i know) can neither be applied to a protected node (->see
      canAddMixin(String mixinName)) nor to any node in the version storage.

      from my understanding applying a retention policy or a hold to a protected node
      or to a node in the version storage is therefore only possible if the mixin type
      mix:managedRetention forms part of the primary nodetype definition (i.e. is a
      super type or an inherited super type). it would however not be possible to add
      the mix:managedRetention manually by calling Node.addMixin(String).

      and I am not totally sure if the following sentence of the specification is in
      accordance with my understanding:

      "Retention and hold may be applied to any node in any workspace (
      including nodes in version and other system storage areas), subject
      to implementation-specific restrictions on the assignment of node types."

        Issue Links

          Activity

          Hide
          stefan_guggisberg added a comment -

          as per F2F decision in Basel, Sept 07:

          deferred (revisit current Retention&Hold spec)

          Show
          stefan_guggisberg added a comment - as per F2F decision in Basel, Sept 07: deferred (revisit current Retention&Hold spec)
          Hide
          anchela added a comment -

          add dependency to #418 and correct subcomponent

          Show
          anchela added a comment - add dependency to #418 and correct subcomponent
          Hide
          Peeter Piegaze added a comment -

          RC17: R&H rewrite has removed the mixin mix:managedRetention

          Show
          Peeter Piegaze added a comment - RC17: R&H rewrite has removed the mixin mix:managedRetention

            People

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

              Dates

              • Created:
                Updated:
                Resolved: