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

Fail loudly if an obsolete OSGi configuration is used against oak-segment-tar

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • Segment Tar 0.0.12
    • segment-tar
    • None

    Description

      Even if oak-segment-tar is meant to replace oak-segment in any given OSGi setup, a deployer might still create a configuration against the old PID for SegmentNodeStoreService where instead the new PID should be used. In this case, oak-segment-tar should be able to intercept the configuration targeting the old PID and print a meaningful error message in the log.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            frm Francesco Mari
            frm Francesco Mari
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment