You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Heitzso <he...@bellsouth.net> on 2002/07/25 16:59:10 UTC
classloader/dll/hell help request
Could someone comment on the official recommended best
practice re placing axis and xerces jars in the following
environment:
sun jdk 1.4.0_01
tomcat 4.0.4
axis beta 3 (though could easily use nightly drop)
(and what are the known differences between the above on
Win2k and Linux)
I've tried most every variation in the book and hit or
miss depending on jdk, os, etc. and often get everything
working just great for one combo and find it breaking
another. Right now I just have to get the above setup
flying right.
Directories to put things in (note that I'm not using
the axis webapp, but rather we have our own named
TheDataWeb_Services).
TheDataWeb_Services/WEB-INF/lib
jakarta-tomcat-4.0.4/common/lib
java.endorsed.dirs (with -Djava.endorsed.dirs=blat)
I've tried all of the above at once!!! and just about
every combo conceivable. For instance, copying all of axis/lib
jars over the common/lib and WEB-INF/lib and using
-Djava.endorsed.dirs=jakarta-etc/common/lib which blows up
rather spectacularly. I'm now breaking down and asking ...
what's the official recommended layout?
Thanks!!!
Heitzso
Re: classloader/dll/hell help request
Posted by marco <sf...@hotmail.com>.
Heitzso,
Same overhere.
On Tomcat 4.0.4 you can leave the jar files in the axis/web-app/lib
directory
The validate output note
"On Tomcat 4.x, you may need to put libraries that contain java.* or
javax.* packages into CATALINA_HOME/commons/lib"
does not seems to apply for Tomcat 4.0.4
I do get the warning message
Warning: could not find resource server-config.wsdd
There is no a server configuration file;run AdminClient to create one
But server-config.wsdd is generted and is working fine. So I suspect that
the warning message is not valid
Here is my validate output:
Examining webapp configuration
Needed Components
Found SAAJ API (javax.xml.soap.SOAPMessage) at E:\Program Files\Apache
Tomcat 4.0\webapps\axis\WEB-INF\lib\saaj.jar
Found JAX-RPC API (javax.xml.rpc.Service) at E:\Program Files\Apache Tomcat
4.0\webapps\axis\WEB-INF\lib\jaxrpc.jar
Found Apache-Axis (org.apache.axis.transport.http.AxisServlet) at E:\Program
Files\Apache Tomcat 4.0\webapps\axis\WEB-INF\lib\axis.jar
Found Jakarta-commons logging (org.apache.commons.logging.Log) at E:\Program
Files\Apache Tomcat 4.0\webapps\axis\WEB-INF\lib\commons-logging.jar
Found IBM's WSDL4Java (com.ibm.wsdl.factory.WSDLFactoryImpl) at E:\Program
Files\Apache Tomcat 4.0\webapps\axis\WEB-INF\lib\wsdl4j.jar
Found JAXP implementation (javax.xml.parsers.SAXParserFactory)
Found Activation API (javax.activation.DataHandler) at E:\Program
Files\Apache Tomcat 4.0\common\lib\activation.jar
Optional Components
Found Mail API (javax.mail.internet.MimeMessage) at E:\Program Files\Apache
Tomcat 4.0\common\lib\mail.jar
Warning: could not find class org.apache.xml.security.Init from file
xmlsec.jar
Attachments will not work
See http://xml.apache.org/security/
Warning: could not find resource server-config.wsdd
There is no a server configuration file;run AdminClient to create oneThe
core axis libraries are present. 1 optional axis library is missing
Note: On Tomcat 4.x, you may need to put libraries that contain java.* or
javax.* packages into CATALINA_HOME/commons/lib
----- Original Message -----
From: "Robert Herold" <he...@cotagesoft.com>
To: <ax...@xml.apache.org>
Sent: Thursday, July 25, 2002 9:15 AM
Subject: RE: classloader/dll/hell help request
> I am using your exact configuration (sun jdk 1.4.0_01, tomcat 4.0.4, axis
> beta 3) on Windows XP. No jars are installed in tomcat/common/lib beyond
> the stock tomcat jars (except for oracle's jdbc drivers classes12.zip).
All
> other jars are in tomcat/webapps/mywebapp/WEB-INF/lib, including:
>
> axis.jar
> commons-logging.jar
> jaxrpc.jar
> log4j.jar (renamed from log4j-1.2.4.jar)
> saaj.jar
> tt-bytecode.jar
> wsdl4j.jar
>
> I also have log4j.xml in WEB-INF/classes.
>
> Everything works fine. I've not tried Linux, however.
>
> It's important to note that this setup doesn't work in Tomcat 4.0.3 - the
> classloader setup would refuse to load *any* javax.whatever package from
> WEB-INF/lib, instead of just the Sun-specified untouchable packages.
>
> -- bob
>
> -----Original Message-----
> From: axis-user-return-5716-herold=cotagesoft.com@xml.apache.org
> [mailto:axis-user-return-5716-herold=cotagesoft.com@xml.apache.org]On
> Behalf Of Heitzso
> Sent: Thursday, July 25, 2002 7:59 AM
> To: axis-user@xml.apache.org
> Subject: classloader/dll/hell help request
>
>
> Could someone comment on the official recommended best
> practice re placing axis and xerces jars in the following
> environment:
>
> sun jdk 1.4.0_01
> tomcat 4.0.4
> axis beta 3 (though could easily use nightly drop)
>
> (and what are the known differences between the above on
> Win2k and Linux)
>
> I've tried most every variation in the book and hit or
> miss depending on jdk, os, etc. and often get everything
> working just great for one combo and find it breaking
> another. Right now I just have to get the above setup
> flying right.
>
> Directories to put things in (note that I'm not using
> the axis webapp, but rather we have our own named
> TheDataWeb_Services).
>
> TheDataWeb_Services/WEB-INF/lib
> jakarta-tomcat-4.0.4/common/lib
> java.endorsed.dirs (with -Djava.endorsed.dirs=blat)
>
> I've tried all of the above at once!!! and just about
> every combo conceivable. For instance, copying all of axis/lib
> jars over the common/lib and WEB-INF/lib and using
> -Djava.endorsed.dirs=jakarta-etc/common/lib which blows up
> rather spectacularly. I'm now breaking down and asking ...
>
> what's the official recommended layout?
>
> Thanks!!!
> Heitzso
>
RE: classloader/dll/hell help request
Posted by Heitzso <he...@bellsouth.net>.
Robert,
Thank you. I used your layout as a guideline with the exception
of the typo re log4j.xml (should be log4j.properties) and was up
and running again in Debian unstable. Moved same setup to RH7.3
and it broke on a xerces class problem so deleted tomcat
4.0.4/common/lib/xerces.jar and replaced with current xerces 2
jars (2 of them) in the common/lib directory and I'm now running
fine on two key linux boxes. I haven't tried running this setup
on my winXX systems but will hold to this baseline that's working.
Recap:
compiled my code with jikes 1.15 using rt.jar from 1.4.0_01
jvm sun 1.4.0_01
axis beta 3
tomcat 4.0.4
axis lib jars (all of them) copied to my WEB-INF/lib
left common/lib alone except for swap out xerces 2 (2 jars)
no additional classpath
no java.endorsed.dirs
Thanks again,
Heitzso
On Thu, 2002-07-25 at 12:15, Robert Herold wrote:
> I am using your exact configuration (sun jdk 1.4.0_01, tomcat 4.0.4, axis
> beta 3) on Windows XP. No jars are installed in tomcat/common/lib beyond
> the stock tomcat jars (except for oracle's jdbc drivers classes12.zip). All
> other jars are in tomcat/webapps/mywebapp/WEB-INF/lib, including:
>
> axis.jar
> commons-logging.jar
> jaxrpc.jar
> log4j.jar (renamed from log4j-1.2.4.jar)
> saaj.jar
> tt-bytecode.jar
> wsdl4j.jar
>
> I also have log4j.xml in WEB-INF/classes.
>
> Everything works fine. I've not tried Linux, however.
>
> It's important to note that this setup doesn't work in Tomcat 4.0.3 - the
> classloader setup would refuse to load *any* javax.whatever package from
> WEB-INF/lib, instead of just the Sun-specified untouchable packages.
>
> -- bob
>
> -----Original Message-----
> From: axis-user-return-5716-herold=cotagesoft.com@xml.apache.org
> [mailto:axis-user-return-5716-herold=cotagesoft.com@xml.apache.org]On
> Behalf Of Heitzso
> Sent: Thursday, July 25, 2002 7:59 AM
> To: axis-user@xml.apache.org
> Subject: classloader/dll/hell help request
>
>
> Could someone comment on the official recommended best
> practice re placing axis and xerces jars in the following
> environment:
>
> sun jdk 1.4.0_01
> tomcat 4.0.4
> axis beta 3 (though could easily use nightly drop)
>
> (and what are the known differences between the above on
> Win2k and Linux)
>
> I've tried most every variation in the book and hit or
> miss depending on jdk, os, etc. and often get everything
> working just great for one combo and find it breaking
> another. Right now I just have to get the above setup
> flying right.
>
> Directories to put things in (note that I'm not using
> the axis webapp, but rather we have our own named
> TheDataWeb_Services).
>
> TheDataWeb_Services/WEB-INF/lib
> jakarta-tomcat-4.0.4/common/lib
> java.endorsed.dirs (with -Djava.endorsed.dirs=blat)
>
> I've tried all of the above at once!!! and just about
> every combo conceivable. For instance, copying all of axis/lib
> jars over the common/lib and WEB-INF/lib and using
> -Djava.endorsed.dirs=jakarta-etc/common/lib which blows up
> rather spectacularly. I'm now breaking down and asking ...
>
> what's the official recommended layout?
>
> Thanks!!!
> Heitzso
>
>
>
RE: classloader/dll/hell help request
Posted by Robert Herold <he...@cotagesoft.com>.
One more thing: I don't set a classpath in the system environment
variables - instead I just let the Tomcat startup script set it.
-----Original Message-----
From: axis-user-return-5730-herold=cotagesoft.com@xml.apache.org
[mailto:axis-user-return-5730-herold=cotagesoft.com@xml.apache.org]On
Behalf Of Robert Herold
Sent: Thursday, July 25, 2002 9:15 AM
To: axis-user@xml.apache.org
Subject: RE: classloader/dll/hell help request
I am using your exact configuration (sun jdk 1.4.0_01, tomcat 4.0.4, axis
beta 3) on Windows XP. No jars are installed in tomcat/common/lib beyond
the stock tomcat jars (except for oracle's jdbc drivers classes12.zip). All
other jars are in tomcat/webapps/mywebapp/WEB-INF/lib, including:
axis.jar
commons-logging.jar
jaxrpc.jar
log4j.jar (renamed from log4j-1.2.4.jar)
saaj.jar
tt-bytecode.jar
wsdl4j.jar
I also have log4j.xml in WEB-INF/classes.
Everything works fine. I've not tried Linux, however.
It's important to note that this setup doesn't work in Tomcat 4.0.3 - the
classloader setup would refuse to load *any* javax.whatever package from
WEB-INF/lib, instead of just the Sun-specified untouchable packages.
-- bob
-----Original Message-----
From: axis-user-return-5716-herold=cotagesoft.com@xml.apache.org
[mailto:axis-user-return-5716-herold=cotagesoft.com@xml.apache.org]On
Behalf Of Heitzso
Sent: Thursday, July 25, 2002 7:59 AM
To: axis-user@xml.apache.org
Subject: classloader/dll/hell help request
Could someone comment on the official recommended best
practice re placing axis and xerces jars in the following
environment:
sun jdk 1.4.0_01
tomcat 4.0.4
axis beta 3 (though could easily use nightly drop)
(and what are the known differences between the above on
Win2k and Linux)
I've tried most every variation in the book and hit or
miss depending on jdk, os, etc. and often get everything
working just great for one combo and find it breaking
another. Right now I just have to get the above setup
flying right.
Directories to put things in (note that I'm not using
the axis webapp, but rather we have our own named
TheDataWeb_Services).
TheDataWeb_Services/WEB-INF/lib
jakarta-tomcat-4.0.4/common/lib
java.endorsed.dirs (with -Djava.endorsed.dirs=blat)
I've tried all of the above at once!!! and just about
every combo conceivable. For instance, copying all of axis/lib
jars over the common/lib and WEB-INF/lib and using
-Djava.endorsed.dirs=jakarta-etc/common/lib which blows up
rather spectacularly. I'm now breaking down and asking ...
what's the official recommended layout?
Thanks!!!
Heitzso
RE: classloader/dll/hell help request
Posted by Robert Herold <he...@cotagesoft.com>.
I am using your exact configuration (sun jdk 1.4.0_01, tomcat 4.0.4, axis
beta 3) on Windows XP. No jars are installed in tomcat/common/lib beyond
the stock tomcat jars (except for oracle's jdbc drivers classes12.zip). All
other jars are in tomcat/webapps/mywebapp/WEB-INF/lib, including:
axis.jar
commons-logging.jar
jaxrpc.jar
log4j.jar (renamed from log4j-1.2.4.jar)
saaj.jar
tt-bytecode.jar
wsdl4j.jar
I also have log4j.xml in WEB-INF/classes.
Everything works fine. I've not tried Linux, however.
It's important to note that this setup doesn't work in Tomcat 4.0.3 - the
classloader setup would refuse to load *any* javax.whatever package from
WEB-INF/lib, instead of just the Sun-specified untouchable packages.
-- bob
-----Original Message-----
From: axis-user-return-5716-herold=cotagesoft.com@xml.apache.org
[mailto:axis-user-return-5716-herold=cotagesoft.com@xml.apache.org]On
Behalf Of Heitzso
Sent: Thursday, July 25, 2002 7:59 AM
To: axis-user@xml.apache.org
Subject: classloader/dll/hell help request
Could someone comment on the official recommended best
practice re placing axis and xerces jars in the following
environment:
sun jdk 1.4.0_01
tomcat 4.0.4
axis beta 3 (though could easily use nightly drop)
(and what are the known differences between the above on
Win2k and Linux)
I've tried most every variation in the book and hit or
miss depending on jdk, os, etc. and often get everything
working just great for one combo and find it breaking
another. Right now I just have to get the above setup
flying right.
Directories to put things in (note that I'm not using
the axis webapp, but rather we have our own named
TheDataWeb_Services).
TheDataWeb_Services/WEB-INF/lib
jakarta-tomcat-4.0.4/common/lib
java.endorsed.dirs (with -Djava.endorsed.dirs=blat)
I've tried all of the above at once!!! and just about
every combo conceivable. For instance, copying all of axis/lib
jars over the common/lib and WEB-INF/lib and using
-Djava.endorsed.dirs=jakarta-etc/common/lib which blows up
rather spectacularly. I'm now breaking down and asking ...
what's the official recommended layout?
Thanks!!!
Heitzso