DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25508>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25508 JNDI Does Not Set Up "comp" namespace ------- Additional Comments From [EMAIL PROTECTED] 2004-02-27 23:35 ------- There is a work around for this: the problem goes away (at least it does for me in 4.1.29) if you ensure that the names of the chain of containers leading to your Context are unique. For example, make sure that multiple Engines and/or Hosts have different names. I think this bug results from the way that NamingContexts are registered, which is static, but by a name derived from values with no reference to the actual instance. The name derivation happens in org.apache.catalina.core.StandardContext.getNamingContextName(), which builds a name by concatenating the names in the container chain together separated by slashes. When a listener for a context is created with a duplicate name, it is going to go unregistered when it subsequently fails the ContextAccessController security checks based on its name (which is already registered) and its container, which is the wrong token for the registered Context. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
