So did the changes Sam made to break out the jaxrpc classes not help at all? Can someone who uses Tomcat 4 look in to this?
-- Tom Jordahl Macromedia -----Original Message----- From: Simon McClenahan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 13, 2002 12:26 PM To: Axis User (E-mail) Subject: Tomcat classloader issue I am running Tomcat 4.0.2 to host the AxisServlet. Whenever I build a new axis.jar, I place all the build jars in the %TOMCAT_HOME%\webapps\axis\WEB-INF\lib directory. As of about a month ago when I just started using Axis, it was discovered that Tomcat was not loading axis.jar and all sorts of errors occurred. The workaround is to place axis.jar in the %TOMCAT_HOME%\common\lib directory. Recently, the javax.rpc.* packages were archived into jaxrpc.jar . For some reason my services were working fine until yesterday I started getting errors with AdminClient. I blew away my axis webapp directory and removed axis.jar from ...\common\lib, did a fresh compile, etc. It turns out that both axis.jar and jaxrpc.jar need to be in ...\common\lib now. Which makes me wonder, all the other jars probably need to be in there too. Obviously this is a problem with Tomcat. The docs explaining class loading (locally with Tomcat running at http://localhost:8080/tomcat-docs/class-loader-howto.html ), and maybe I should put the jars in the Shared directory %TOMCAT_HOME%\lib instead of the Common directory. Could there be something wrong with the Tomcat configuration file, or is it a bug in Tomcat? In the mean-time, I'm going to copy ALL of the jars in the axis lib directory to the Tomcat shared lib directory until someone figures out what is going on here! cheers, Simon
