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/29 03:22:30 UTC
DO NOT REPLY [Bug 21168] New: -
Incorrect paths in generated SMAP file entries
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=21168>.
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=21168
Incorrect paths in generated SMAP file entries
Summary: Incorrect paths in generated SMAP file entries
Product: Tomcat 5
Version: 5.0.3
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: Other
Component: Jasper2
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: jph@us.ibm.com
One of the new features of Jasper in Tomcat 5 is that it attaches a "Source
Map" attribute to class files to describe the file name and line number
mapping from a JSP source file to the generated Java source file.
The SMAP that I see in the class files generated by Jasper (5.0.3 alpha)
has a couple of small problems:
1. The second line of the SMAP, according to JSR-45, is the name of the
generated source file. This name should be without path information,
but path information appears in the version generated by Jasper.
2. In the "*F" section, there's a pair of lines that defines the JSP file.
The second line is the source path for the JSP file. The path created
by Jasper contains a leading slash, making it an absolute path. It
should be relative; the leading slash should not appear.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org