Hi Thomas,
What's your platform? There is a problem with the Sun compiler and
iostreams that requires a patch from Sun. That would account for the
second, fatal error.
The first problem with the warning is probably a bug in Xalan 1.4 related
to schema processing. That was fixed in the inte
That one might be a long shot (I am far from being convinced that this is a
Xalan 1.4 problem), but just in case.
Since we switched to Xalan 1.4, from time to time we get the following error
messages through our error handler:
Xalan warning (publicId: , systemId: , line: 0, column: 0): An excepti
D & J PRINTING CORPORATION.CALL US FOR YOUR CARTRIDGE NEEDS
Phone 770-974-8228
Fax 770-974-7223
LOOK AT THESE SAVINGS!! UP TO 60% OFF RETAIL PRICES!
Goverment,School and University purchase orders WELCOME.
Hi Alexei,
Xalan "never" writes a null byte to the end of the stream, as it has no
idea that you're writing to a "string". This behavior has been consistent
since the first version of Xalan was released.
If this worked before it was just by chance, or was, as you suggested,
attributable to a
