Check for spurious soap.jar, such as soap.jar in $JAVA_HOME/jre/lib/ext or in a catalina.[sh|bat] classpath. If the Apache SOAP classes get loaded from outside the webapp, they cannot load the service classes from the webapp.
Scott Nichol Do not send e-mail directly to this e-mail address, because it is filtered to accept only mail from specific mail lists. ----- Original Message ----- From: "Malte Kempff" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, August 27, 2003 12:45 PM Subject: AW: Trouble with BadTargetObjectURI / ClassNotFoundException > Hi Scott, > thanks for your reply. The thing is, that we did it as you have said, but we > got the BadTargetObjectURI / ClassNotFoundException. The usual Soap-tests > worked fine like they are to be read in the soap-docs. > The $CATALINA_HOME/webapps/soap/WEB-INF/lib] containes the needed .jar's, > so it is not clear to me why the class holding the RPCs is not found. > > > Malte > > -----Ursprüngliche Nachricht----- > Von: Scott Nichol [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 27. August 2003 17:14 > An: [EMAIL PROTECTED] > Betreff: Re: Trouble with BadTargetObjectURI / ClassNotFoundException > > > Here is what I typically do. > > 1. Stop Tomcat. > > 2. Manually explode soap.war into $CATALINA_HOME/webapps/soap. I do it > manually even though Tomcat will do the same thing if soap.war is placed in > $CATALINA_HOME/webapps, because I also add/change files in > $CATALINA_HOME/webapps/soap/WEB-INF/[classes|lib], which is not supported on > all servlet containers when you let them explode the .war for you. > > 3. Put my service classes and jars into > $CATALINA_HOME/webapps/soap/WEB-INF/[classes|lib]. > > 4. Start Tomcat. > > 5. Deploy services. > > Scott Nichol > > Do not send e-mail directly to this e-mail address, > because it is filtered to accept only mail from > specific mail lists. > ----- Original Message ----- > From: "Malte Kempff" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, August 27, 2003 6:36 AM > Subject: Trouble with BadTargetObjectURI / ClassNotFoundException > > > > Hello, > > I have read a lot about that Problem, but in my perticular situation I did > > not find a solution that works. > > Soap was deployed by putting the soap.war into tomcats webapps-directory. > > In one try there there was no enty in the server.xml and we got the > > Server.BadTagetObjectURI with the ClassNotFoundException about the class > > containing the soap-rpcs, even the jar-files neded are in teh web-inf/lib > > directory. > > When we put in a xml-statement in the server.xml of tomcat we must have > got > > an Exceptionmessage > > like this "Error opening socket:", "Connection refused:" or that > > "java.net.NoRouteToHostException" > > because the programm catches these messages assuming proxy-parameters have > > to be setup and comes up with a dialog to enter them. > > My question here is which of those two installations is on the futher way > of > > working corectly? > > does soap first recognice a connectiontrouble or does it first recognice > > that the serving class is not found? > > > > thanks in advance > > > > Malte > > > > > > > > >
