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/07/29 20:43:36 UTC
DO NOT REPLY [Bug 21978] New: -
Certain tag file pathnames lead to compile errors
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=21978>.
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=21978
Certain tag file pathnames lead to compile errors
Summary: Certain tag file pathnames lead to compile errors
Product: Tomcat 5
Version: Nightly Build
Platform: All
OS/Version: All
Status: NEW
Severity: Minor
Priority: Other
Component: Jasper2
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: ecarmich@alumni.rice.edu
Tomcat can't compile certain tag files:
1) Tag files whose relative pathname contains a component (one of the
directories, or the filename without the ".tag" suffix) which is not a legal
Java identifier. Tomcat converts the relative pathname to a fully-qualified
class name, and if the parts aren't all legal Java identifiers, the Java
compiler will throw an error.
2) Tag files in /<some_directories>/<immediate_parent_directory>/ when there's
a tag file in /<some_directories>/ with
filename "<immediate_parent_directory>.tag". Here the problem is that the
package of the tag files in /<some_directories>/<immediate_parent_directory>/
clashes with the class of the "<immediate_parent_directory>.tag" tag file.
For instance, the tag file /WEB-INF/tags/foo/bar.tag will have package name
org.apache.jsp.tag.web.foo, which conflicts with the fully-qualified class
name of the tag file /WEB-INF/tags/foo.tag.
I will attach a patch that fixes this.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org