> Mike wrote: > Never got an answer on this before -- trying again...
Such issues are better answered at xerces user mailing list.. > Basically trying to see if it is a bug or this behavior is as expected... I checked with Xerces-J 2.0.1 and i see the desired behavior system id "http://localhost/dtd/api.dtd"; as expected and public id "null" Neeraj > -----Original Message----- > From: Mike Starr > Sent: Monday, May 06, 2002 12:28 PM > To: '[EMAIL PROTECTED]' > Subject: SystemID is null when parsing DOCTYPE > > > It appears that Xerces-J 2.0.1 has a bug when parsing a DOCTYPE declaration > with just a SYSTEM identifier. Here is my XML snippet: > > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE a2wml SYSTEM "http://localhost/dtd/api.dtd"; > > <a2wml></a2wml> > > When I print the publicId and systemId in an entity resolver that a register > with the parser, both are NULL. The spec docs for the "resolveEntity" > method say that I should be able to use the systemId when performing > customized DTD loopkups. > > Also, XercesJ 1.4.4 reported the systemID as "http://localhost/dtd/api.dtd";. > > > -Mike > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Neeraj --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
