DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=31316>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31316 Tomcat 5 rejects <jsp:include ....></jsp:include> Summary: Tomcat 5 rejects <jsp:include ....></jsp:include> Product: Tomcat 5 Version: 5.0.28 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Servlet & JSP API AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] In porting an app from Tomcat 4.1.30 to Tomcat 5.0.28 we discovered that the following JSP text no longer works: <jsp:include page="departments.jsp" flush="false"></jsp:include> It throws a JasperException: org.apache.jasper.JasperException: /index.jsp(374,0) Expecting "jsp:param" standard action with "name" and "value" attributes unless the text is changed to <jsp:include page="departments.jsp" flush="false"/> The change in behavior seems to violate the old (1.2) and new (2.0) JSP specs, which both say: A jsp:include action may have jsp:param subelements that can provide values for some parameters in the request to be used for the inclusion. i.e. it *may* have <jsp:param> subelements (it doesn't insist on them). Even the syntax description (on page 1-110 of the 2.0 spec) explicitly permits omitting <jsp:param> when opening and closing jsp:include tags are used instead of <jsp:include ... />: <jsp:include page="urlSpec" flush="true|false"> { <jsp:param ..../> }* </jsp:include> In any case the change in behavior is problematic for people porting applications. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
