[AXIOM-24] OMDocument#serializeAndConsume doesn't consume the document

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.2.8
• Fix Version/s: 1.2.11
• Component/s: DOOM, LLOM
• Assignee: Andreas Veithen
• Reporter: Andreas Veithen
• Created: 10/Mar/09 12:05
• Updated: 27/Mar/11 11:43
• Resolved: 02/Jan/11 16:06

Description

OMDocument#serializeAndConsume doesn't consume the document but instead fully builds it.

This is caused by the following piece of code:

while (children.hasNext())

{ OMNodeEx omNode = (OMNodeEx) children.next(); omNode.internalSerializeAndConsume(writer); }

As described in WSCOMMONS-346, the call to Iterator#next() actually builds the returned node, so that the call to internalSerializeAndConsume has the same effect as serialization with caching enabled. This means that the code fully builds the document.

Note that the code actually doesn't make sense because once a child (in particular the document element) has been consumed, it is not possible to retrieve the next sibling. This means that even if WSCOMMONS-346 is solved, the code still wouldn't behave as expected. Worse, it would trigger an exception.

Issue Links

• blocks: AXIOM-333 getFirstChildWithName should not read the next element.
• is blocked by: AXIOM-346 Enhance OMStAXWrapper/OMNavigator to work with OMDocument objects