You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-dev@axis.apache.org by "Davanum Srinivas (JIRA)" <ji...@apache.org> on 2006/03/30 21:19:27 UTC

[jira] Resolved: (AXIS2-330) Calling setText on an OMElement whose only child is an OMTextImpl concatenates rather than replaces

     [ http://issues.apache.org/jira/browse/AXIS2-330?page=all ]
     
Davanum Srinivas resolved AXIS2-330:
------------------------------------

    Resolution: Fixed

Resolving issue as fixed.

-- dims

> Calling setText on an OMElement whose only child is an OMTextImpl concatenates rather than replaces
> ---------------------------------------------------------------------------------------------------
>
>          Key: AXIS2-330
>          URL: http://issues.apache.org/jira/browse/AXIS2-330
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug
>   Components: core
>     Versions: 0.93
>     Reporter: Craig Chaney
>     Assignee: Eran Chinthaka

>
> The first time you call setText() on an OMElement that has no children, the data structure setup is slightly incorrect.  The previousSibling field of the OMTextImpl points back to itself (i.e. the same OMTextImpl instance).
> Then, when calling setText() again, the logic that removes all other text children doesn't account for this, and the end result is that the old OMTextImpl still exists in the linked list of children.  So on the wire, both text elements appear, the second one appended to the first one.

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