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

Posted to c-dev@axis.apache.org by "S.Uthaiyashankar (JIRA)" <ji...@apache.org> on 2010/02/02 13:50:18 UTC

[jira] Resolved: (AXIS2C-1445) Detaching an axiom node is not setting the builder's last node properly

     [ https://issues.apache.org/jira/browse/AXIS2C-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

S.Uthaiyashankar resolved AXIS2C-1445.
--------------------------------------

    Resolution: Fixed

Fixed in revision 905612

> Detaching an axiom node is not setting the builder's last node properly
> -----------------------------------------------------------------------
>
>                 Key: AXIS2C-1445
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1445
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: xml/om
>    Affects Versions: Current (Nightly)
>            Reporter: S.Uthaiyashankar
>            Assignee: S.Uthaiyashankar
>             Fix For: 1.7.0
>
>
> When detaching/freeing a node, the underlying builder's last node is freed node, it should be adjusted correctly. If the full tree is built already, detaching will not be a problem. But if we are in the middle of building the tree, and last node built is same as the node we are trying to free, then builder's last node property should be assigned to either previous sibling or parent of the deleted node. 
> Since it is not assigned properly, this cause a crash in Rampart when validating signatures/encryption. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.