This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
That shouldn't be the case. In the WSDL omitting the soapAction attribute is equivalent to setting soapAction="". It means that the SOAPAction HTTP header will be empty. The WS-I Basic Profile requires that a SOAP envelope inside an HTTP POST request is accompanied by an HTTP SOAPAction header - however it permits the SOAPAction header to be empty. The soapAction attribute simply specifies the content of the SOAPAction HTTP header. The content of the SOAPAction HTTP header is supposed to communicate the "intent" (e.g. operation) of the SOAP envelope, so that proxies and firewalls can act on it without looking into the XML SOAP envelope.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com