[SLING-2352] Move out the repository RegistrationSupport support logic to a different bundle

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: JCR Jackrabbit Server 2.1.0
• Fix Version/s: JCR Registration 1.0.0, JCR Jackrabbit Server 2.1.2
• Component/s: JCR
• Assignee: Felix Meschberger
• Reporter: Chetan Mehrotra
• Created: 10/Jan/12 17:54
• Updated: 09/Aug/13 13:41
• Resolved: 02/May/12 13:45

Description

We have a usecase where we want to embed the Sling based war within an existing ear. In that mode we want to expose the repository instance registered by a different bundle (other than org.apache.sling.jcr.jackrabbit.server bundle) into the JNDI so that code within the ear can access the repository in InVM mode

Currently the Repository registration support logic is part of org.apache.sling.jcr.jackrabbit.server bundle. However this bundle is also responsible for creating and registering the Jackrabbit repository instance.

Attached is a patch which refactors the registration logic into a different bundle.

Points to note regarding patch
1. The RmiRegistrationSupport has been retained in the Jackrabbit Server Bundle due to its dependency on the Jackrabbit classes
2. The AbstractRegistrationSupport has been moved to a different package and part of exported package now and is now imported by JR Server bundle. This is done to support #1 above
3. The component names have been retained for backward compatibility support for configuration