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 22867] New: - Tag handlers can't be inner/nested classes
Date Mon, 01 Sep 2003 22:01:40 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=22867>.
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=22867

Tag handlers can't be inner/nested classes

           Summary: Tag handlers can't be inner/nested classes
           Product: Tomcat 4
           Version: 4.1.24
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Jasper
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: gthb@dimon.is


When I try to use a nested class such as com.foo.MyTag$Bar as a tag handler,
the JSP-generated class fails compilation due to the use of names containing $
in source code. It says something like "perchance you meant com.foo.MyTag.Bar".
When I try replacing the $ with a . in the TLD file, it gives me this:

o.a.j.JasperException: /headlines.jsp(11,2) Unable to load class generator
  at o.a.j.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:94)
  at o.a.j.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:428)
  at o.a.j.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:219)
  at o.a.j.compiler.Parser.parseCustomTag(Parser.java:712)
  at o.a.j.compiler.Parser.parseElements(Parser.java:804)
  ...

(where I replaced org.apache.jasper with o.a.j to make the stack trace readable
in Bugzilla)

My exact same classes are working fine as tag handlers in the version of Tomcat
integrated into Borland Enterprise Server 5.2 (don't know what version that is,
nor which modifications they may have made, but it's certainly somewhat older
than Tomcat 4.1.24), but I'm seeing this failure in Tomcat 4.1.24 integrated
into JBoss 3.2.1. Thus I do not know for sure whether this problem is a result
of a classloader bug introduced by the JBoss integration (or one fixed by the
BES integration) or simply a Tomcat/Jasper bug that cropped up sometime between
these two versions.

I also don't know whether this should go to the Jasper component or the Jasper2
component (no version info in the jasper-compiler.jar and jasper-runtime.jar
manifest files)

Mime
View raw message