axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Veithen <andreas.veit...@gmail.com>
Subject Re: Axiom bug?
Date Wed, 04 Feb 2009 15:41:49 GMT
Andrei,

What is the Axiom version you are using? If it is not 1.2.8 or a
recent snapshot, please check against version 1.2.8. If you can
confirm that the issue still exists in that version, please open a
JIRA issue in the WSCOMMONS project.

Regards,

Andreas

On Wed, Feb 4, 2009 at 16:08, Andrei Ivanov <andrei.ivanov@gmail.com> wrote:
> Hello,
> I'm trying to use Sandesha with Rampart and I think I've found a bug.
> When the server is replying to a CreateSequence message, it gets to
> RampartSender,
> which calls org.apache.rampart.MessageBuilder.build(MessageContext msgCtx),
> which verifies that the security header is empty and tries to remove it:
>
> if ( secHeader != null && secHeader.isEmpty(doc) ) {
>           secHeader.removeSecurityHeader(doc);
> }
>
> WSSecHeader.removeSecurityHeader(Document doc) does this:
> ...
> Node parent = securityHeader.getParentNode();
> parent.removeChild(securityHeader);
>
> Parent:
> <soapenv:Header
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
>      <wsse:Security
> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
> soapenv:mustUnderstand="1" />
>      <wsa:To>http://192.168.1.5:6060/axis2/services/personalDataService@286914895/</wsa:To>
>      <wsa:ReplyTo><wsa:Address>http://www.w3.org/2005/08/addressing/none</wsa:Address></wsa:ReplyTo>
>      <wsa:MessageID>urn:uuid:E3FC5985317BCF16351233758322948</wsa:MessageID>
>      <wsa:Action>http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequenceResponse</wsa:Action>
>      <wsa:RelatesTo>urn:uuid:A07FCCC1972C7E06671233758319824</wsa:RelatesTo>
> </soapenv:Header>
>
> securityHeader:
> <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> soapenv:mustUnderstand="1" />
>
> Then, org.apache.axiom.om.impl.dom.ParentNode.removeChild(Node) is
> called and it gets to this, begining with line 482:
> if (this.firstChild == tempNode) {
>        // If this is the first child
>        this.firstChild = null;
>        this.lastChild = null;
>        tempNode.parentNode = null;
> }
>
> tempNode is the security header and it is equal to the firstChild of
> the envelope header.
> The firstChild is removed... then the lastChild(which is the relatesTo
> child) is removed...
>
> The resulting envelope header is this:
> <soapenv:Header
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:wsa="http://www.w3.org/2005/08/addressing" />
>
> I'm using Axis-1.4.1, Addressing-1.41, Sandesha2-1.3, Rampart-1.4, Axiom 1.2.8
> I've looked in the Axiom sources and it seems this code is from before
> revision 389047 ("Moving doom into ws-commons axiom from axis2")
>
> I think this is a bug...
> Am I right? Should I create an issue?
>

Mime
View raw message