Why Xalan 2.2 and not 2.4

[comdivisionys]

Hello,

can someone explain me why JBoss uses Xalan 2.2 and not 2.4? 2.4 is much faster...

Within a servlet wich uses xalan on a Sun Fire 280R it needs 2.2 needs over 12 secs. for interpretation with JBoss. If I exchange 2.2 with 2.2 it goes down to 3 secs.

Is there something I may have not seen??

Bye Yves

[juha]

Could be because no one has seen a reason to update it yet, or that no one has requested such a change.

[comdivisionys]

Ok, so what can I do to get the current Xalan integrated in the next JBoss release??? We have tested many different applications and found no problem with xalan 2.4 and Jboss 3.0.3

[sgturner]

Why not download the JBoss source, install 2.4 and then run the testsuite. See what happens. Gotta say, I'm a proponet of "if it ain't broke, don't mess with it"

[johnc]

I'm interested in using the CachedXPathAPI class available in Xalan 2.2.D14+. CachedXPathAPI seems to offer quite a speed advantage over XPathAPI in my application.

JBoss 3.0.6 uses 2.2.D11, which means that it is not available. I'm not keen on having two versions of the same Jar loaded.

It seems reasonable to upgrade the library to the non-developer release 2.2. What is the process of introducing an updated Xalan and associated libs into the 3.0.x branch?

Any advice/help appreciated,

John.