[AXIOM-476] Descendant-or-self starting at document node fails to reach elements

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.16
• Fix Version/s: 1.2.17
• Component/s: Core Model
• Environment: Mac OS X
• Assignee: Andreas Veithen
• Reporter: Michael Kay
• Created: 08/Dec/15 21:25
• Updated: 09/Dec/15 19:34
• Resolved: 09/Dec/15 19:34

Description

The iterator obtained by OMDocument.getDescendants(true) returns the document node itself, and no further nodes. The problem is new in 1.2.16, and causes Saxon's XPath processor to deliver incorrect results when running against an Axiom document. The problem appears to be in AbstractNodeIterator, which is apparently new in 1.2.16. The problem is demonstrated by the following test case:

public void testDescendantAxis() {
OMFactory factory = OMAbstractFactory.getOMFactory();
OMDocument document = factory.createOMDocument();
OMElement element = factory.createOMElement("test", null);
document.setOMDocumentElement(element);
Iterator iter = document.getDescendants(true);
int count = 0;
while (iter.hasNext())

{ Object o = iter.next(); count++; }

assertEquals("Two nodes", 2, count);
System.err.println(count);
}

Running in the debugger, the document node is returned OK, but the iterator is left in a state where the following call on hasNext() returns false.