This module, both source code and documentation, is in the
Public Domain, and comes with NO WARRANTY.
for further information.
This class allows a SAX application to encapsulate information
about an input source in a single object, which may include
a public identifier, a system identifier, a byte stream (possibly
with a specified encoding), and/or a character stream.
There are two places that the application can deliver an
input source to the parser: as the argument to the Parser.parse
method, or as the return value of the EntityResolver.resolveEntity
The SAX parser will use the InputSource object to determine how
to read XML input. If there is a character stream available, the
parser will read that stream directly, disregarding any text
encoding declaration found in that stream.
If there is no character stream, but there is
a byte stream, the parser will use that byte stream, using the
encoding specified in the InputSource or else (if no encoding is
specified) autodetecting the character encoding using an algorithm
such as the one in the XML specification. If neither a character
stream nor a
byte stream is available, the parser will attempt to open a URI
connection to the resource identified by the system
An InputSource object belongs to the application: the SAX parser
shall never modify it in any way (it may modify a copy if
necessary). However, standard processing of both byte and
character streams is to close them on as part of end-of-parse cleanup,
so applications should not attempt to re-use such streams after they
have been handed to a parser.
Application writers should use setSystemId() to provide a base
for resolving relative URIs, may use setPublicId to include a
public identifier, and may use setEncoding to specify the object's
byteStream - The raw byte stream containing the document.
The system identifier is optional if there is a byte stream
or a character stream, but it is still useful to provide one,
since the application can use it to resolve relative URIs
and can include it in error messages and warnings (the parser
will attempt to open a connection to the URI only if
there is no byte stream or character stream specified).
If the application knows the character encoding of the
object pointed to by the system identifier, it can register
the encoding using the setEncoding method.
If the system identifier is a URL, it must be fully
resolved (it may not be a relative URL).
Submit a bug or feature For further API reference and developer documentation, see Java SE Developer Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.