commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut Wannheden <>
Subject Re: [JXPath] unordered node-sets
Date Thu, 20 Jan 2005 12:17:44 GMT

Dmitri Plotnikov <dmitri <at>> writes:

> Ok, I think I now get it. Sorry about having been so obtuse.  To make the
search interruptable, we should
> eliminate the isChildOrderingRequired method. Actually I don't even know why
we have it. Paths like
> "//foo" would produce results in the right order even without it.
> Try this: comment out the DescendantContext#isChildOrderingRequired method. 
Let me know if it makes a
> difference.  If it does without breaking anything else, I will make the change

Yes, that change did help!  I will still leave my dirty hack in for interrupting
other kinds of badly written expressions.



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message