You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2012/05/02 05:29:03 UTC
[jira] [Commented] (SLING-2352) Move out the repository
RegistrationSupport support logic to a different bundle
[ https://issues.apache.org/jira/browse/SLING-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266315#comment-13266315 ]
Chetan Mehrotra commented on SLING-2352:
----------------------------------------
Hi Felix,
Were you able to look into this issue?
> Move out the repository RegistrationSupport support logic to a different bundle
> -------------------------------------------------------------------------------
>
> Key: SLING-2352
> URL: https://issues.apache.org/jira/browse/SLING-2352
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Jackrabbit Server 2.1.0
> Reporter: Chetan Mehrotra
> Assignee: Felix Meschberger
> Priority: Minor
> Attachments: repository-registrar.patch
>
>
> 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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira