[
Lists Home |
Date Index |
Thread Index
]
At 6:52 PM +0000 2/28/04, Michael Kay wrote:
># > Taking this argument to extremes, is it acceptable for a parser not
># > to call startDocument? Just to call fatalError? I have caught parsers
># > doing this, especially when the error is very early in the document;
># > e.g. in the byte order mark or the XML declaration.
>#
># I would say that at this point the document has started
>
>So what constitutes a document "starting"? What happens if no resource with
>the given System ID can be found?
That's an I/O error and the parser throws an IOException but does not
call startDocument, fatalError, or endDocument.
> What happens if a resource can be found,
>but it is zero-length?
The resource is malformed. The parser calls startDocument,
fatalError, and endDocument.
> What happens if there is a timeout while trying to
>fetch the resource?
This is also an I/O error and the parser throws an IOException and
does not call startDocument, fatalError, or endDocument.
--
Elliotte Rusty Harold
elharo@metalab.unc.edu
Effective XML (Addison-Wesley, 2003)
http://www.cafeconleche.org/books/effectivexml
http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaulaitA
|
