[
https://issues.apache.org/jira/browse/JCR-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-2771.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.2.0
Assignee: Jukka Zitting
Implemented in revision 1005449.
> Simplified Repository URI format for JNDI lookups
> -------------------------------------------------
>
> Key: JCR-2771
> URL: https://issues.apache.org/jira/browse/JCR-2771
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jcr-commons
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Priority: Minor
> Fix For: 2.2.0
>
>
> The JndiRepositoryFactory class (together with JcrUtils) currently supports
> the following repository URI formats:
> JcrUtils.getRepository("jndi:name-of-repository");
>
> JcrUtils.getRepository("jndi://ignored?org.apache.jackrabbit.repository.jndi.name=name-of-repository&other-parameters");
> The first uri formats allows no extra JNDI environment settings to be passed
> in, and the second one is pretty verbose and simply ignores the authority and
> path parts of the URI.
> I'd like to add support for the following simplified format that makes it
> easy to provide the repository name along with the initial context factory
> from which the name is to be looked up:
>
> JcrUtils.getRepository("jndi://initial-context-factory/name-of-repository");
> Extra JNDI environment settings could still be included as additional query
> parameters. Backwards compatibility with the previous formats would be
> guaranteed based on the presence or absence of the
> org.apache.jackrabbit.repository.jndi.name parameter in hierarchical URIs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
