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
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution||INVALID
--- Additional Comments From [EMAIL PROTECTED] 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
