Mailing-List: contact aries-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: aries-dev@incubator.apache.org
Message-ID: <16068246.90151292248446911.JavaMail.jira@thor>
Date: Mon, 13 Dec 2010 08:54:06 -0500 (EST)
From: "Alasdair Nottingham (JIRA)" <jira@apache.org>
To: aries-dev@incubator.apache.org
Subject: [jira] Work started: (ARIES-515) Exceptions being hidden when
 thrown by InitialContextFactory from a Builder
In-Reply-To: <26075266.90011292247005511.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Work on ARIES-515 started by Alasdair Nottingham.

> Exceptions being hidden when thrown by InitialContextFactory from a Builder
> ---------------------------------------------------------------------------
>
>                 Key: ARIES-515
>                 URL: https://issues.apache.org/jira/browse/ARIES-515
>             Project: Aries
>          Issue Type: Bug
>          Components: JNDI
>    Affects Versions: 0.3
>            Reporter: Alasdair Nottingham
>            Assignee: Alasdair Nottingham
>             Fix For: 0.3
>
>
> A common use of JNDI is to perform authentication against an LDAP registry of users. This typically works by going new InitialDirContext(props) where the props contains a userid/password. This requires the AuthenticationException to be thrown from the InitialDirContext constructor. When used with the default JNDI implementation what actually happens is you get a NoInitialContextException because the creation of the Context fails and if the ICF was created from an ICFB then the exception is swallowed rather than rethrown.
> Alasdair

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.