You don't have to copy all the files into common/lib, you can deploy them
with your web app (i.e. put them in WEB-INF/lib). The only thing that has to
be in common/endorsed are the files from %JWSDP_HOME%/jaxp/lib/endorsed.
I can't remember exactly what happens when you install JWSDP over a web
server, I believe that they replace the startup files (catalina.bat) and run
TC using a different app loader that sets up the classpath 'correctly', but
my memory may be mistaken, it's been a while since I looked,
Kevin Jones
http://public.xdi.org/=kevin.jones
skype (www.skype.com): kevinrjones
________________________________
From: Ryan Champlin [mailto:ryan.champlin_at_firstlogic.com]
Sent: 07 April 2005 20:00
To: users_at_jax-rpc.dev.java.net
Subject: Getting Tomcat to locate jars needed for Web Services
I see someone else posted a request on how to setup a standalone
(not incorporated into JWSDP) instance of Tomcat to run web services. The
solution was to copy all the needed JAX-RPC jar files in the common/lib
directory for tomcat. I haven't done thus but assumed it will work.
However, I'm trying to figure out how they did this in the JWSDP. I
don't see those files in the common/lib directory and I've been trying to
see if there is a config file in Tomcat that they've used to add these jar's
to the CLASSPATH. Anybody have any ideas?
I'd prefer not to copy all my jars over to the common lib but have
them picked up by Tomcat. It looks like I could do this in the
catalina.properties file.
However, the Tomcat shipped with JWSDP didn't do that. How did
they.
Thanks,
Ryan