> Yes, I know that using XPath expression I can evaluate and get the required
> But using XPath evaluate() is more expensive operation than using
> So I am looking whether the same kind of result I can get by using
> If not possible using iterateAxis, I will go with XPath expression
In all but a very few situations, emulating Saxon's own XPath processor
is much slower than creating a re-usable XPath processor from Saxon's
own. You are using an external API to emulate the internals of a tool,
that is like building your own wheels under a car that already has
wheels of its own, only to try to speed up that car. Rather you should
consider using good oil, a new steering wheel etc.
I once had an implementation where an XPath was created from a string
for each XML that passed by. That was expensive, yes. But by caching the
XPath (easy enough), it became very speedily.