From: Wolfgang M. <wol...@ex...> - 2013-01-02 06:50:34
|
Anrzej, > This xpath error still exists (all puns intended) in the RC2.0 (trunk) version. I concerns me, > since there is obviously an issue deep in the parsing or execution of XPath expressions....which > might cause other issues. I tried to fix this before RC2, but debugging the issue is really time consuming. The problem seems to appear in certain constellations only and after processing the first bunch of nodes. I'm still trying to find the real cause. Probably something simple, but hard to pinpoint. Wolfgang |