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 2003/06/19 23:59:51 UTC

DO NOT REPLY [Bug 20821] - Wrong SMAP information generate

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=20821>.
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=20821

Wrong SMAP information generate

kin-man.chung@sun.com changed:

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



------- Additional Comments From kin-man.chung@sun.com  2003-06-19 21:59 -------
The SAMP may not what you want, but it is not wrong.  :-)

Take for instance line 43 of the Java code:

43       out.write("\n\t\tHello ");

Note that it starts with writing a '\n' character.  This means that the
beginning of this statement, the JSP line has not been advanced, so the mapping
is technically correct.

It could be argued that it would be more useful, for debugging, to break up the
above java code into two:

	out.write("\n");
	out.write("\t\tHello ");

But this is not the same issue.  In any case, this would increase the size of
the bytecode, so it has to be controlled with a compliation option.

To get around this "problem", write

<% String name= request.getParameter("name");
%> Hello 

instead.

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