You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Scott Basinger (JIRA)" <ji...@apache.org> on 2008/09/11 23:51:44 UTC
[jira] Commented: (SLING-254) Launchpad war should optionally use
an external Repository, without requiring a change of bundles
[ https://issues.apache.org/jira/browse/SLING-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630394#action_12630394 ]
Scott Basinger commented on SLING-254:
--------------------------------------
The issue I have when deploying to JBoss, where Jackrabbit JCA is the external repository, is JBoss registers all JNDI references under java:*. so jcr/local is registered as java:jcr/local. RepositoryAccessor jndi lookup logic tokenizes based on a colon, which is a valid charater in a jndi name. Could that separator be changed to a | or some non-valid jndi naming character.
> Launchpad war should optionally use an external Repository, without requiring a change of bundles
> -------------------------------------------------------------------------------------------------
>
> Key: SLING-254
> URL: https://issues.apache.org/jira/browse/SLING-254
> Project: Sling
> Issue Type: Improvement
> Components: Launchpad
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
>
> It would be useful to allow the Launchpad to use an external Repository (accessed via JNDI or RMI), without having to modify the war file or load/unload bundles.
> I'll search for a solution along these lines:
> 1) Launchpad includes both the jackrabbit-server (embedded repository) and jackrabbit-client (access to external repositories via JNDI or RMI) bundles, but by default the jackrabbit-client does not provide a Repository.
> 2) At startup, the Sling class searches the classpath and/or environment for additional configuration properties
> 3) A specific configuration property prevents the jackrabbit-server bundle from providing a Repository, and lets the jackrabbit-client provide it.
> In this way, the web container could be setup in advance to define which Repository to use, and new releases of the launchpad war file could be dropped in without requiring any configuration or war file changes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (SLING-254) Launchpad war should optionally
use an external Repository, without requiring a change of bundles
Posted by Felix Meschberger <fm...@gmail.com>.
Hi Scott,
Scott Basinger (JIRA) schrieb:
> The issue I have when deploying to JBoss, where Jackrabbit JCA is the external repository, is JBoss registers all JNDI references under java:*. so jcr/local is registered as java:jcr/local. RepositoryAccessor jndi lookup logic tokenizes based on a colon, which is a valid charater in a jndi name. Could that separator be changed to a | or some non-valid jndi naming character.
Thanks for posting this question.
Could you please turn to the mailing list or create a new issue for this
? Thanks. This issue has long been closed. Any follow up discussions
should be held on the mailing list or a new issue. Otherwise this might
create confusion in the future.
Thank you very much for your comprehension.
Regards
Felix
>
>
>
>
>
>> Launchpad war should optionally use an external Repository, without requiring a change of bundles
>> -------------------------------------------------------------------------------------------------
>>
>> Key: SLING-254
>> URL: https://issues.apache.org/jira/browse/SLING-254
>> Project: Sling
>> Issue Type: Improvement
>> Components: Launchpad
>> Reporter: Bertrand Delacretaz
>> Assignee: Bertrand Delacretaz
>>
>> It would be useful to allow the Launchpad to use an external Repository (accessed via JNDI or RMI), without having to modify the war file or load/unload bundles.
>> I'll search for a solution along these lines:
>> 1) Launchpad includes both the jackrabbit-server (embedded repository) and jackrabbit-client (access to external repositories via JNDI or RMI) bundles, but by default the jackrabbit-client does not provide a Repository.
>> 2) At startup, the Sling class searches the classpath and/or environment for additional configuration properties
>> 3) A specific configuration property prevents the jackrabbit-server bundle from providing a Repository, and lets the jackrabbit-client provide it.
>> In this way, the web container could be setup in advance to define which Repository to use, and new releases of the launchpad war file could be dropped in without requiring any configuration or war file changes.
>