Hey - that wasn't that long. Pretty good description too - thanks!
(Although as you noted true bugfix help comes more quickly to those who
include the calling code and especially the printStackTrace() output...
;-)
Yes, JAXP has a 'magic' lookup system; yes, in previous Xalan builds
the last-ditch default code may have been hardcoded to crimson, which
it shouldn't have been (I don't remember).
It's very odd that you get more exceptions when crimson.jar is around
rather than when it's not. One other thing to check: JAXP's 'magic'
loading also searches your JAVA_HOME/lib/ext directory for any .jar
files therein - so if you have jaxp.jar, crimson.jar, xalan.jar, or the
like in *that* directory, they may be being called instead of the .jars
that are in your CLASSPATH. (Which version of Crimson you have also
makes a difference too...)
The other suggestion is to try upgrading to the latest Xalan-J 2.2
developer build, if you can do that at this point in your project.
In any case, don't worry about reporting the bug, I think with the
upcoming xml-commons stuff (a new copy of JAXP code, etc. in a standard
place) and the current Xalan/Crimson/Xerces builds we should have it
covered. But of course come back and ask more questions if Xalan's not
working for you now.
- Shane
=====
<eof aka="mailto:[EMAIL PROTECTED]";
quote="Odo: [You'd shoot a man in the back?]
Garak: [Well, it's the safest way, isn't it?]"/>
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
