0
Answer

Namespace prefixes are a problem for .NET Web Service

andre.rodriguez

andre.rodriguez

21y
3.3k
1
I have written a Web Service in .NET and it works when invoked through a browser. However, the parameter has a null value when accessing it from a Java RPC call. The method is GenerateComments and the (only) parameter is QARequestNumber. I have narrowed the problem down to the existance of a namespace prefix. The following SOAP snippet is from a request that *does not* work: MyRequestNumber The following manually modified SOAP snippet is from a request that *works*, no problem: MyRequestNumber As you can see the 'ns1' namespace prefix is what appears to be the problem. How can I get my Web Service to accept the ns1 prefix, or ignore it? (The other side of the coin is getting the JAX-RPC call to not put in the ns1 prefix, but that is a different challenge.) TIA