Hi,
I'm new to this list, so pardon me if this has been discussed
before... I didn't see anything about it in a quick search of the
archives.
I'm trying to certify our app server for J2EE 1.3 using xerces
(1.4.4 currently) and xalan as the parser / transform engine. I'd
really rather not use crimson as most of our customers want to use
xerces.
Out of the currently 2286 JAXP conformance tests, we fail 8.
Four of them are due to bug 5461, which I opened yesterday
(DefaultEntityHandler.expandSystemId(), returns the empty string
when passed a null systemId).
The other four are due to the fact that
DefaultEntityHandler.startReadingFromDocument() throws a
SAXException instead of an IOException when it can't find the
source.
In startReadingFromDocument, Neil has already noted that this causes
JAXP problems...
} catch (FileNotFoundException fnf) {
// according to the JAXP spec, SAXExceptions should not be
// generated in this case! - neilg
Is there any desire to make xerces 1.4.x JAXP 1.1 compliant (at
least enough to pass the J2EE 1.3 JAXP CTS tests)? I thought that
the xerces Java 1 page claimed to be JAXP 1.1 compliant, but I don't
see that there anymore.
Has anyone used Xerces Java 2 for passing the 1.3 CTS?
Would the maintainers be willing to take code changes that fixed
these problems?
Thanks!
-John
----------------------------------------------------------------
John Rousseau [EMAIL PROTECTED]
SilverStream Software Phone: +1 978 262 3564
2 Federal Street Fax: +1 978 262 3499
Billerica, MA 01821 http://www.silverstream.com
----------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
