Elena Litani wrote:
> 2. Modify XMLDocumentScannerImpl to send 2 extra events -startDTD,
> endDTD - for the described above case. This is tricky, since we don't
> have access in the document scanner to the DTDHandler.. (we can retrieve
> it doing casting of the xni.parser.DTDScanner to
> xerces.impl.XMLDTDScannerImpl).
Could we change the code in the document scanner's
DTDDispatcher to call setInputSource on the DTD scanner
with an empty input source? Then the document scanner
can act in the same way that it does in the case where
the information is provided.
Some possible problems that would need to be solved:
1) the DTD scanner/entity manager barfs having no
system identifier
2) extra events would be produced when previously
we didn't have any
The first part would be a change in the implentation's
behavior. Which isn't so bad. But should we document
that implementors of XMLDTDScanner are supposed to
behave this way in the case where the DOCTYPE is empty?
The second shouldn't be so bad in practice, either.
I can't think of a case where it would hurt having
the start/endDTD calls coming through the system.
Whatcha think?
--
Andy Clark * [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
