Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <28627487.1159797620066.JavaMail.root@brutus>
Date: Mon, 2 Oct 2006 07:00:20 -0700 (PDT)
From: "Alex Karasulu (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Closed: (DIRSERVER-342) Return non-null context on shutdown
 request
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DIRSERVER-342?page=all ]

Alex Karasulu closed DIRSERVER-342.
-----------------------------------


fixed and confirmed - dead context is returned

> Return non-null context on shutdown request
> -------------------------------------------
>
>                 Key: DIRSERVER-342
>                 URL: http://issues.apache.org/jira/browse/DIRSERVER-342
>             Project: Directory ApacheDS
>          Issue Type: Bug
>            Reporter: Alex Karasulu
>         Assigned To: Alex Karasulu
>            Priority: Critical
>
> We can still return a non-null JNDI context yet prevent users from using that context.  We can make it a dummy context which throws system shutdown exceptions where a new request for an initial context would need to fire the system back up again.  This will prevent some very nasty code to handle exceptions in the standard case.  Users will hate this if it sticks around.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira