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 21366] - A JSP-Servlet translation bug
Date Sat, 09 Aug 2003 16:32:16 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=21366>.
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=21366

A JSP-Servlet translation bug

ecarmich@alumni.rice.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Servlet & JSP API           |Jasper 2



------- Additional Comments From ecarmich@alumni.rice.edu  2003-08-09 16:32 -------
I have the same problem with Tomcat 5 (latest CVS) on Windows XP 
(j2sdk1.4.1_02 and j2sdk1.4.2). I can reproduce it consistently by compiling 
xml/xml.jsp from the jsp-examples webapp that ships with Tomcat 5.

The problem seems to be that the scriptlet text that 
org.apache.crimson.parser.InputEntity.parsedContent passes to 
JspDocumentParser.java's characters() method doesn't contain any line feeds. 
characters() is called separately for each line of the scriplet text, and 
dutifully creates TemplateText nodes for each line. Then 
Node.ScriptingElement's getText() method concatenates the text of the 
different TemplateText nodes into the text you see in the output .java file, 
still without any line feeds.

If that's intended behavior on the part of 
org.apache.crimson.parser.InputEntity.parsedContent, then this can be fixed by 
having Node.ScriptingElement's getText() method insert the necessary line 
feeds. But I note that the precompiled xml/xml_jsp.java that ships with Tomcat 
5 doesn't have this problem (which means it compiles correctly on _someone's_ 
machine), and the Platform given in the original bug report was "PC", same as 
my machine. So perhaps this is a Windows-only problem.

I don't have access to a non-Windows machine to develop or test on, so I don't 
think I can go any further with this. Can someone with more hardware and/or 
knowledge of XML parsers pick this up?

Also changing the Component from "Servlet & JSP API" to "Jasper 2", as this is 
a problem with Jasper or something Jasper relies on.

Mime
View raw message