Glenn Nielsen wrote:
Chris Malley 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.
[...]
Moving soap.jar to
Chris Malley 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.
[...]
Remy Maucherat wrote:
[...]
Moving soap.jar to
, SOAPContext req, SOAPContext
res )
throws IOException, MessagingException;
What makes me think that this may be a Tomcat classloader
problem is that I can make the fault go away by removing
$CATALINA_HOME/webapps/soap/WEB-INF/classes/org/.
But I don't understand why this makes the fault go away
env, SOAPContext req, SOAPContext
res )
throws IOException, MessagingException;
What makes me think that this may be a Tomcat classloader
problem is that I can make the fault go away by removing
$CATALINA_HOME/webapps/soap/WEB-INF/classes/org/.
But I don't understand why this makes
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
