Thanks, now I understand what's going on (though I still don't understand how it manifests itself as a "no signature match" for my service).
While I've always thought that the packaging of the SOAP binary was a little strange, one could also argue that the Catalina classloader could be a bit smarter about things like this. In any case, judging by the number of people who have contacted me since I posted, I'm not the only one experiencing this problem. It should at least be documented in some hopefully-soon-to-be-written "installing Apache SOAP 2.2 with Tomcat 4" doc. How do you suggest that this be resolved? Should I bring this to the attention of someone in particular in the Apache SOAP group? -Chris Remy Maucherat wrote: > > > I'm experiencing a problem with SOAP message-style services > > when using Tomcat 4.01. When trying to access any message-style > > SOAP service, my client receives a "no signature match" fault. [...] > > The problem is that there are class conflicts, as half of the SOAP classes > are in the webapp CL, and will be loaded from there (since the CL won't > delegate), and the rest will be loaded from the shared CL. The conflicts > will occur because the SOAP classes loaded from the shared CL will also load > a "different" copy of the same SOAP classes from soap.jar. > > Moving soap.jar to $CATALINA_HOME/webapps/soap/WEB-INF/lib/soap.jar should > solve the problem, and could be used as a workaround. Alternately, you can > remove from $CATALINA_HOME/webapps/soap/WEB-INF/classes/ the classes which > are also present in the JAR. > > Note: I don't consider this a Catalina problem, but more a questionable > packaging choice of the SOAP binary. > > Remy -- Chris Malley PixelZoom, Inc. Voice: +1.303.494.8849 835 Orman Drive EMail: [EMAIL PROTECTED] Boulder CO 80303-2616 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
