Re: [Resin-interest] More on include()/forward() issue.

2008-03-07 Thread Mattias Jiderhamn
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

Re: [Resin-interest] More on include()/forward() issue.

2008-03-07 Thread Mattias Jiderhamn
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

Re: [Resin-interest] Disabling display of server info

2008-03-07 Thread Scott Ferguson
On Mar 3, 2008, at 6:46 PM, Chris Chen wrote: > Does anyone know if there is a configuration setting that allows me to > either disable server info or server version info when an error code/ > page is shown? > > Currently, if a 404 or 500 or other error occurs, resin outputs an > error with the s

Re: [Resin-interest] More on include()/forward() issue.

2008-03-07 Thread Ilya Kasnacheev
В сообщении от 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

Re: [Resin-interest] More on include()/forward() issue.

2008-03-07 Thread Huitang Li
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 develo

Re: [Resin-interest] More on include()/forward() issue.

2008-03-07 Thread Mattias Jiderhamn
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 forwar

Re: [Resin-interest] More on include()/forward() issue.

2008-03-07 Thread Ilya Kasnacheev
В сообщении от 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

[Resin-interest] More on include()/forward() issue.

2008-03-07 Thread Ilya Kasnacheev
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 " + resp