> I thnk its based on the StackIterator, which calls for the parent > iterator, and then that object's parent, and then that object's > parent, and so forth. > > Ancestor ends up being just a synthesis of the Parent axis recursively > applied. It's one of those axes that you get 'for free' when you > provide a parent axis iterator.
Ah, that explains a lot, including the performance problem :) The paths involving ancestor:: were the *only* paths that were slower in Jaxen (than in Xalan). I'll write a native ancestor iterator for DOM ASAP.. Christian _______________________________________________ Jaxen-interest mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jaxen-interest
