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=25965>. 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=25965 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2005-01-06 00:50 ------- Let me approach this from a different angle to impress upon you that this is a bug. What is the point of invoking a servlet in another application if one is expected to provide all the resources (JSPs etc.) that is going to be included by that servlet? Think about this for a second. It is very likely that someone else wrote application B and its purpose is entirely different from application A. The folks that wrote application B packaged their application with JSPs/HTML files etc. that are included/forwarded to by their servlet. If I write application A and want to invoke a servlet in application B, am I expected to know what are all the resources included/forwarded by the servlet in application B and in addition provide them in my application??? That is what you are effectively saying and it makes no sense. This is a bug in Tomcat. Thanks to William for pointing out the spec. If the request is currently being processed by the servlet in application B, then the current servlet context is clearly B and not A. At the risk of repetition, it doesn't matter that the request came to application A first. Application A passed along the request to a servlet in application B after obtaining the servlet context for B and hence we are in B's context now. The resources should then be looked up in application B not application A. Please stop dismissing this as invalid as this is a bug (it is quite irritating to reopen it again and again). I ran this example in another server (Weblogic 8.1) and it worked flawlessly (the resource was looked up in application B and not application A). At the very least, leave it as REOPENED so that other folks can provide their input. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
