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
