Anyway, for those who wants to know the trick is to set the MustUnderstand to false when consuming the web service with WSE.
Just write (in C#) the following before calling the actual methods of your service:
// Creating an instance of the service wrapper
TestSOAPServiceWse service = new TestSOAPServiceWse();
service.Url = "" class="moz-txt-link-rfc2396E" href="http://localhost:8080/axis/services/SOAPTest">"http://localhost:8080/axis/services/SOAPTest";
// setting the "MustUnderstand" to false
SoapContext context = service.RequestSoapContext;
context.Path.EncodedMustUnderstand = "false";
// Consuming the service
Console.WriteLine(service.testDouble());
Now I can start testing SOAP with attachement in .NET :) Nice !
Cheers,
Patrick.
BLIS Webmaster (Patrick Houbaux) wrote:
Hi Josh and all,
It might be a bit late comments for you but I just started to use .NET WSE 1.0 to consume an AXIS web service and I run into the same problem.
My configuration is:
- Axis 1.1 final on tomcat
- Web service server on axis.
- Client with .NET WSE 1.0
When I run the client in .Visual .NET I get:
"Did not understand "MustUnderstand" header(s):"
What is strange is that when I'm using the normal .NET class (MyService instead of MyServiceWse) it works fine.
Does anybody knows if we need to do something special when we are using .NET WSE compare to the orginal .NET?
Any workaround for the problem?
Is .NET WSE buggy?
Regards,
Patrick.
Josh Kropf wrote:
Hi All
I am working on a project where my intent is to make a web service that can be consumed by multiple platforms. I am currently using the latest version of Axis (1.1beta). My Web Service also attaches files to the SOAP message.
The main non-Java platform I have been playing with is blotBlet... excuse me :) ... .Net, more specificly, the Microsoft WSE 1.0 which is a subset of the origional Web Service library that allows SOAP with attachements. When the WSE 1.0 Web Service client attempts to consume the Axis Web Service, Axis throws an Exception saying must understand yadda, yadda, yadda. It seems like .NET WSE 1.0 sends extra SOAP message elements that Axis fails when parsing.
Has anyone ran into this or knows a work around for this?
Thanks
Josh
