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 2002/02/25 20:16:04 UTC

DO NOT REPLY [Bug 6662] New: - servlet context fails if webapp name smaller version of another webapp

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=6662>.
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=6662

servlet context fails if webapp name smaller version of another webapp

           Summary: servlet context fails if webapp name smaller version of
                    another webapp
           Product: Tomcat 4
           Version: 4.0.2 Final
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: heitzso@bellsouth.net


Not sure I have the summary correct.
We have both "TheDataWeb" and "TheDataWeb_XXXs"
webapps in the webapp directory.  A configuration
service is provided by one of the webapps.  It's
accessed via a sc = getServletContext() followed by
code that uses the sc.getContext()
to pick up an attribute that's been stored in
a context via getAttribute("blat");

This works across webapps in 4.0.1 w/o crossContext
in server.xml but has to have crossContext="true"
in server.xml in 4.0.2.  That's not the 'bug' I'm
working with.

It works fine from TheDataWeb_X1 and TheDataWeb_X2
but _not_ from TheDataWeb.  (following the above
rules for crossContext).  All I have to do is rename
'TheDataWeb' to something unique, i.e. 'TheDataWeb_X3'
and, voila, the configuration information that's 
stored in the attribute is suddenly available the
way it's been all along for the other, uniquely named,
webapps.

I'll be glad to provide any level of code detail.
The problem is in both 4.0.1 and 4.0.2.  When
testing 4.0.2 I carefully setup crossContext="true"
for all webapps in server.xml, including the 
substring-not-unique-webapp-named webapp.  The
crossContext setup worked for all webapps except
the substring-not-unique-webbapp-named webapp.

Note that I'm not sure the crossContext default/setting
has anything to do with this problem.


Heitzso
xxh1@cdc.gov or heitzso@bellsouth.net

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>