You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@tomcat.apache.org by Dave Jones <dj...@ix.netcom.com> on 2003/04/23 21:15:45 UTC

jsp:include problem migrating to Tomcat 4.1.18

Hi,
I've run into a problem migrating an application from Tomcat 3.3 
to 4.1.18. Briefly, the problem is that my JSP pages, which 
include several jsp:include tags, stop displaying at the first 
include when an exception is thrown by a later include.

Example:
<body>
<html>
<table>
         <tr><td>        <----- (A)
         <jsp:include page="header.jsp" flush="true" />
         </td></tr>

         <tr><td>
         <jsp:include page="body.jsp" flush="true" />
         </td></tr>
</table>
</body>
</html>

body.jsp contains html, jsp scriptlets and tags and calls to beans.

If body.jsp does not throw an exception, the page displays fine. 
However, if body.jsp throws an exception, the page only displays 
up to point A above.

If I comment out the include tag of header.jsp, a stack trace is 
displayed (as expected).

If I replace the include tag with code from the included 
header.jsp, a stack trace is displayed (as expected).

The problem only occurs when a) an exception is thrown from 
body.jsp and b) the header code is included via jsp:include 
instead of placed in-line.

Can anyone shed some light on this?

TIA,
Dave Jones
NetEffect