Tag Libraries

[Reinhard Pilz <rp...@faw.uni-linz.ac.at>]

After installing Tomcat3.0 from
http://jakarta.apache.org/builds/tomcat/release/v3.0/tomcat.zip
I had problems to use the <%@ taglib %> feature published in the JSP1.1
Specification.

Processing a .jsp file including tag libraries (e.g. by viewing the source
of the numguess example) caused the virtual machine throwing an exception
like this:

  Unhandled error! You might want to consider having an error page to report
such errors more gracefully
  java.lang.IllegalAccessError: try to access class
com/sun/xml/tree/ParentNode from class
  org/apache/jasper/compiler/TagLibraryInfoImpl
    at
org.apache.jasper.compiler.JspParseEventListener.handleDirective(JspParseEve
ntListener.java, Compiled Code)
      at
org.apache.jasper.compiler.JspParseEventListener.handleDirective(JspParseEve
ntListener.java, Compiled Code)
        at
org.apache.jasper.compiler.DelegatingListener.handleDirective(DelegatingList
ener.java:110)
        at org.apache.jasper.compiler.Parser$Directive.accept(Parser.java,
Compiled Code)
        at org.apache.jasper.compiler.Parser.parse(Parser.java, Compiled
Code)
        at org.apache.jasper.compiler.Parser.parse(Parser.java:959)
        at org.apache.jasper.compiler.Parser.parse(Parser.java:955)
        at org.apache.jasper.compiler.Compiler.compile(Compiler.java,
Compiled Code)
        at org.apache.jasper.runtime.JspLoader.loadJSP(JspLoader.java:226)
        at
org.apache.jasper.runtime.JspServlet$JspServletWrapper.loadIfNecessary(JspSe
rvlet.java:137)
        at
org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServlet.ja
va:148)
        at
org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet.java:247)
        at org.apache.jasper.runtime.JspServlet.service(JspServlet.java,
Compiled Code)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
        at
org.apache.tomcat.core.ServiceInvocationHandler.method(ServletWrapper.java:6
26)
        at
org.apache.tomcat.core.ServletWrapper.handleInvocation(ServletWrapper.java,
Compiled Code)
        at
org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java:378)
        at org.apache.tomcat.core.Context.handleRequest(Context.java:644)
        at
org.apache.tomcat.core.ContextManager.service(ContextManager.java:440)
        at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC
onnectionHandler.java:144)
        at
org.apache.tomcat.service.TcpConnectionThread.run(TcpEndpoint.java:304)
        at java.lang.Thread.run(Thread.java:479)

I could solve the problem by patching the xml.jar file (tomcat lib
directory).
As source code for these classes I used the source of the latest version of
the "Java[tm] Project X Technology Release 2"
(got it from http://developer.java.sun.com/developer/products/xml/)
By changing com.sun.xml.tree.ParentNode.class to public I was able prevent
the exception mentioned above.


My question now:

Is there another way than patching the libraries included in the tomcat 3.0
release?
I'm working with JDK1.2.2 and JBuilder3. - Could I possibly have made a
mistake when installing JDK, JBuilder or Tomcat?

Reinhard Pilz

Re: Tag Libraries

[Danno Ferrin <sh...@earthlink.net>]

The binary distribution has a binary error in one of the compiled classes,
but if you compile from one of the source distributions or from the CVS or
nightly builds you will not encounter this problem.

--Danno

"Reinhard Pilz" reitterated:
> After installing Tomcat3.0 from
> http://jakarta.apache.org/builds/tomcat/release/v3.0/tomcat.zip
> I had problems to use the <%@ taglib %> feature published in the JSP1.1
> Specification.
>
> Processing a .jsp file including tag libraries (e.g. by viewing the source
> of the numguess example) caused the virtual machine throwing an exception
> like this:
>
>   Unhandled error! You might want to consider having an error page to
report
> such errors more gracefully
>   java.lang.IllegalAccessError: try to access class
> com/sun/xml/tree/ParentNode from class
>   org/apache/jasper/compiler/TagLibraryInfoImpl
>     at
>
org.apache.jasper.compiler.JspParseEventListener.handleDirective(JspParseEve
> ntListener.java, Compiled Code)
>       at
>
org.apache.jasper.compiler.JspParseEventListener.handleDirective(JspParseEve
> ntListener.java, Compiled Code)
>         at
>
org.apache.jasper.compiler.DelegatingListener.handleDirective(DelegatingList
> ener.java:110)
>         at org.apache.jasper.compiler.Parser$Directive.accept(Parser.java,
> Compiled Code)
>         at org.apache.jasper.compiler.Parser.parse(Parser.java, Compiled
> Code)
>         at org.apache.jasper.compiler.Parser.parse(Parser.java:959)
>         at org.apache.jasper.compiler.Parser.parse(Parser.java:955)
>         at org.apache.jasper.compiler.Compiler.compile(Compiler.java,
> Compiled Code)
>         at org.apache.jasper.runtime.JspLoader.loadJSP(JspLoader.java:226)
>         at
>
org.apache.jasper.runtime.JspServlet$JspServletWrapper.loadIfNecessary(JspSe
> rvlet.java:137)
>         at
>
org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServlet.ja
> va:148)
>         at
> org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet.java:247)
>         at org.apache.jasper.runtime.JspServlet.service(JspServlet.java,
> Compiled Code)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
>         at
>
org.apache.tomcat.core.ServiceInvocationHandler.method(ServletWrapper.java:6
> 26)
>         at
>
org.apache.tomcat.core.ServletWrapper.handleInvocation(ServletWrapper.java,
> Compiled Code)
>         at
>
org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java:378)
>         at org.apache.tomcat.core.Context.handleRequest(Context.java:644)
>         at
> org.apache.tomcat.core.ContextManager.service(ContextManager.java:440)
>         at
>
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC
> onnectionHandler.java:144)
>         at
> org.apache.tomcat.service.TcpConnectionThread.run(TcpEndpoint.java:304)
>         at java.lang.Thread.run(Thread.java:479)
>
> I could solve the problem by patching the xml.jar file (tomcat lib
> directory).
> As source code for these classes I used the source of the latest version
of
> the "Java[tm] Project X Technology Release 2"
> (got it from http://developer.java.sun.com/developer/products/xml/)
> By changing com.sun.xml.tree.ParentNode.class to public I was able prevent
> the exception mentioned above.
>
>
> My question now:
>
> Is there another way than patching the libraries included in the tomcat
3.0
> release?
> I'm working with JDK1.2.2 and JBuilder3. - Could I possibly have made a
> mistake when installing JDK, JBuilder or Tomcat?
>
> Reinhard Pilz
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
>