Since you describe this as a show-stopper, I thought I would pass
along the thought you might not be setting the systemId on your
InputSource. There are several places within Xerces where this
causes a bit of indigestion, this being one of them. The parser
would like to be able to resolve a.ent on the off chance that you
might use it, and not having a baseURI might make cases like yours
where the a.ent is a relative system id hard to resolve without
one.
That said, these sorts of things need to be tightened up to avoid
NPEs, which are an unacceptable behavior.
-Glenn
"Attila
Szegedi" To: <[EMAIL PROTECTED]>
<szegedia@free cc:
mail.hu> Subject: NullPointerException when
parsing entity decl in
internal DTD subset
10/18/2001
06:15 AM
Please respond
to
xerces-j-dev
I get NPE in Xerces 1.2.1, 1.2.3, and 1.4.3 when attempting to parse the
following stripped-down test-case XML document:
<?xml version="1.0"?>
<!DOCTYPE root SYSTEM "root.dtd"
[
<!ENTITY a PUBLIC "a" "a.ent">
]>
<root/>
The "root.dtd" contains a single line:
<!ELEMENT root EMPTY>
The exact stack trace is:
[snip]
I believe the DefaultEntityHandler.addExternalEntityDecl is faulty.
As I compose documents from many entities, being unable to parse them is a
show-stopper for me. (I can't switch to other XML parser, as I use FOP, and
it works with Xerces only...)
Attila.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
