[
https://issues.apache.org/jira/browse/JCR-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1433:
-------------------------------
Status: Patch Available (was: Open)
> web.xml should contain explicit jndi-enabled param instead of checking for a
> provided java.naming.provider.url
> --------------------------------------------------------------------------------------------------------------
>
> Key: JCR-1433
> URL: https://issues.apache.org/jira/browse/JCR-1433
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-webapp
> Environment: This should work in every Servlet Container.
> Reporter: squiddle
> Priority: Minor
> Attachments: jndi-enabled-init-param.diff
>
>
> If there is no need or no possibilty to set a java.naming.provider.url it is
> impossible to use the RepositoryAccessServlet cause it won't lookup in the
> JNDI unless this is specified.
> The enabling of this feature should not depend on an optional Configparameter.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
