[AXIOM-65] OM Serialization doesn't work when a tree contains more than on non-built OMElements

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Assignee: Eran Chinthaka
• Reporter: Eran Chinthaka
• Created: 13/Sep/06 18:32
• Updated: 02/May/13 02:28
• Resolved: 13/Sep/06 18:38

Description

Consider the following scenario.

• You programatically create an OMTree, say you call SOAPFactory.createDefaultSOAPEnvelope().
• You create an OMElement out of an XMLStreamReader and adds that as a child in SOAPHeader
• You do the same thing and adds another node to SOAPHeader.
• When you serialize this, only the first child gets serialized, ignoring the second one.

This seems to be the root cause for http://issues.apache.org/jira/browse/AXIS2-928 as well.

Issue Links

• is depended upon by: AXIS2-928 Not all added header elements are included in outgoing SOAP header unless run under debugger - bug in OMElement caching?
• relates to: AXIOM-315 Handling of completeness in OMNodes and correct OM Serialization in DOOM impl