request.getRequestDispatcher include priority is corrupted

Konstantin,

The output is actually correct.
The reason for that is the JspWriter does not write to the response outputstream/writer not until the full jsp file is served (in your case "index.jsp").

request.getRequestDispatcher("includePage.jsp?p=2").include(request, response) <-- this writes the content after serving includePage.jsp which is why
it appears first on the page.

I've deployed your webapp to tomcat-5.5 and I'm getting the same output.

Cheers,
dyu

I would suggest you use jsp:include in all your pages to sync the writing of the content with the JspWriter on your main jsp.

Hmm, I do not think the behavior is consistent with javadoc
http://java.sun.com/j2ee/1.4/docs/api/javax/servlet/RequestDispatcher.html#include(javax.servlet.ServletRequest,%20javax.servlet.ServletResponse)

And I am aware that Tomcat behaves similarly, but I do not think that makes the behavior correct.

>>The reason for that is the JspWriter does not write to the response outputstream/writer not until the full jsp file is served (in your case "index.jsp").

Well, that means IMO that implementation of the request dispatcher should write its response to JspWriter since that is what is used currently for rendering response.

You're trying to tie up the JspWriter with the RequestDispatcher Nowhere to be found in the specs.
Remember, not all webapps use jsp. And a jsp is just "another servlet".

Since you really want to use that code, then:

• call out.flush() before you dispatch
  e.g.
  <% out.flush(); request.getRequestDispatcher("includePage.jsp?p=2").include(request, response); %>

That should follow the flow of your index.jsp.

Cheers

No, I do not want them to be tied: but since the current response is passed to the dispatcher it should use it to write response to it. Spec says that response should be "included" not prepended, and that the method is analogous to the 'server side include'.

So it should work this way.

So what happening is quite strange IMO: the out on the page is different instance of writer then we get by calling response.getWriter()

<%= out.toString() %>
<br/>
<%= response.getWriter().toString()%>
gives this

org.apache.jasper.runtime.JspWriterImpl@a270b2
org.mortbay.jetty.HttpConnection$1@94d9d5

to make matters worse: if jsp output before call to the request dispatcher exceeds the buffer size for the JspWriter then by defaults response from dispatcher will appear at arbitrary place in the total response....