SOAP header element attributes "mustUnderstand" and "actor" added twice
-----------------------------------------------------------------------

                 Key: AXIS-2624
                 URL: https://issues.apache.org/jira/browse/AXIS-2624
             Project: Axis
          Issue Type: Bug
          Components: Serialization/Deserialization
    Affects Versions: current (nightly), 1.4
         Environment: OS: Windows XP Professional SP2
Application Server: Apache Tomcat 5.5.17
            Reporter: Martin Dreier


Hello,

the described issue occurs in the following environment: web service A is 
called from a client. During processing, it calls in turn a web service B, 
running on the same engine. During the call, a handler is used on the client 
side, which adds a new SOAP header block. The resulting message:

<?xml version="1.0" encoding="utf-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
        <soapenv:Header>
                <wssb:wssbUUID mustUnderstand="0" 
actor="http://schemas.xmlsoap.org/soap/actor/next"; mustUnderstand="0" actor="" 
xmlns:wssb="http://www.sap.com/wssb";>0dd3c106-1028-4ef2-b71e-15f6076383b4</wssb:wssbUUID>
        </soapenv:Header>
        <soapenv:Body>
                <ns1:getAllAvailCardiologists 
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; 
xmlns:ns1="HPIndex"/>
        </soapenv:Body>
</soapenv:Envelope>

As you can see, the attributes "mustUnderstand" and "actor" of the 
"wssb:wssbUUID" header element appear twice. Debugging has led me to the 
conclusion that these attribute duplicates are added during serialization at 
the client side. I have confirmed that immediately before serialization both 
attributes appear only once each.

This is the code in the handler to add the header:

        Name uuidNodeName = 
currentMessage.getSOAPEnvelope().createName("wssbUUID", "wssb", NAMESPACE);
        uuidNode = 
currentMessage.getSOAPHeader().addHeaderElement(uuidNodeName);
        uuidNode.setMustUnderstand(false);
        uuidNode.setActor(Constants.URI_SOAP11_NEXT_ACTOR);
        uuidNode.addTextNode(uuid.toString());

All web services run perfectly well if adding the header is omitted (i.e. the 
above lines are commented out). This issue occurs on Axis, release 1.4 as well 
as on the current SVN checkout. It also appears on the latest released Xalan 
and Xerces versions as well as on their latest SVN checkouts.

I also found a bug report with a similar issue. However, I do not know if the 
two are related: https://issues.apache.org/jira/browse/AXIS-1466.

Best regards,
Martin Dreier

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to