The Jasper Engine is messing around with JSP ordering.
If in a servlet called FROM a JSP via a taglib, the servlet then
passes the control to anothr JSP, the latter JSP is output first. Note
that output from the servlet IS correctly placed.
Initial JSP:
<%@ taglib uri="Common" prefix="common" %>
<html><body><common:FormDay /></body></html>
Say, in the Common servlet there is:
pageContext.getOut().print("foo");
request.getRequestDispatcher("/secondary.jsp").include(request, response);
and secondary.jsp is:
<b>sometext</b>
Then the output will be:
<b>sometext</b>
<html><body>foo</body></html>
See how the secondary.jsp has been popped off the JSP stack first, yet
the servlet code is correctly positioned?
I trawled the archives, and there was a similar report back in 2001.
See:
http://mikal.org/interests/java/tomcat/archive/view?mesg=48825
From: [EMAIL PROTECTED]
Subject: Order of execution - JSP/RequestDispatcher include problem
Date: Wed, 5 Dec 2001 14:20:02 -0600
No answer though. Plenty of others have expressed similar problems, but
they have differing problem domains, so express their questions
differently. They boil down to the same JSP ordering issue though.
Any thoughts?
--
Terry Alexis Lurie
Software Engineer
Weboutcome Ltd.
____________________________
t: +44 (0)20 7953 7457
f: +44 (0)7092 123 230
m: +44 (0)7980 768 142
e: [EMAIL PROTECTED]
w: http://www.weboutcome.com
Unit 302, The Chandlery
50 Westminster Bridge Road
London SE1 7QY
____________________________
***This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you receive this message in error, please return it to the
sender.***
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
