[
https://issues.apache.org/jira/browse/AXIOM-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416412#comment-13416412
]
Hudson commented on AXIOM-432:
------------------------------
Integrated in ws-axiom-trunk #1110 (See
[https://builds.apache.org/job/ws-axiom-trunk/1110/])
AXIOM-432: Further increased the test coverage of ParentNode#replaceChild
and fixed a couple of issues that occur when newChild is a document fragment.
(Revision 1362582)
Result = SUCCESS
veithen :
Files :
*
/webservices/commons/trunk/modules/axiom/modules/axiom-dom-testsuite/src/main/java/org/apache/axiom/ts/dom/DOMTestSuiteBuilder.java
*
/webservices/commons/trunk/modules/axiom/modules/axiom-dom-testsuite/src/main/java/org/apache/axiom/ts/dom/element/TestInsertBeforeWithDocumentFragment.java
*
/webservices/commons/trunk/modules/axiom/modules/axiom-dom-testsuite/src/main/java/org/apache/axiom/ts/dom/element/TestReplaceChild.java
*
/webservices/commons/trunk/modules/axiom/modules/axiom-dom-testsuite/src/main/java/org/apache/axiom/ts/dom/element/TestReplaceChildCyclic.java
*
/webservices/commons/trunk/modules/axiom/modules/axiom-dom-testsuite/src/main/java/org/apache/axiom/ts/dom/element/TestReplaceChildFirst.java
*
/webservices/commons/trunk/modules/axiom/modules/axiom-dom-testsuite/src/main/java/org/apache/axiom/ts/dom/element/TestReplaceChildFirstWithDocumentFragment.java
*
/webservices/commons/trunk/modules/axiom/modules/axiom-dom-testsuite/src/main/java/org/apache/axiom/ts/dom/element/TestReplaceChildLast.java
*
/webservices/commons/trunk/modules/axiom/modules/axiom-dom-testsuite/src/main/java/org/apache/axiom/ts/dom/element/TestReplaceChildLastWithDocumentFragment.java
*
/webservices/commons/trunk/modules/axiom/modules/axiom-dom-testsuite/src/main/java/org/apache/axiom/ts/dom/element/TestReplaceChildMiddle.java
*
/webservices/commons/trunk/modules/axiom/modules/axiom-dom-testsuite/src/main/java/org/apache/axiom/ts/dom/element/TestReplaceChildMiddleWithDocumentFragment.java
*
/webservices/commons/trunk/modules/axiom/modules/axiom-dom-testsuite/src/main/java/org/apache/axiom/ts/dom/element/TestReplaceChildWithAncestor.java
*
/webservices/commons/trunk/modules/axiom/modules/axiom-dom/src/main/java/org/apache/axiom/om/impl/dom/ParentNode.java
> Updating the last child is not correct unless we are replacing the last child
> -----------------------------------------------------------------------------
>
> Key: AXIOM-432
> URL: https://issues.apache.org/jira/browse/AXIOM-432
> Project: Axiom
> Issue Type: Bug
> Components: DOOM
> Reporter: [email protected]
> Attachments: axiom432-test.zip
>
>
> I have a simple policy which encrypts a header. When the WSS for J decrypts I
> could see in the Dom model the decrypted header. Actually I have 3 headers of
> which one is encrypted in the Dom model. I see all the 3 headers after it is
> decrypted.
> But when it is converted into the OOM model some of the headers disappear.
> soapHeader.addHeaderBlock(element.getLocalName(), element.getNamespace());
> statement
> I noticed that the lastChild field of the SOAPHeader block points to a header
> element somewhere in the middle of the list instead of the last one
> meaning if the Header block contains 3 headers HDR1 -> HDR2 -> HDR3
> then the lastChild should point to HDR3; instead it points to HDR2
> so when a new header HDR4 is added, instead of the list becoming HDR1 -> HDR2
> -> HDR3 -> HDR4
> it becomes HDR1 -> HDR2 -> HDR4 skipping HDR3
> The defect is in org.apache.axiom.om.impl.dom.ParentNode.replaceChild(Node,
> Node) ,line 414, where
> updating the last child is not correct unless we are replacing the last child.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
