CabeelalsEfep
New Member
I have a web service running on Axis 1.2 which returns soap messages in the following format:\[code\]<soapenv:Envelope xmlns:soapenv="AAA" xmlns:v1="BBB"> <soapenv:Body xmlns:soapenv="AAA"> <VL xmlns="BBB">\[/code\]Using the C# proxy generated with the relevant WSDL and svcutil.exe, I can run the application however get NULL objects. Searching SO and Google, I saw that this is a common problem when Axis 1.x web services are consumed in .NET, and the reason is mismatched namespaces.So I created a mock service within SoapUI and played with the response SOAP and saw that if I modify the response like that:\[code\]<soapenv:Envelope xmlns:soapenv="AAA" xmlns:v1="BBB"> <soapenv:Body xmlns:soapenv="AAA"> <v1:VL>\[/code\](note the last line has changed) without changing the proxy the object is deserialized successfully.Since I have NO chance (it is 3rd party) to change anything on web service side (so I am stuck to first response), how can I modify my proxy class to handle that?