axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Dreier (JIRA)" <>
Subject [jira] Created: (AXIS-2624) SOAP header element attributes "mustUnderstand" and "actor" added twice
Date Mon, 05 Feb 2007 18:15:06 GMT
SOAP header element attributes "mustUnderstand" and "actor" added twice

                 Key: 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


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

<?xml version="1.0" encoding="utf-8"?>
<soapenv:Envelope xmlns:soapenv="" xmlns:xsd=""
		<wssb:wssbUUID mustUnderstand="0" actor=""
mustUnderstand="0" actor="" xmlns:wssb="">0dd3c106-1028-4ef2-b71e-15f6076383b4</wssb:wssbUUID>
		<ns1:getAllAvailCardiologists soapenv:encodingStyle=""

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);

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:

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:
For additional commands, e-mail:

View raw message