Configuring SOAP Method Namespace Prefix for .NET Web Services

When using the IPWorks SOAP component with web services, correct message structure is essential for ensuring that parameters are interpreted correctly. A key factor in this is the MethodNamespacePrefix, which controls how the SOAP method is represented in the request body and can affect compatibility with certain services, especially .NET-based ones.

By default, the component applies a prefix such as "m" to SOAP methods, but some services require a different value or no prefix at all. This behavior can be controlled using the MethodNamespacePrefix setting as shown below:

//To remove the prefix:
soap1.Config("MethodNamespacePrefix=");

//To set a custom prefix:
soap1.Config("MethodNamespacePrefix=new_value");

Service behavior also depends on whether it follows RPC or Document style, which determines how parameters are structured in the SOAP request. This can be identified through service metadata or attributes such as SoapRPCService, SoapRPCMethod, SoapDocumentService, and SoapDocumentMethod.

In Document style services, mismatched or unexpected prefixes can result in parameters not being recognized. Aligning the namespace prefix with the service's expected format ensures that the request is processed correctly without altering the underlying service logic.