[ http://issues.apache.org/jira/browse/WSCOMMONS-136?page=comments#action_12457315 ] Toshiro Takase commented on WSCOMMONS-136: ------------------------------------------
I understood. And I verified your changes. Thank you very much for your explanation and fix, Eran. > OMElement.setFirstChild() can break the AXIOM tree > -------------------------------------------------- > > Key: WSCOMMONS-136 > URL: http://issues.apache.org/jira/browse/WSCOMMONS-136 > Project: WS-Commons > Issue Type: Bug > Components: AXIOM > 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. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.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]
