RE: Problem with recursive xpath

[keshlam]

Sanity-check: Are you altering your DOM model between the two queries?

If so, that's a problem. Our standard DOM adapter is very much a static/cached adapter; it will *not* tolerate having the document altered after it has been loaded, and the only thing you can do to overcome that is to flush the cache by obtaining a new XPath evaluator (effectively discarding the cached adapter layer) and running the new query against that.

We have experimented with alternate solutions -- you might want to look at the DOM2DTM2 prototype, which may still be checked in although it was never finished, and solving the encapsulation issues more elegantly was part of the goal of the XDM proposal.

______________________________________
"... Three things see no end: A loop with exit code done wrong,
A semaphore untested, And the change that comes along. ..."
-- "Threes" Rev 1.1 - Duane Elms / Leslie Fish (http://www.ovff.org/pegasus/songs/threes-rev-11.html)