Hi Joe,
After talking to you on the phone, I collected more
information on the problems I'm seeing that may reflect
an incompatibility using post Xalan-Java 2.2.D13 and
Xerces-Java 2.0.0 Beta 3.
I ran Xalan over java fullversion 1.3.1_01 and had only
xalan.jar (from current CVS) and xerces.jar (Xerces-Java 2.0.0 Beta 3)
on my classpath. I ran a few conf tests by hand using
org.apache.xalan.xslt.Process
and got either no output or missing output. It made
no difference if I put xml-apis.jar on my CP. It made
no difference if I used the -NOOPTIMIZE option on the
commandline.
Here's a sampling of conf tests that fail:
axes113 - only outputs the xml declaration, the rest of the
output is missing
copy38 - missing output
lre13 - no output
idkey01 - no output
Of course, these conf tests work fine in the same context with
the current CVS version of xerces.jar, so the problem seems
to be the combination of Xalan and Xerces.
I hope this is enough so you can reproduce the problem.
Tom
