Hi all, We have a very XPATH-intense application and the performance is to bad using the ordinary XPATH-api in Xalan. We switched and started using the CachedXPathAPI and the performance is great.
Example use:
NodeList anl = cachedXPathAPI.selectNodeList(document.getDocumentElement(),
attributesXPath);
We have had no problems in our development environment but when we deploy to
the server we sometimes get the following error:
SEVERE Wed May 21 16:42:07 CEST 2003An error occurred during the update of
the Xpath:java.lang.ArrayIndexOutOfBoundsException: -1
SEVERE Wed May 21 16:42:07 CEST
2003java.lang.ArrayIndexOutOfBoundsException: -1
at
org.apache.xpath.XPathContext.pushCurrentNode(XPathContext.java:767)
at
org.apache.xpath.axes.PredicatedNodeTest.acceptNode(PredicatedNodeTest.java:
427)
at org.apache.xpath.axes.AxesWalker.nextNode(AxesWalker.java:392)
at
org.apache.xpath.axes.WalkingIterator.nextNode(WalkingIterator.java:182)
at
org.apache.xpath.axes.LocPathIterator.runTo(LocPathIterator.java:802)
at org.apache.xml.dtm.ref.DTMNodeList.<init>(DTMNodeList.java:114)
at org.apache.xpath.objects.XNodeSet.nodelist(XNodeSet.java:384)
at
org.apache.xpath.CachedXPathAPI.selectNodeList(CachedXPathAPI.java:258)
at
org.apache.xpath.CachedXPathAPI.selectNodeList(CachedXPathAPI.java:235)
at
se.sprawlsolutions.qm.controllers.QuestionnaireTemplateController.updateXPat
hValue(QuestionnaireTemplateController.java:637)
Have any of you experienced this or have any idea of what it can be? Is it
possible the JDK we run 1.4.1_02 can interfere with the Xalan we have
deployed in our app?
Regards
Mattias Bogeblad
_______________________________________________________________
Mattias Bogeblad | PH: +46 31 799 01 16 | MOB: +46 702 80 05 05
SPRAWL SOLUTIONS AB
FABRIKSGATAN 7
412 50 GÖTEBORG
FAX: +46 31 799 00 10
_______________________________________________________________
<<attachment: winmail.dat>>
