jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "squiddle (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-1433) web.xml should contain explicit jndi-enabled param instead of checking for a provided java.naming.provider.url
Date Wed, 27 Feb 2008 22:09:51 GMT

     [ https://issues.apache.org/jira/browse/JCR-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

squiddle updated JCR-1433:
--------------------------

    Attachment: jndi-enabled-init-param.diff

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


Mime
View raw message