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 31523] - Request parameters are not always passed to HttpServlet.service
Date Mon, 04 Oct 2004 11:36:37 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=31523>.
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=31523

Request parameters are not always passed to HttpServlet.service





------- Additional Comments From remm@apache.org  2004-10-04 11:36 -------
Yes, of course, all the container objects provided by Tomcat are recycled. The
exception is, of course, when using a security manager. In that case, all the
facade objects are invalidated, and then discarded.

Adding "getParameterNames" is inefficient, but useful for debug.
request.getParameter("foo") would trigger the same evaluation as well.

So, since the issue would be independent of Cocoon, do you think you can build a
single JSP page (or servlet if you're more comfortable with servlets) with an
appropriate form (you didn't describe either what the form should be) in it
which would reproduce the issue ?
I still recommend trying my workaround, though. You can also tweak the request
class, and modify the recycling of components (discarding the response and
streams facades, etc) to see what it does.

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


Mime
View raw message