Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <1509748890.1204150191146.JavaMail.jira@brutus>
Date: Wed, 27 Feb 2008 14:09:51 -0800 (PST)
From: "squiddle (JIRA)" <jira@apache.org>
To: dev@jackrabbit.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
In-Reply-To: <1324231383.1204138911441.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

    Attachment:     (was: 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.