Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-2909

Review and improve Oak and Jcr repository setup

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Won't Fix
    • None
    • None
    • core, jcr

    Description

      There is the Oak and Jcr builder classes for setting up Oak and Jcr repositories. Both builders don't have clear semantics regarding the life cycle of the individual components they register. On top of that the requirements regarding those life cycles differ depending on whether the individual components run within an OSGi container or not. In the former case the container would already manage the life cycle so the builder should not.

      IMO we should specify the builders to only be used for non OSGi deployments and have the manage the life cycles of the components they instantiate. OTOH for OSGi deployments we should leverage OSGi subsystems to properly set things up.

      Attachments

        Issue Links

          relates to

          Sub-task - The sub-task of the issue OAK-2775 Oak builder changes its state during repository creation

          • Major - Major loss of function.
          • Resolved

          Sub-task - The sub-task of the issue OAK-2894 RepositoryImpl should not manage the lifecycle of ContentRepository

          • Major - Major loss of function.
          • Resolved

          Sub-task - The sub-task of the issue OAK-2932 Limit the scope of exported packages

          • Major - Major loss of function.
          • Resolved

          Sub-task - The sub-task of the issue OAK-2828 Jcr builder class does not allow overriding most of its dependencies

          • Major - Major loss of function.
          • Closed

          Sub-task - The sub-task of the issue OAK-2760 HttpServer in Oak creates multiple instance of ContentRepository

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

          Bug - A problem which impairs or prevents the functions of the product. OAK-3197 RepositoryImpl doesn't close the scheduler nicely

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. OAK-2736 Oak instance does not close the executors created upon ContentRepository creation

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

          Improvement - An improvement or enhancement to an existing feature or task. OAK-2786 Add a way to to get the OAK ContentRepository from the JCR Repository

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              frm Francesco Mari
              mduerig Michael Dürig
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: