Thanks for replies, Scott and Daniel!
Today I went the 'find references and eliminate them' way. I looked into heap
dump, found reference that could possibly screw things, and eliminated it.
After each of them I started resin, touched web.xml for a few times and
dumped heap.
I've found this
I've found one thing in resin 3.1 regarding RequestDispatcher, include() and
forward()
Let's suppose we have a ServletResponse, and we've wrote some text into its
output stream, so it's now in committed state.
That means, as J2EE spec tells, that we can no longer do forward() on it, or
we'll
В сообщении от 27 Февраль 2008 19:30 Huitang Li написал(a):
I tested with struts 1.0.x, 1.1.x, and 1.2.x, I got the same error.
However, when I tried struts 1.3.8, this exception disappeared.
Well, I've switched to struts 1.3.8 as you suggested, but exception is still
in place. I guess I'll
Let's say we've got a servlet such as
==
protected void doGet(HttpServletRequest request, HttpServletResponse
response)
throws ServletException, IOException
{
RequestDispatcher rd = getServletContext().getRequestDispatcher(/target);
String s;
s = Launcher: response is
+
В сообщении от 7 Март 2008 13:14 Ilya Kasnacheev написал(a):
response
P.S. I wonder how bad it can be:
response = new HttpServletResponseWrapper(response) {
public boolean isCommitted()
{
return false;
}
};
That's, like, http://folk.poesie.ru
В сообщении от 7 Март 2008 15:48 Mattias Jiderhamn написал(a):
If I understand your question: the reason the DispatchResponse is
committed is that you have called .flush() explicitly on the original
HttpServletRequest (HttpResponse).
Yeah, that's what I did exactly. It would have committed it
В сообщении от 7 Март 2008 22:12 Mattias Jiderhamn написал(a):
page - include (forward - forward - forward - forward - page)
... forward() in included servlet does not mean instead of including
page but instead of included page
Ok, now I see where you're coming from.
Do you have to
