Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-127 JCR: Support for XML imports
  3. OAK-414

Importing protected properties and nodes

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.11
    • Component/s: jcr
    • Labels:
      None

      Description

      for backwards compatibility with jackrabbit we should also implement
      the ability to import protected items.

      while import version content is most probably unique and system defined,
      there are quite some areas like user management and access control that
      need to be pluggable and thus the particular import behavior should be
      defined by the corresponding implementation.

      i envision this to work in a similar way than the implementation
      specific validators.

      steps to get there include:

      • properly setup the xml-import such that it recognizes protected items
        and calls the configured protected-item-importers.
      • allow to plugin implementation specific extensions
      • define an interface for that protected item import.

      regarding the latest part: in contrast to jackrabbit core, where we had
      just the JCR API at hand i would suggest to setup those special importers
      such that they can operate both on the JCR API (session and extensions)
      and on the OAK API giving the implementation more flexibility on how
      to actually treat the import.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                baedke Manfred Baedke
                Reporter:
                angela Angela Schreiber
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: