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=13223>. 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=13223 JSP pages in XML syntax do not compile properly [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|DUPLICATE | ------- Additional Comments From [EMAIL PROTECTED] 2002-10-03 18:15 ------- On reading the spec more closely, I do not agree with the comment that this is (entirely) a spec bug. The spec, section 5.2.1 clearly states that the XML model supports a special attribute syntax for request-time expressions. The spec in 5.3.11 clarifies what that syntax is. The spec also clearly states, in section 5.3.1 that only 2 transformations are performed to map a JSP page in XML syntax to the XML view of that page. As far as the custom actions are concerned, the fact that they work in the non-XML syntax, coupled with the Spec' expression that they are equally valid within the XML syntax, implies that they should work in the same manner. Granted, the spec is unclear as to how non-expression items should be handled in XML syntax for attribute values, and this should be brought to the specification lead's attention, but it would seem reasonable to have Tomcat either document an expected manner of handling them (perhaps replacing the <> with < and >) and permit this usage while the spec group works out how this mechanism should be handled... If Tomcat is to be fully compliant with JSP 1.2, at the very least the specified XML expression syntax (attribute='%=item.getValue%') should be supported; as it is even this path is closed(the page processor completely ignores the expression and passes it through unprocessed). As a maximally useful tool, Tomcat would be best with the mechanism for handling standard actions within attribute values in the JSP syntax linked into the processing path for the XML syntax until the 1.2 spec can be clarified (or the issue is resolved in JSP 2.0). The notes on the similar bug 10683 indicate that something was brought up to the Spec group, but no response was heard. Since Tomcat is considered the reference implementation for the spec; would it perhaps be wise to keep a separate low-priority bug open here to ensure that the specification issue is tracked to resolution(and the clarification implemented) and to help regularly remind the specification group of the problem? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
