You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Theo <th...@visoft.co.za> on 2000/02/03 13:09:05 UTC
IllegalAccessError and Tags
Hi there
I can't get the Tag Extensions example to work with none of the builds using
windows NT.
I've tried to include additional XML jars (e.g. xml4j.jar), jdk1.3,
allow-all-policy files.
Does it actually work? It seems like the java.lang.IllegalAccessError is
caused my a call on a method that does not exists? Below a screen dump of
using tomcat.zip (3 Feb 2000) after a call to
http://127.0.0.1:8080/examples/jsp/simpletag/foo.jsp from the tag example
page.
Otherwise, viva Tomcat!
Thanks for a good product
Theo van Niekerk
----------
Using classpath:
.\classes;.\lib\webserver.jar;.\lib\servlet.jar;.\lib\jasper.jar;.\webpages\
WEB-INF\classes\jsp\beans;.
\lib\xml.jar;c:\java\jdk1.2.2\lib\tools.jar;.;
Automatic addContext( /examples, webapps/examples)
Automatic addContext( , webapps/ROOT)
Automatic addContext( /test, webapps/test)
Context(/examples): webapps/examples
Context(/examples): Loading -2147483646 jsp
Context(/examples): jsp: init
Context(/examples): Loading -2147483646 default
Context(/examples): default: init
Context(/test): webapps/test
Context(/test): Loading -2147483646 jsp
Context(/test): jsp: init
Context(/test): Loading -2147483646 default
Context(/test): default: init
Context(): webapps/ROOT
Context(): Loading -2147483646 jsp
Context(): jsp: init
Context(): Loading -2147483646 default
Context(): default: init
Starting tcp endpoint on 8080 with
org.apache.tomcat.service.http.HttpConnectionHandler
Starting tcp endpoint on 8007 with
org.apache.tomcat.service.connector.Ajp12ConnectionHandler
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/TagL
ibraryInfoImpl
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:1002)
at org.apache.jasper.compiler.Parser.parse(Parser.java:998)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java,
Compiled Code)
at org.apache.jasper.runtime.JspLoader.loadJSP(JspLoader.java:227)
at
org.apache.jasper.runtime.JspServlet$JspServletWrapper.loadIfNecessary(JspSe
rvlet.java:138)
at
org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServlet.ja
va:149)
at
org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet.java:256)
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.ServletWrapper.handleInvocation(ServletWrapper.java,
Compiled Code)
at
org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java:234)
at
org.apache.tomcat.core.ContextManager.service(ContextManager.java:367)
at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC
onnectionHandler.java:144)
at
org.apache.tomcat.service.TcpConnectionThread.run(TcpEndpoint.java:305)
at java.lang.Thread.run(Thread.java:479)
nightly build scripts (was: IllegalAccessError and Tags)
Posted by Danno Ferrin <sh...@earthlink.net>.
More follow-up on this for the build process....
Where are the tomcat zips being made? After seeing this error on two
(or more...) different binary releases it leads me to believe that this
error is being introduced by someting that can be changed and not by
random occurrence. Is the compiler jikes or the 1.3ea compiler? Is
there an old xml jar in the extensions? If it happens more than once it
can be nailed down.
--Danno
Theo wrote:
>
> Hi there
>
> I can't get the Tag Extensions example to work with none of the builds using
> windows NT.
> I've tried to include additional XML jars (e.g. xml4j.jar), jdk1.3,
> allow-all-policy files.
> Does it actually work? It seems like the java.lang.IllegalAccessError is
> caused my a call on a method that does not exists? Below a screen dump of
> using tomcat.zip (3 Feb 2000) after a call to
> http://127.0.0.1:8080/examples/jsp/simpletag/foo.jsp from the tag example
> page.
>
> Otherwise, viva Tomcat!
> Thanks for a good product
>
> Theo van Niekerk
>
> ----------
>
> Using classpath:
> .\classes;.\lib\webserver.jar;.\lib\servlet.jar;.\lib\jasper.jar;.\webpages\
> WEB-INF\classes\jsp\beans;.
> \lib\xml.jar;c:\java\jdk1.2.2\lib\tools.jar;.;
> Automatic addContext( /examples, webapps/examples)
> Automatic addContext( , webapps/ROOT)
> Automatic addContext( /test, webapps/test)
> Context(/examples): webapps/examples
> Context(/examples): Loading -2147483646 jsp
> Context(/examples): jsp: init
> Context(/examples): Loading -2147483646 default
> Context(/examples): default: init
> Context(/test): webapps/test
> Context(/test): Loading -2147483646 jsp
> Context(/test): jsp: init
> Context(/test): Loading -2147483646 default
> Context(/test): default: init
> Context(): webapps/ROOT
> Context(): Loading -2147483646 jsp
> Context(): jsp: init
> Context(): Loading -2147483646 default
> Context(): default: init
> Starting tcp endpoint on 8080 with
> org.apache.tomcat.service.http.HttpConnectionHandler
> Starting tcp endpoint on 8007 with
> org.apache.tomcat.service.connector.Ajp12ConnectionHandler
> 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/TagL
> ibraryInfoImpl
> 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:1002)
> at org.apache.jasper.compiler.Parser.parse(Parser.java:998)
> at org.apache.jasper.compiler.Compiler.compile(Compiler.java,
> Compiled Code)
> at org.apache.jasper.runtime.JspLoader.loadJSP(JspLoader.java:227)
> at
> org.apache.jasper.runtime.JspServlet$JspServletWrapper.loadIfNecessary(JspSe
> rvlet.java:138)
> at
> org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServlet.ja
> va:149)
> at
> org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet.java:256)
> 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.ServletWrapper.handleInvocation(ServletWrapper.java,
> Compiled Code)
> at
> org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java:234)
> at
> org.apache.tomcat.core.ContextManager.service(ContextManager.java:367)
> at
> org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC
> onnectionHandler.java:144)
> at
> org.apache.tomcat.service.TcpConnectionThread.run(TcpEndpoint.java:305)
> at java.lang.Thread.run(Thread.java:479)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: Few minor Q's for a ServerConnector
Posted by co...@eng.sun.com.
On Thu, 3 Feb 2000, Bob Jamison wrote:
> 1: Is implementing ServerConnector, getting the ContextManager
> from the setContextManager() call, and naming the Connector in server.xml,
> sufficient to bind the Connector to the rest of Tomcat to process
> Requests? I -think- it is, just want to make sure before I go down the
> wrong path.
We can add some magic words :-)
( you can get config parameters in setProperty if you need to ).
> 2: On the Apache side, is the call:
>
> ap_get_client_block(requestPtr,buffer,buffer_length);
>
> the proper place to get the information to feed the input stream
> of a RequestImpl? (For PUTs and POSTs)
Should work.
> 3: On the Apache side again, is the call:
>
> ap_write(write_buf,buf_length,requestPtr);
> the proper destination for the servletOutputStream of the ResponseImpl?
Yes.
Costin
Few minor Q's for a ServerConnector
Posted by Bob Jamison <rj...@lincom-asg.com>.
Hey, guys, I have a couple more questions about Tomcat and Apache.
I am making a Connector, and I need to get a few facts I have not been
able to get explicitly, after reading the source code (all of it, I think ;-)
1: Is implementing ServerConnector, getting the ContextManager
from the setContextManager() call, and naming the Connector in server.xml,
sufficient to bind the Connector to the rest of Tomcat to process
Requests? I -think- it is, just want to make sure before I go down the
wrong path.
2: On the Apache side, is the call:
ap_get_client_block(requestPtr,buffer,buffer_length);
the proper place to get the information to feed the input stream
of a RequestImpl? (For PUTs and POSTs)
3: On the Apache side again, is the call:
ap_write(write_buf,buf_length,requestPtr);
the proper destination for the servletOutputStream of the ResponseImpl?
Again, I think these are the ones, but I want to make sure. I should
have this Connector running roughly by the end of the week. When
it does, I'll post it, for whoever is interested.
Believe me, learning all about Apache modules, and Tomcat services,
has been a great education (whew!)
Bob Jamison
LinCom Corp
Re: IllegalAccessError and Tags
Posted by Danno Ferrin <sh...@earthlink.net>.
RTFFAQ
http://jakarta.apache.org/jyve-faq/Turbine/screen/DisplayQuestionAnswer/action/SetAll/project_id/2/faq_id/12/topic_id/43/question_id/235
Theo wrote:
>
> Hi there
>
> I can't get the Tag Extensions example to work with none of the builds using
> windows NT.
> I've tried to include additional XML jars (e.g. xml4j.jar), jdk1.3,
> allow-all-policy files.
> Does it actually work? It seems like the java.lang.IllegalAccessError is
> caused my a call on a method that does not exists? Below a screen dump of
> using tomcat.zip (3 Feb 2000) after a call to
> http://127.0.0.1:8080/examples/jsp/simpletag/foo.jsp from the tag example
> page.
>
> Otherwise, viva Tomcat!
> Thanks for a good product
>
> Theo van Niekerk
>
> ----------
>
> Using classpath:
> .\classes;.\lib\webserver.jar;.\lib\servlet.jar;.\lib\jasper.jar;.\webpages\
> WEB-INF\classes\jsp\beans;.
> \lib\xml.jar;c:\java\jdk1.2.2\lib\tools.jar;.;
> Automatic addContext( /examples, webapps/examples)
> Automatic addContext( , webapps/ROOT)
> Automatic addContext( /test, webapps/test)
> Context(/examples): webapps/examples
> Context(/examples): Loading -2147483646 jsp
> Context(/examples): jsp: init
> Context(/examples): Loading -2147483646 default
> Context(/examples): default: init
> Context(/test): webapps/test
> Context(/test): Loading -2147483646 jsp
> Context(/test): jsp: init
> Context(/test): Loading -2147483646 default
> Context(/test): default: init
> Context(): webapps/ROOT
> Context(): Loading -2147483646 jsp
> Context(): jsp: init
> Context(): Loading -2147483646 default
> Context(): default: init
> Starting tcp endpoint on 8080 with
> org.apache.tomcat.service.http.HttpConnectionHandler
> Starting tcp endpoint on 8007 with
> org.apache.tomcat.service.connector.Ajp12ConnectionHandler
> 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/TagL
> ibraryInfoImpl
> 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:1002)
> at org.apache.jasper.compiler.Parser.parse(Parser.java:998)
> at org.apache.jasper.compiler.Compiler.compile(Compiler.java,
> Compiled Code)
> at org.apache.jasper.runtime.JspLoader.loadJSP(JspLoader.java:227)
> at
> org.apache.jasper.runtime.JspServlet$JspServletWrapper.loadIfNecessary(JspSe
> rvlet.java:138)
> at
> org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServlet.ja
> va:149)
> at
> org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet.java:256)
> 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.ServletWrapper.handleInvocation(ServletWrapper.java,
> Compiled Code)
> at
> org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java:234)
> at
> org.apache.tomcat.core.ContextManager.service(ContextManager.java:367)
> at
> org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC
> onnectionHandler.java:144)
> at
> org.apache.tomcat.service.TcpConnectionThread.run(TcpEndpoint.java:305)
> at java.lang.Thread.run(Thread.java:479)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org