Hi Joseph,
"Joseph Kesselman/Watson/IBM" <[EMAIL PROTECTED]> writes:
>
> I'm not sure, but this appears to be either a broken build or a
> broken classpath, since the IncrementalSAXSource_Xerces class has
> been part of Xalan for many months now. It looks as if you've failed
> to compile this class for some reason... or are somehow running
> classes from two different versions of Xalan at once.
The second may be possible. I checked the jar file, xalan.jar, and the
class is in there.
I just now went through all the *.jar files in the class path and
xalan.jar is the only one that shows up:
for i in *.jar; do
echo $i ;
unzip -l $i | grep "org/apache/xml/dtm/ref/IncrementalSAXSource_Xerces" ;
done
xalan.jar
9328 02-19-02 17:28
org/apache/xml/dtm/ref/IncrementalSAXSource_Xerces.class
> How are you invoking the processor -- is it possible that you're
> changing classloaders in mid-stream?
I'm just using org.apache.xalan.xslt.Process.
> (IncrementalSAXSource_Xerces does use reflection to avoid hard
> dependencies on Xerces, as Shane pointed out, but a failure in that
> reflection code ought to be caught and handled internally, and even
> if that malfunctioned should be reported as an inability to access
> the Xerces classes rather than failure loading this "glue" class.)
>>The weird thing is that the transformation appears to be fine.
> There are fallbacks which allow us to process with whatever JAXP
> parser is available, if Xerces can't be loaded. It's possible that
> those are robust enough that they're managing to handle this case
> too, though that's certainly not what they were designed for.
That's good to know.
My first reaction to seeing this error was to search for it on google
(here's their cache):
<http://216.239.51.100/search?q=cache:yKTp77xwXK0C:https://www.medieninformatik.hdm-stuttgart.de/skripte/dokerstell1/uebung/Sources/Memoxml/err+java.lang.ClassNotFoundException:+org/apache/xml/dtm/ref/IncrementalSAXSource_Xerces&hl=en&ie=UTF8>
A lot of times when I encounter these types of things and I search via
google, I'll see that others have experieneced the same problem - I
was suprised not to see this one in a mailing list.
Elizabeth
