[ openjms-Bugs-797689 ] Embedded JNDI contexts should be read-only

Bugs item #797689, was opened at 2003-08-30 16:57
Message generated for change (Comment added) made by tanderson
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=797689&group_id=54559

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: jndi
Group: v0.7.6-rc1
>Status: Closed
>Resolution: Rejected
Priority: 5
Submitted By: Tim Anderson (tanderson)
>Assigned to: Tim Anderson (tanderson)
Summary: Embedded JNDI contexts should be read-only

Initial Comment:
The Context instances returned by the embedded JNDI 
provider should be read-only. It shouldn't be possible to 
add, remove, or change bindings.

----------------------------------------------------------------------

>Comment By: Tim Anderson (tanderson)
Date: 2005-08-31 16:03

Message:
Logged In: YES 
user_id=557161

Closing this. There is no good reason to do this any longer, 
particularly now that the embedded JNDI service supports 
authentication.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=797689&group_id=54559


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf