Title: XPath Performance
Eric,
Could you retry using Xalan 2.1
And measure time differences ?
We noticed a huge speed increase.
Geert
- Original Message -
From:
Walsh,
Eric
To: '[EMAIL PROTECTED]'
Sent: Wednesday, December 19, 2001 6:39
PM
Subject: XPath Perfor
> > Why does Sun take a beta release and why include it by default ?
> Why include by default: For the convenience of folks who don't want to
have
> to explicitly download it from Apache.
Ok, but dozens of other things can be as well. :-)
But I agree XML is usefull enough :-))
> The real issue he
> This is because JDK 1.4.x includes a backlevel copy of Xalan and
> Crimson in the rt.jar or some other silly place, making them almost
> impossible to override. Ask Sun about it.
> Techniques to use your preferred version of Xalan or to use Xerces are
> not yet clearly FAQ-documented, but ideas
> You _did_ remember to disable the copy of Xerces or Xalan on the Extension
> Class Path (the JDK's lib/ext directory, usually), right? If not, then no
> matter what classpath you set you're probably running obsolete code.
Where was the possibility to disable this ?
It's included with the JDK sou
Thanks Tom !!
> Another backdoor you can use with JDK1.4 to override the xalan classes in
> the rt.jar is to create a directory called "endorsed" under
>
> $JAVA_HOME/jre/lib
>
> and put the xalan and xerces jars in there.
>
> Tom
nTEST ==--
java -classpath %CLASSPATH% org.apache.xalan.xslt.EnvironmentCheck
echo
echo --== XercesTEST ==--
java -classpath %CLASSPATH% org.apache.xerces.framework.Version
echo
REM Actual compilation
javac -classpath %CLASSPATH% -deprecation -d ./%CLASSESDIR%
./src/les/LES.java
pause
best,
Geert Poels
> (Frankly, it may be the case that a standalone XPath implementation and an
> optimized XPath implementation for use within an XLST processor are
actually
> COMPLETE DIFFERENT products.)
But one that has my complete support :-)
I know too little of how Xalan internally works.
Could you briefly tell when and DOM2DTM proxy layer is used ?
Could the creation of this layer be added as an option ?
> We do expect some performance degredation when running XPath against a
DOM,
> since we now have to build the DOM2DTM proxy laye
Whatever the reason may be of the speed decrease using XPathAPI in 2.2 vs
2.1.
What's currently important for us is to know if known major bugs exist in
XPathAPI 2.1.
Bugzilla didn't find any major one so currently, we'll stick with 2.1.
BTW : What's the story of IBM's XML parser ? Are they invo
My previous statement of "Xalan is slow" was definitely too wide.
We're only using the XPath part. (XPathAPI class in fact)
XPathAPI.selectNodeList
XPathAPI.selectSingleNode
and then of course usual stuff like
.item(index).getAttributes().getNamedItem
child.getNodeValue()
The difference in spe
> > Maybe some other collection might be faster. (ArrayList is said to be
> faster)
> Wouldn't help in this case, since it's still oriented toward objects and
> we're storing ints.
ok
> We're still locked into Java 1.1.x compatability. That means we can't use
> Java 1.2 collections classes. (Well
> strategy, then separate JARs for the different APIs would be nice:
> DOM2.jar, SAX2.jar, etc. It can make for a long classpath, but it's the
> clearest alternative.
That's a good idea.
Although is can be accesed from code, I'd like a small readme in jars as
well
stating the date and version nu
Those interested in the Xalan benchmarking, I've created -prof output.
Available to anyone on demand. (300k zipped)
I read this output using :
http://www.capital.net/~dittmer/profileviewer/
A(ll) lot of our time is going to calling the
org.apache.xpath.XPathAPI.selectNodeList method and I only f
That's was good idea.
What's the difference between xml.jar and xml-api.jar ?
Since what version of Xerces have these api's been placed seperately ?
I haven't looked into it in detail but I noticed Document, DocumentBuilder
and probably others
to be both in xerces.jar and xml-api.jar. Are thes
You mean, another library besides Xalan/Xerces or the same but a skinned
version ?
This file is to be found within Xalan/Xerces distributions or elsewhere ?
> Um, did you include the new xml-apis.jar in your classpath? This new
> .jar file contains all the DOM/SAX/JAXP files required to run.
Thanks
> See http://xml.apache.org/xalan-j/faq.html#faq-9 and look for the
> org.apache.xalan.xslt.EnvironmentCheck utility to determine Xalan
> versions. Note that it may not be present in older Xalan builds,
> although you can simply get the latest version from CVS and compile it
> yourself
Following my tests.
I got a compiler exception compiling my sources
using Xalan 22 D13 !!
Geert
C:\xalantest\demo>javac -classpath
.;./src;./lib/xerces144.jar;./lib/xalan22D13.jar;./lib/log4j.jar;./lib/acrobat.zip;./lib/MRJToolkitStubs.zip
-deprecation -d./classes ./src/les/LES.javaAn exc
hello,
This mail is meant for the developers of the Xalan
package, Java version.
We are writing an application which reads and
processes an XML file to read our data from.
Used quite a lot in our code are the XPath api's
from Xalan. (mostly used class : XPathAPI )
Recently we've upgrad
18 matches
Mail list logo
