Sure enough, those classpaths are missing jaxrpc.jar. Ivan raises a good point for those who are trying to take my advice during an Axis install -- I didn't do a very thorough test of the client side installation at all. I can vouch for my results as far as installing the webapp into Tomcat, but I did my testing with a different service and a separate client installation.
-- Nathan D. Bowen [EMAIL PROTECTED] On Sat, Apr 13, 2002 at 12:52:50AM -0700, Ivan Filippenko wrote: > Yes, thank you again Nathan for your thorough and helpful analysis > of the AXIS/Tomcat installation and version match-up issues. > > However, I have to take one small exception to your remark: > > > With an out-of-the-box Tomcat 4.0.1 or Tomcat 4.0.4-b2, I can install a > > perfectly functioning out-of-the-box Axis according to the installation > > documentation provided. > > In my experience, not quite. Step 5 of the xml-axis-beta1 install.html > fails to include jaxrpc.jar among the files that are instructed to be > placed on the system classpath (the others mentioned being axis.jar, > commons-logging.jar, log4j-core.jar, tt-bytecode.jar, and XML parser > jar files). > > Without jaxrpc.jar on the classpath, I get a NoClassDefFoundError > for javax/xml/soap/SOAPElement when attempting command-line deployment > of a web service as described in that step, since jaxrpc.jar contains > that class. > > At least it remains true, as you state, that with Tomcat 4.0.4-b2-01 > there is no need for copying jar files from the webapps directories > to tomcat /lib directories. This is indeed a good thing. > > Just wanted to note that one omission in the AXIS install instructions, > since it caused me a little hiccup. > > Best regards, > > -- Ivan
