You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/09/30 19:07:00 UTC
DO NOT REPLY [Bug 13144] New: -
Scriplet comment breaks JSPs silently
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=13144>.
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=13144
Scriplet comment breaks JSPs silently
Summary: Scriplet comment breaks JSPs silently
Product: Tomcat 4
Version: 4.1.10
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Jasper
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: boris@folgmann.de
There are already some bug reports about // comments in scriplets in the bug
database. Here is another one that is really dangerous, because jasper compiles
those JSPs without complaining, but the generated Java source doesn't work as
expected. See my simplified example:
part of a JSP:
<% if (msg.send(user))
{ // ok %>
Message sent.<br>
<br>
<html:a href='index.jsp'>Ok</a><br><%
} %>
the following Java source is generated:
if (msg.send(user))
{ // ok out.write("\n Message sent.");
out.write("<br>\n ");
out.write("<br>\n\t");
[...]
That means that the text "Message sent." is not printed on the HTML-Page. This
is really a source for a lot of more serious problems.
This example used to work in tomcat 4.0 with 4.1.10 it doesn't. Is this problem
already fixed in a develeoper release?
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>