Details

    • Type: Task Task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.3
    • Component/s: jcr
    • Labels:
      None

      Description

      We should clean up oak-jcr: OAK-5 provides primarily JCR bindings. We should identify which parts thereof should go into other components and move them:

      • persistent node state handling should go into oak-core
      • JSON parsing should go into oak-core or some other place
      • stuff in the utils package should probably move to a common place depending on whether it is general enough

        Issue Links

          Activity

          Hide
          Michael Dürig added a comment -

          I resolve this as fixed since the main issues are addressed by now. We should open more specific bugs for further issues.

          Show
          Michael Dürig added a comment - I resolve this as fixed since the main issues are addressed by now. We should open more specific bugs for further issues.
          Hide
          Michael Dürig added a comment -

          By now (rev. 1311731) the dependencies to MicroKernel from oak-jcr have been removed.

          The remaining dependencies are on: NodeState, NodeStateEditor, PropertyState, Scalar, ScalarImpl and PathUtils.

          Except for PathUtils, I suggest to duplicate these in the oak-api (OAK-18) and evolve them independently from the corresponding entities in oak-mk on an as need basis.

          Wrt. PathUtils I think we should not rely on PathUtils from oak-mk but rather roll our own.

          Show
          Michael Dürig added a comment - By now (rev. 1311731) the dependencies to MicroKernel from oak-jcr have been removed. The remaining dependencies are on: NodeState, NodeStateEditor, PropertyState, Scalar, ScalarImpl and PathUtils. Except for PathUtils, I suggest to duplicate these in the oak-api ( OAK-18 ) and evolve them independently from the corresponding entities in oak-mk on an as need basis. Wrt. PathUtils I think we should not rely on PathUtils from oak-mk but rather roll our own.
          Hide
          Thomas Mueller added a comment -

          > JSON parsing should go into oak-core or some other place

          oak-mk also needs this, so I would keep the low-level part of JSON/JSON-Diff be in oak-mk. The higher level part (that is not needed in oak-mk) could be in oak-core.

          Show
          Thomas Mueller added a comment - > JSON parsing should go into oak-core or some other place oak-mk also needs this, so I would keep the low-level part of JSON/JSON-Diff be in oak-mk. The higher level part (that is not needed in oak-mk) could be in oak-core.
          Hide
          Michael Dürig added a comment -

          See also Oak component structure
          [1] http://wiki.apache.org/jackrabbit/OakComponentStructure

          Show
          Michael Dürig added a comment - See also Oak component structure [1] http://wiki.apache.org/jackrabbit/OakComponentStructure

            People

            • Assignee:
              Michael Dürig
              Reporter:
              Michael Dürig
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development