[
https://issues.apache.org/jira/browse/AXIOM-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated AXIOM-361:
----------------------------------
Fix Version/s: 1.2.13
> OMNodeImpl detach, when done on the document element of a document, fails to
> record the state change on the OMDocumentImpl.
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIOM-361
> URL: https://issues.apache.org/jira/browse/AXIOM-361
> Project: Axiom
> Issue Type: Bug
> Components: LLOM
> Affects Versions: 1.2.11
> Reporter: Eric Johnson
> Priority: Minor
> Fix For: 1.2.13
>
>
> When doing full document decryption in
> https://code.google.com/a/apache-extras.org/p/santuario-genxdm/, it is
> necessary to replace the document element of a document with its decrypted
> counterpart.
> However, OMNodeImpl.detach doesn't inform the document that the element has
> been removed, and the OMDocumentImpl.documentElement still points at the one
> being detached. When subsequently attempting to add in the newly decrypted
> form of the element, it fails, asserting that the document already has an
> element.
> The work-around here is to specifically check in the case of doing a detach
> on the element of a document, to set the document element of a document to
> null. Unfortunately, but do-able without resorting to implementation details.
--
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
