tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 40801] - antiResourceLocking causes undexpected context results from jndi queries
Date Tue, 07 Nov 2006 04:50:54 GMT
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=40801>.
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=40801


rick.fisk@authoria.com changed:

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




------- Additional Comments From rick.fisk@authoria.com  2006-11-06 20:50 -------
I beg to differ. We are using a context.xml file and it conforms to the 
document you've linked. 

The problem is that getservletContextName() does not report the context of the 
application as it was deployed when antiJarLocking and antiResourceLocking is 
enabled.

If I deploy my app at webapps/foo, getservletContextName reports 8-foo instead 
of the proper context. How is that not a bug?

The only question I asked was if there was a workaround. What we have had to 
do is to strip off the leading [\d-] from the erroneous value returned from 
the call. 

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message