Important: RE: [TC3.3b1](=? TC3.3rc1) use of taglib causes org.apache.crimson.jaxp.DocumentBuilderFactoryImpl not found error
I have the same problem, but I'm just using raw JSPs, no Jetspeed or
anything.
Further, I thought that Tomcat 3.3 (later builds) was supposed to solve the
problems with
mixed XML parsers. The problem I get is when a JSP includes some other
JSP via jsp:include. What ~seems~ to be happening is that the included
JSP
gets compiled using the ClassLoader of the WebApp rather than Tomcat's
ClassLoader
so that if the XML parser you're using is incompatible there'll be a
problem.
Is there a Tomcat developer out there who can help?
Thanks a lot,
Huw
-Original Message-
From: Paul Spencer [mailto:[EMAIL PROTECTED]]
Sent: 01 September 2001 22:42
To: [EMAIL PROTECTED]
Subject: Re: [TC3.3b1] use of taglib causes
org.apache.crimson.jaxp.DocumentBuilderFactoryImpl not found error
I have made the changes suggested. I still get the same errors.
The jsp file will work when referenced directly,
http://localhost/jetspeed/hello.jsp, but fails when it is executed by
Jetspeed.
This problem is does not occur in Tomcat 3.3-m4 or Tomcat 4.0-b7. I
suspect something that was changed between 3.3-m4 and 3.3-b1
is causing
the problem, but I do not know what it is :-(. I do not believe the
problem is with Jetspeed because I used the same WAR file when testing
all 3 versions of Tomcat.
The error message may not be related to the actual error. The empty
.java file in the work directory may be the closer to the problem.
Maybe somewhere in the process of converting from .jsp to .java when a
taglib is defined.
I enabled debug logging.
No entries on the servlet logfile
The jasper log contained:
2001-09-01 17:29:25 - Package name is:
WEB_0002dINF.templates.jsp.portlets.html
2001-09-01 17:29:25 - Class file name is:
E:\apache\jakarta-tomcat-3.3-b1\work\DEFAULT\jetspeed\WEB_0002
dINF\templates\jsp\portlets\html\Example_1.class
2001-09-01 17:29:25 - Java file name is:
E:\apache\jakarta-tomcat-3.3-b1\work\DEFAULT\jetspeed\WEB_0002
dINF\templates\jsp\portlets\html\Example_1.java
2001-09-01 17:29:25 - Class name is: Example_1
2001-09-01 17:29:25 -
Handling Directive: taglib
{uri=/WEB-INF/templates/jsp/tld/template.tld,
prefix=jetspeed}
Ideas?
Paul Spencer
Will Stranathan wrote:
Take the XML related jars in TOMCAT_HOME/lib and rename them to
x[whatever].jar (for example, xjaxp.jar). Then put Velocity's XML
parsers in TOMCAT_HOME/lib.
I know it's a kludge, but AFAICT, these sorts of
classloader issues have
been corrected in 4.0. (Which is all the Struts people
can't understand
why their stuff suddenly DOESN'T work - all the Struts WAR's come
without any parser libraries.)
w
Paul Spencer wrote:
I am getting the following error while using Jetspeed with Tomcat
3.3-b1. This error does NOT occur in Tomcat 3.3-m4!
[Fri Aug 31 22:19:33 EDT 2001] -- ERROR -- Error
rendering Velocity
template: /controllers/html/multicolumn.vm: Invocation of method
'getContent' in class
org.apache.jetspeed.portal.controls.VelocityPortletControl threw
exception class javax.xml.parsers.FactoryConfigurationError :
Provider
org.apache.crimson.jaxp.DocumentBuilderFactoryImpl not found
In addition the .java file created in the work directory
is has a size
of 0 bytes.
I copied crimson.jar and jaxp.jar to the lib/apps directory, as
suggested in
http://www.mail-archive.com/tomcat-dev@jakarta.apache.org/msg1
3224.html
,
but that did not work.
My jsp file is below (Note this file work in Tomcat v3.3-m3 and -m4):
%@ taglib uri='/WEB-INF/templates/jsp/tld/template.tld'
prefix='jetspeed' %
p
bJSP/b Hello World!
bServer date:/b jetspeed:info requestedInfo=ServerDate /
/p
Ideas?
Thank you
Paul Spencer
The information in this email is confidential and is intended solely
for the addressee(s).
Access to this email by anyone else is unauthorised. If you are not
an intended recipient, you must not read, use or disseminate the
information contained in the email.
Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be
the views of Capco.
http://www.capco.com
***
RE: Important: RE: [TC3.3b1](=? TC3.3rc1) use of taglib causes org.apache.crimson.jaxp.DocumentBuilderFactoryImpl not found error
This a known problem that suffered rc1, test gainst rc2 this should be
solved..
Saludos ,
Ignacio J. Ortega
-Mensaje original-
De: Roberts Huw [mailto:[EMAIL PROTECTED]]
Enviado el: jueves 18 de octubre de 2001 11:21
Para: '[EMAIL PROTECTED]'
Asunto: Important: RE: [TC3.3b1](=? TC3.3rc1) use of taglib causes
org.apache.crimson.jaxp.DocumentBuilderFactoryImpl not found error
I have the same problem, but I'm just using raw JSPs, no Jetspeed or
anything.
Further, I thought that Tomcat 3.3 (later builds) was
supposed to solve the
problems with
mixed XML parsers. The problem I get is when a JSP includes
some other
JSP via jsp:include. What ~seems~ to be happening is that
the included
JSP
gets compiled using the ClassLoader of the WebApp rather than Tomcat's
ClassLoader
so that if the XML parser you're using is incompatible there'll be a
problem.
Is there a Tomcat developer out there who can help?
Thanks a lot,
Huw
-Original Message-
From: Paul Spencer [mailto:[EMAIL PROTECTED]]
Sent: 01 September 2001 22:42
To: [EMAIL PROTECTED]
Subject: Re: [TC3.3b1] use of taglib causes
org.apache.crimson.jaxp.DocumentBuilderFactoryImpl not found error
I have made the changes suggested. I still get the same errors.
The jsp file will work when referenced directly,
http://localhost/jetspeed/hello.jsp, but fails when it is
executed by
Jetspeed.
This problem is does not occur in Tomcat 3.3-m4 or Tomcat 4.0-b7. I
suspect something that was changed between 3.3-m4 and 3.3-b1
is causing
the problem, but I do not know what it is :-(. I do not believe the
problem is with Jetspeed because I used the same WAR file
when testing
all 3 versions of Tomcat.
The error message may not be related to the actual error. The empty
.java file in the work directory may be the closer to the problem.
Maybe somewhere in the process of converting from .jsp to
.java when a
taglib is defined.
I enabled debug logging.
No entries on the servlet logfile
The jasper log contained:
2001-09-01 17:29:25 - Package name is:
WEB_0002dINF.templates.jsp.portlets.html
2001-09-01 17:29:25 - Class file name is:
E:\apache\jakarta-tomcat-3.3-b1\work\DEFAULT\jetspeed\WEB_0002
dINF\templates\jsp\portlets\html\Example_1.class
2001-09-01 17:29:25 - Java file name is:
E:\apache\jakarta-tomcat-3.3-b1\work\DEFAULT\jetspeed\WEB_0002
dINF\templates\jsp\portlets\html\Example_1.java
2001-09-01 17:29:25 - Class name is: Example_1
2001-09-01 17:29:25 -
Handling Directive: taglib
{uri=/WEB-INF/templates/jsp/tld/template.tld,
prefix=jetspeed}
Ideas?
Paul Spencer
Will Stranathan wrote:
Take the XML related jars in TOMCAT_HOME/lib and rename them to
x[whatever].jar (for example, xjaxp.jar). Then put Velocity's XML
parsers in TOMCAT_HOME/lib.
I know it's a kludge, but AFAICT, these sorts of
classloader issues have
been corrected in 4.0. (Which is all the Struts people
can't understand
why their stuff suddenly DOESN'T work - all the Struts WAR's come
without any parser libraries.)
w
Paul Spencer wrote:
I am getting the following error while using Jetspeed
with Tomcat
3.3-b1. This error does NOT occur in Tomcat 3.3-m4!
[Fri Aug 31 22:19:33 EDT 2001] -- ERROR -- Error
rendering Velocity
template: /controllers/html/multicolumn.vm:
Invocation of method
'getContent' in class
org.apache.jetspeed.portal.controls.VelocityPortletControl threw
exception class javax.xml.parsers.FactoryConfigurationError :
Provider
org.apache.crimson.jaxp.DocumentBuilderFactoryImpl not found
In addition the .java file created in the work directory
is has a size
of 0 bytes.
I copied crimson.jar and jaxp.jar to the lib/apps directory, as
suggested in
http://www.mail-archive.com/tomcat-dev@jakarta.apache.org/msg1
3224.html
,
but that did not work.
My jsp file is below (Note this file work in Tomcat
v3.3-m3 and -m4):
%@ taglib uri='/WEB-INF/templates/jsp/tld/template.tld'
prefix='jetspeed' %
p
bJSP/b Hello World!
bServer date:/b jetspeed:info
requestedInfo=ServerDate /
/p
Ideas?
Thank you
Paul Spencer
**
**
The information in this email is confidential and is intended solely
for the addressee(s).
Access to this email by anyone else is unauthorised. If you are not
an intended recipient, you must not read, use or disseminate the
information contained in the email.
Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be
the views of Capco.
http://www.capco.com
**
*
