SOAPAction header

From: Sam Gardner-Dell <>
Date: Thu, 9 Dec 2004 13:27:03 -0000

I was recently assigned to track a bug which prevents our API from talking to a third-party web service, it turns out the the (Microsoft) based third-party web service dies because the SOAPAction HTTP header contains an empty string whereas our (Java based) test service happily processes the SOAP message even though it doesn't include a valud SOAPAction HTTP header.
After looking at the WSDL file and the stub generated from it, it becomes clear that the SOAPAction here is also an empty string (see below) so it isn't any wonder...How can I force wscompile to automatically include the appropriate soapAction in theh WSDL or is it necessary to do this manually?

<operation name="sendRequestForm">
        <soap:body encodingStyle="" use="encoded" namespace=""/>
        <soap:body encodingStyle="" use="encoded" namespace=""/>
      <soap:operation soapAction=""/>

Thanks in advance,

Sam Gardner-Dell
Analyst Developer

To unsubscribe, e-mail:
For additional commands, e-mail: