[JBoss-dev] [ jboss-Bugs-594563 ] Include of JSP jumps to top of page

[<no...@so...>]

Bugs item #594563, was opened at 2002-08-13 05:18
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=594563&group_id=22866

Category: CatalinaBundle
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Jeff Miner (jeff_miner)
Assigned to: Scott M Stark (starksm)
Summary: Include of JSP jumps to top of page

Initial Comment:
OS: Win98
JDK: 1.4

I have some code that manually does a JSP include 
by getting a RequestDispatcher.  The code worked 
under Weblogic 5.1 and 6.  In Jboss/Catalina, 
although there are no errors thrown, the output from 
the included JSP gets put at the top of the containing 
page rather than in the middle where it was called.  
This is puzzling because it ought to be exactly the 
same as a <jsp:include ...> tag (and I assume those 
work!)

******Containing Page*******
....<table><tr><td>

<%= myObject.getOutput(request, response) %>

</td></tr></table>...


******* Object ********
  public String getOutput(HttpServletRequest request, 
HttpServletResponse response) {
     RequestDispatcher dispatch = 
context.getRequestDispatcher("someJSP.jsp");
     try {
           dispatch.include(request, response);
          } catch(Exception e){}
    return "";
*************

The output from "someJSP.jsp" should go inside the 
table, but instead it goes at the top of the containing 
page.


----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2002-09-30 03:43

Message:
Logged In: NO 

The jump to the top of the page is due to the buffer not being 
flushed. The given example is the same as a jsp include 
without a buffer flush. If you want the buffer flushed, you have 
to explicitly code that.

----------------------------------------------------------------------

Comment By: Scott M Stark (starksm)
Date: 2002-09-28 20:12

Message:
Logged In: YES 
user_id=175228

This was a jasper issue that has been fixed.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=594563&group_id=22866