My coworker has tried Xalan 2.2.x with our system, and unfortunately,
there's still a few too many bugs to be able to use it for our production
system.
It was just an interesting/annoying little quirk that I discovered and
thought you guys should know about just in case someone else ran into the
same problem. As I said, it was a minor bug if a bug at all.
The part that is most intriguing to me is that the JAXP stuff would 'sniff'
a directory in the CLASSPATH and grab JAR files that aren't EXPLICITY listed
in the CLASSPATH.
My other concern about DOMHelper/DTM still stands though for users of the
Xalan 2.1 release. I'm sure we'd all love to use Xalan 2.2 (or better) when
it's permissible by our particular situations, but for the time being... ;-)
Thanks for the fast reply.
Brion
-----Original Message-----
From: Shane Curcuru [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 01, 2001 4:53 PM
To: [EMAIL PROTECTED]
Subject: Re: Potential bug in default DocumentBuilder (LONG)
<snip/>
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/
