tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 10683] - some problems with JSP documents in xml syntax
Date Fri, 12 Jul 2002 23:59:51 GMT
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=10683>.
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=10683

some problems with JSP documents in xml syntax

jan.luehe@sun.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From jan.luehe@sun.com  2002-07-12 23:59 -------
a) SAX APIs don't support XML comments, and JSP spec does not require
   them to be preserved.


b) Fail to reproduce. When I access your page, I get this:

Request time attribute expressions don't seem to work in jsp documents, or maybe
I'm doing sth. wrong. According to the JSP spec. paragraph 5.3.11,
     the quoting convention used in jsp documents is as follows: However, the
expression inside the href attribute is not being evaluated. 
     If an xml element contains mixed content, e.g. plain text and other xml
elements, then the resulting output is not correct in every case. If plain text
     is directly preceding a taglib element, then the taglib output is written
to the jsp-outputstream prior to the plain text. For example, note that the
     following JSTL tag should deliver its output behind this text here, but
within the webpage the taglib output will appear first. THIS TEXT SHOULD NOT
     APPEAR FIRST. If however the plain text preceding a taglib element is
interleaved with other xml elements, as it is done here, then everything works
     fine again. TAGLIB TEXT See ? (And plain text behind a taglib element is
also save.) 
     In the resulting page, the javascript at the end of this page is missing.
The comment around the javascript part is needed by some browsers. I could
     place the body of the script element into a CDATA section but I believe
that it is a bug to erase xml comments from the source page. Also, if I would
     just place a jsp:text element arount the javascript, this would also erase
the xml comment. Unfortunately the JSP spec doesn't explicitly mention the
     treatment of xml comments and whether they should be erased or not. In
addition to that it is a pity that the SAX API's don't really report the
     occurence of xml comments. Only the org.xml.sax.ext.LexicalHelper does, but
it is an optional extension to SAX2 and can only be plugged in as an
     attribute to the parser. ;( 


c) Request-time attributes are not supported for "ordinary" XML
   elements (XML elements that are neither standard nor custom actions)
   in JSP documents (JSP pages in XML syntax).

   Section JSP.5.3.11, which you are referring to, deals with how
   request-time attributes in a JSP page in JSP syntax get mapped to the
   corresponding XML view of the page.

--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message