Did not get mustUnderstand - Error in SOAP Header

[praveennagle kumar]

hello guys,

I am getting the error: Did not understand "MustUnderstand".
In the SOAP header

am using axis with tomcat
and using wsdd file to deploy.



regards
praveen

[Ulf Dittmer]

Welcome to JavaRanch.

A "mustUnderstand" attribute -if set to true- says that the SOAP header it's part of must be understood by the actor handler which tries to handle it. If it's named "MustUnderstand" then it wouldn't be understood (because case matters in XML).

[praveennagle kumar]

Hello, thanks to reply.

below code is my SOAP HEader Part.

<soapenv:Header>
<wsu:Timestamp xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility"><wsu:Created>2005-03-10T05:46:46.401Z</wsu:Created>
</wsu:Timestamp>
<wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/07/secext">

<ds:Signature xmlns s="http://www.w3.org/2000/09/xmldsig#">
<ds:SignedInfo>
<ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
<ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
<ds:Reference URI="#id-14672643">
<ds:Transforms>
<ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
</ds:Transforms>
<ds igestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<ds igestValue>kTdgU10r0SHIAS1ZUZJYkTOWWaI=</ds igestValue>
</ds:Reference>
</ds:SignedInfo>
<ds:SignatureValue>
mCPP+j8UiTxUuQIS8CtS5TLhDwAd7y8V4WwiBx4ZrEd2J81rtPttfo5mxNlBjUqbp0pKRAVT54so
qreb98Fd4gFfGppU8XvmB8fPuuS2AL+H4LOPlj4JvmkckZQVxlXFsrDfjRDVG2lmYXUOsIVifiNb
ixkyPNELx+GqESsxI5A=
</ds:SignatureValue>
<ds:KeyInfo Id="KeyId-3431235">
<wsse:SecurityTokenReference wsu:Id="STRId-2883071" xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility"><wsse:Reference URI="#CertId-9623562" ValueType="wsse:X509v3"/></wsse:SecurityTokenReference>
</ds:KeyInfo>

</ds:Signature>

</wsse:Security> header part



-------------
But eventhou I am getting this error.

<faultstring>
Did not understand "MustUnderstand" header(s):
</faultstring>


regards
praveen

[Dieskun Koper]

The Axis stub did not understand that header, so it generated a fault.

Use a client handler to process (and then remove) the header. The handler will do its work before the message gets deserialized, so that will solve the problem.