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
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.
