DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20894>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20894 body-content value of "JSP" should be error if SimpleTag Summary: body-content value of "JSP" should be error if SimpleTag Product: Tomcat 5 Version: Nightly Build Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Jasper2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] According to JSP 2.0 PFD3, JSP.7.1.5, "The body of a Simple Tag, if present, is translated into a JSP Fragment and passed to the setJspBody method." According to JSP 2.0 PFD3, JSP.7.1.6, "A translation error must occur if a piece of JSP code that is to be translated into a JSP Fragment contains scriptlets or scriptlet expressions." There is nothing that explicitly requires that a <body-content> of "JSP" in the TLD for a SimpleTag must produce an error. However, this is technically invalid, and the JSP 2.0 specification will now say that it such a TLD will be considered invalid. It would be very helpful for tag library developers if Tomcat can flag such an error right away and indicate that the TLD is invalid for that reason. This can take the form of a translation error, for example. This would be symmetrical with the current treatment of body-content="JSP" in Tag Files (which is currently explicitly required to produce a translation error). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
