[ https://issues.apache.org/jira/browse/AXIOM-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069783#comment-13069783 ]
Hudson commented on AXIOM-115: ------------------------------ Integrated in ws-axiom-trunk #453 (See [https://builds.apache.org/job/ws-axiom-trunk/453/]) Removed a method that was deprecated long time ago and that should never be used by application code (see AXIOM-115). veithen : Files : * /webservices/commons/trunk/modules/axiom/modules/axiom-api/src/main/java/org/apache/axiom/om/OMElement.java > OMElement.setFirstChild() can break the AXIOM tree > -------------------------------------------------- > > Key: AXIOM-115 > URL: https://issues.apache.org/jira/browse/AXIOM-115 > Project: Axiom > Issue Type: Bug > Environment: Windows > Reporter: Toshiro Takase > Priority: Critical > > It seems that OMElementImpl.setFirstChild has strange behavior. > Let's see,,, > ----- > OMElement parent = ..... > OMElement a = ..... > OMElement b = ..... > OMElement c = ..... > parent.addChild(a); > parent.addChild(b); > parent.addChild(c); > parent.setFirstChild(b); > ----- > Then, what happens? > In current implementation, the first child of "parent" is "b". > The previous sibling of "b" is still "a". > The next sibling of "b" is "c".... > Is this correct behavior? > Or in the setFirstChild method , "b" should be detached before "b" is set as > first element? > The original first child "a" should be 2nd child? > What is the correct semantics of setFirstChild method? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ws.apache.org For additional commands, e-mail: dev-h...@ws.apache.org