[AXIOM-508] Calling OMElement.cloneOMElement after OMElement.toString causes exception

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.3.0
• Fix Version/s: 1.4.0
• Component/s: Core Model

Language

Java

• Assignee: Andreas Veithen
• Reporter: Kyla Miller
• Created: 12/Nov/21 02:03
• Updated: 17/Nov/21 00:00
• Resolved: 17/Nov/21 00:00

Description

If there is a descendant processing instruction within an element and the processing has any "psuedo" attributes then calling OMElement.cloneOMElement after OMElement.toString will cause an UnsupportedOperationException exeption.  Example code:

 
        String inputFile = "test-resources\\XMLStaxUtils
ComplexPITest.xml";        OMDocument inputDoc = XMLStaxUtils.readDocument(inputFile);
        OMElement rootElement = inputDoc.getOMDocumentElement();
        
        // This is the call that causes PIs to get trashed and will cause an UnsupportedOperationException to be thrown when cloning.
        rootElement.toString();
        
        try
        

{             rootElement.cloneOMElement();             fail("UnsupportedOperationException should have been thrown.  If it was not then axiom has been fixed so update this test and XMLStaxUtils.cloneOMElement.");         }

        catch (UnsupportedOperationException ex)
        

{         }

We got around it by creating a helper method that resets the text:
 
        List<OMNode> piNodes = getNodesWithDescendantPI(srcElement);
        for (OMNode piNode : piNodes)
        

{             OMProcessingInstruction pi = (OMProcessingInstruction) piNode;             String piValue = pi.getValue();             pi.setValue(piValue);         }

        return srcElement.cloneOMElement();