There are use cases where you may want to send a message through HTTP, File, or another transport to a .NET Web Service. Using Mule ESB
, it’s fairly straight-forward to accomplish this.
Consider this use case:
* A client sends an XML message (not SOAP) to Mule, which goes through some transformation and gets forwarded to a .NET-based web service using an SSL certificate.
* If the client queries for the WSDL, a specialized component in Mule called WSProxyService returns the WSDL, which is retrieved from the .NET web service.
* To the client, http://localhost:8888/services/myservice
exposes a standard web service, and the client doesn’t have to know what this service is implemented by, e.g., whether it’s Axis2, .NET, or CXF.
* In some cases, a SOAP action header may need to be added to the message so that .NET can find the right service on the .NET side.
Detailed instructions on interoperating with .NET Web Services in Mule ESB.