Axiom
  1. Axiom
  2. AXIOM-361

OMNodeImpl detach, when done on the document element of a document, fails to record the state change on the OMDocumentImpl.

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.2.11
    • Fix Version/s: 1.2.13
    • Component/s: LLOM
    • Labels:
      None

      Description

      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.

        Activity

        Eric Johnson created issue -
        Andreas Veithen made changes -
        Field Original Value New Value
        Fix Version/s 1.2.13 [ 12316677 ]
        Andreas Veithen made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Assignee Andreas Veithen [ veithen ]
        Resolution Fixed [ 1 ]

          People

          • Assignee:
            Andreas Veithen
            Reporter:
            Eric Johnson
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development