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=35725>. 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=35725 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2005-07-15 05:08 ------- (In reply to comment #4) > I'm still unclear about something. > - You said "Entity resolution is done at translation time > (as required by the spec),", could you provide us which spec > and where( i.e. which section ) has this requirement ? <spec-quote spec="JSP" version="2.0" section="6.2.3"> The first step in processing a JSP document is to process it as an XML document, checking for well-formedness, processing entity resolution and, if applicable, performing validation as described in Section JSP.6.2.4. </spec-quote> > - Current jasper can resolve some entities(<, >, > ", &, ' ). I'd like to know why. > If what you said is correct, they should be also flagged as an > error. Why I'm asking is that I'd like to know how to > have Jasper recognize additional entities. ( adding something > to jsp:root tag ? or something like that. ) Doh, those are standard XML entities that all XML parsers recognize. Use them in (without escaping) your JSPX page, and you're toast ;-). Watch your browser choke on: <jsp:root xmlns:jsp=="http://java.sun.com/JSP/Page"; version="2.0"> <jsp:output omit-xml-declaration="no" doctype-root-element="html" doctype-public="-//W3C//DTD XHTML 1.1//EN" doctype-system="http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"/> <html> <body>Hello <World</body> </html> </jsp:root> > - When I tried the syntax "&#D;", jasper seems to recognize it. > (Note that according to HTML spec, this syntax is valid. ) > Is this shure that this syntax is also runnable for jasper ? Again, a standard XML entity. > Why I'm asking these is that current jasper accepts some > entities while it doesn't accept others so I'm wondering > what is the threshold for jasper to accept/not accept > entities. It's really simple: Jasper accepts the standard XML entities, as well as those defined in the internal and/or external DTD of the source document. And, of course, DTD declarations buried in CDATA sections don't count (they are nothing more than text Strings at translation time). But you are really missing the point: You don't want Jasper to resolve the XHTML entities at translation time. > Thank you very much. > . > . -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
