Ilya Kasnacheev wrote (2008-03-12 12:18):
В сообщении от 12 Март 2008 12:07 Mattias Jiderhamn написал(a):
What about my anonymous wrapper? See reply to original post.
It may work if you are certain there will be no flushing to the client
before a forward().
Nope, there
Ilya Kasnacheev wrote (2008-03-11 11:35):
or would increasing the
buffer (response.setBufferSize()) prevent the response from being
comitted until the included forward has been issued???
This way is too like hack. What if we'll fill this buffer prematurely anyway?
If the amount of data
В сообщении от 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
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,
If I understand your question: the reason the DispatchResponse is
committed is that you have called .flush() explicitly on the original
HttpServletRequest (HttpResponse).
This is nothing strange. Why could you want to create a wrapper to
hide the commited state, so that you can perform
Here is not a solution, while it gives some insights on java sevelet
spec and jsp spec:
http://today.java.net/pub/a/today/2005/08/04/jspcomponents.html?page=3#jsp_servlets_compatibility
In this article, it referred to old resin versions, I believe. Probably
this can be helpful for resin
В сообщении от 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
Ilya Kasnacheev wrote (2008-03-07 16:33):
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 issue the explicit .flush() or
Ilya Kasnacheev wrote (2008-03-07 16:33):
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 issue the explicit .flush() or
10 matches
Mail list logo
