> It seems as if it has something to do with diving into the
FLNZustandsWechselCLASS element
> for evaluating the predicate (which works fast) and then after having the
candidate node set
> going down again in the final two location steps (which slows the process
down).
>
> Evaluating the same expression with the SimpleXPathAPI sample or within
the xpath console
> of the CookTop 2.500 tool indicated no performance problem at all. In the
case of
> SimpleXPathAPI it may be due to the fact that it's using Xalan's native
DOM instead of
> mapping to/from the Xerces DOM.
I suspect you're building the bridge/wrapper the wrong way. A couple of
questions:
1. Which Xerces DOM are you using? The deprecated one, or the new one?
2. How do you wrap the Xerces DOM instance. A snippet of your code
which builds the wrapper would help diagnose this.
Unfortunately, some performance degradation is inherent with wrapping the
Xerces DOM.
Dave
