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=3727>.
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=3727
Switched included request parameters
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
------- Additional Comments From [EMAIL PROTECTED] 2001-09-21 17:17 -------
Sorry to be so insistent, but for the area of servlet-based framework
development neither the given mapping nor the use of the include mechanism
are 'abnormal'. Any framework containing a central contoller servlet, which
handles all requests sent to the corresponding application context, has its url
mapping set to '/' and '/*'.
To push the problem back into the scope of the servlet API specification I have
modified the test code to call the servlet using its name. Thus, the call looks
like:
RequestDispatcher disp = null;
disp = getServletContext().getRequestDispatcher("/SnoopIncluder");
And, still, we get different results depending on the set of url mappings
present in the web.xml file. Having only '/' and '/*' defined the output
contains:
javax.servlet.include.path_info = /SnoopIncluder
javax.servlet.include.servlet_path =
javax.servlet.include.context_path = /appsvtest
javax.servlet.include.request_uri = /appsvtest/SnoopIncluder
Adding a dummy url mapping, the values are set as it might be expected:
javax.servlet.include.servlet_path = /SnoopIncluder
javax.servlet.include.context_path = /appsvtest
javax.servlet.include.request_uri = /appsvtest/SnoopIncluder
The example shows, that the problem has nothing to to with the "Invoker". For me
this rather looks like a pattern matching problem for a given set of url
mappings and a request URI.
