You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2004/09/17 17:50:56 UTC

DO NOT REPLY [Bug 30079] - Inconsistent JNDI lookups within ServletContextListener

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30079>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30079

Inconsistent JNDI lookups within ServletContextListener

yoavs@computer.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From yoavs@computer.org  2004-09-17 15:50 -------
DefaultContext JNDI behavior was a bit shaky with a few Tomcat releases, so it 
could be your issue is valid.  However:
- DefaultContext is gone altogether in Tomcat 5.5, replaced with a different 
mechanism,
- JNDI resources work fine for both normal Contexts and via 
GlobalNamingResources/ResourceLink: either one of those is a better approach 
and more encouraged than using DefaultContext,
- Several Tomcat versions on the 5.0.x branch have been released since, so if 
you really must keep using DefaultContext you could try these later versions

Given those three points, and the lack of response to Remy's comments from two 
months ago, I'm going to close this issue as INVALID.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org