First message is on windows, second message is on Solaris :-(
I will test with the interim release for the first message.
For the sun compiler patch, where can I find the information about this patch? As part of the Solaris distribution of Xalan 1.4?
As a side note, I must recognize and thank you again for all the help you provide. It really makes a huge difference for us to have such a responsive and effective person in this open source project. Thanks again, we all appreciate.
Thomas
-----Original Message-----
From: David N Bertoni/Cambridge/IBM [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 04, 2002 6:00 PM
To: [email protected]
Subject: Re: Xalan 1.4 weird behavior (may be:-)
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 interim release. At any rate, this should not interfere with processing.
Dave
[EMAIL PROTECTED]
oftware.com To: [email protected]
cc: (bcc: David N Bertoni/Cambridge/IBM)
12/04/2002 02:47 PM Subject: Xalan 1.4 weird behavior (may be:-)
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 exception occurred! Type:RuntimeException, Message:Warning: The primary document entity could not be opened. Id=
Or
Xalan fatal error (publicId: , systemId: , line: 1, column: 2): Expected an element name
We have been looking at our input XML and XSLT documents over and over without finding the cause of those problems. It also seems that it happens only when passing the input XML document as a stream instead of a file path.
Any ideas/suggestions?
Thomas
