Hi everbody,

We have implemented a SOAP service using Axis 1.0 and Axis 1.1. This service
added a custom sessionID to the SOAP header. The sessionID is added as an
attribute to the header, because of some requirements of our client. Now we
have switched from Axis 1.0 to Axis 1.1, but Axis 1.1 seems to handle the
SOAP header differently: Axis 1.1 adds the mustUnderstand Attribute to our
custom sessionID, e.g.:
The Axis 1.1 client sends
   ...
   <soapenv:Header>  
      <sessionID sessionID="mySession" soapenv:mustUnderstand="0"/> 
   </soapenv:Header> 
   ...
instead of
   ...
   <soapenv:Header>  
      <sessionID sessionID="mySession"/> 
   </soapenv:Header> 
   ...
in the Axis 1.0 client.

According to the SOAP 1.1 specification omitting the mustUnderstand
attribute is equivalent to mustUnderstand="0".
So, is it possible to turn off the mustUnderstand attribute in the Axis 1.1
serialization. If so can anybody tell me how to turn if off.

Thanks,
Thomas

Reply via email to