elena 2002/12/11 08:15:26
Modified: java/src/org/w3c/dom/ls DOMWriter.java DOMBuilder.java
Log:
Update LS to reflect DOMConfiguration changes
Revision Changes Path
1.6 +130 -185 xml-xerces/java/src/org/w3c/dom/ls/DOMWriter.java
Index: DOMWriter.java
===================================================================
RCS file: /home/cvs/xml-xerces/java/src/org/w3c/dom/ls/DOMWriter.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- DOMWriter.java 18 Sep 2002 22:03:17 -0000 1.5
+++ DOMWriter.java 11 Dec 2002 16:15:26 -0000 1.6
@@ -14,7 +14,8 @@
import org.w3c.dom.Node;
import org.w3c.dom.DOMException;
-import org.apache.xerces.dom3.DOMErrorHandler;
+import org.apache.xerces.dom3.DOMConfiguration;
+
/**
* <strong>DOM Level 3 WD Experimental:
@@ -27,7 +28,7 @@
* stream, the type of which depends on the specific language bindings in
* use.
* <p> During serialization of XML data, namespace fixup is done when possible
- * as defined in , Appendix B. allows empty strings as a real namespace
+ * as defined in [<a
href='http://www.w3.org/TR/2002/WD-DOM-Level-3-Core-20020114'>DOM Level 3 Core</a>],
Appendix B. [<a href='http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113'>DOM
Level 2 Core</a>] allows empty strings as a real namespace
* URI. If the <code>namespaceURI</code> of a <code>Node</code> is empty
* string, the serialization will treat them as <code>null</code>, ignoring
* the prefix if any. should the remark on DOM Level 2 namespace URI
@@ -40,40 +41,42 @@
* serialized form is not specified, but should be something useful to a
* human for debugging or diagnostic purposes. Note: rigorously designing an
* external (source) form for stand-alone node types that don't already have
- * one defined in seems a bit much to take on here.
- * <p>Within a Document, DocumentFragment, or Entity being serialized, Nodes
- * are processed as follows Documents are written including an XML
+ * one defined in [<a href='http://www.w3.org/TR/2000/REC-xml-20001006'>XML
1.0</a>] seems a bit much to take on here.
+ * <p>Within a <code>Document</code>, <code>DocumentFragment</code>, or
+ * <code>Entity</code> being serialized, <code>Nodes</code> are processed as
+ * follows <code>Document</code> nodes are written including with the XML
* declaration and a DTD subset, if one exists in the DOM. Writing a
- * document node serializes the entire document. Entity nodes, when written
- * directly by <code>writeNode</code> defined in the <code>DOMWriter</code>
- * interface, output the entity expansion but no namespace fixup is done.
- * The resulting output will be valid as an external entity. Entity
- * reference nodes are serialized as an entity reference of the form "
- * <code>&entityName;</code>" in the output. Child nodes (the expansion)
- * of the entity reference are ignored. CDATA sections containing content
- * characters that can not be represented in the specified output encoding
- * are handled according to the "split-cdata-sections" feature.If the
- * feature is <code>true</code>, CDATA sections are split, and the
- * unrepresentable characters are serialized as numeric character references
- * in ordinary content. The exact position and number of splits is not
- * specified. If the feature is <code>false</code>, unrepresentable
- * characters in a CDATA section are reported as errors. The error is not
- * recoverable - there is no mechanism for supplying alternative characters
- * and continuing with the serialization. DocumentFragment nodes are
+ * <code>Document</code> node serializes the entire document.
+ * <code>Entity</code> nodes, when written directly by
+ * <code>DOMWriter.writeNode</code>, output the entity expansion but no
+ * namespace fixup is done. The resulting output will be valid as an
+ * external entity. <code>EntityReference</code> nodes are serialized as an
+ * entity reference of the form "<code>&entityName;</code>" in the
+ * output. Child nodes (the expansion) of the entity reference are ignored.
+ * CDATA sections containing content characters that can not be represented
+ * in the specified output encoding are handled according to the
+ * "split-cdata-sections" boolean parameter. If the boolean parameter is
+ * <code>true</code>, CDATA sections are split, and the unrepresentable
+ * characters are serialized as numeric character references in ordinary
+ * content. The exact position and number of splits is not specified. If
+ * the boolean parameter is <code>false</code>, unrepresentable characters
+ * in a CDATA section are reported as errors. The error is not recoverable -
+ * there is no mechanism for supplying alternative characters and continuing
+ * with the serialization. <code>DocumentFragment</code> nodes are
* serialized by serializing the children of the document fragment in the
* order they appear in the document fragment. All other node types
* (Element, Text, etc.) are serialized to their corresponding XML source
- * form. The serialization of a DOM Node does not always generate a
- * well-formed XML document, i.e. a <code>DOMBuilder</code> might through
+ * form. The serialization of a <code>Node</code> does not always generate
+ * a well-formed XML document, i.e. a <code>DOMBuilder</code> might through
* fatal errors when parsing the resulting serialization.
* <p> Within the character data of a document (outside of markup), any
* characters that cannot be represented directly are replaced with
* character references. Occurrences of '<' and '&' are replaced by
- * the predefined entities &lt; and &amp. The other predefined
- * entities (&gt, &apos, etc.) are not used; these characters can be
- * included directly. Any character that can not be represented directly in
- * the output character encoding is serialized as a numeric character
- * reference.
+ * the predefined entities &lt; and &amp;. The other predefined
+ * entities (&gt, &apos, and &quot;) are not used; these
+ * characters can be included directly. Any character that can not be
+ * represented directly in the output character encoding is serialized as a
+ * numeric character reference.
* <p> Attributes not containing quotes are serialized in quotes. Attributes
* containing quotes but no apostrophes are serialized in apostrophes
* (single quotes). Attributes containing both forms of quotes are
@@ -84,165 +87,123 @@
* <p> Within markup, but outside of attributes, any occurrence of a character
* that cannot be represented in the output character encoding is reported
* as an error. An example would be serializing the element
- * <LaCaņada/> with the encoding="us-ascii".
- * <p> When requested by setting the <code>normalize-characters</code> feature
- * on <code>DOMWriter</code>, all data to be serialized, both markup and
- * character data, is W3C Text normalized according to the rules defined in
- * . The W3C Text normalization process affects only the data as it is being
- * written; it does not alter the DOM's view of the document after
- * serialization has completed.
- * <p>Namespaces are fixed up during serialization, the serialization process
+ * <LaCaņada/> with <code>encoding="us-ascii"</code>.
+ * <p> When requested by setting the <code>normalize-characters</code> boolean
+ * parameter on <code>DOMWriter</code>, all data to be serialized, both
+ * markup and character data, is W3C Text normalized according to the rules
+ * defined in [<a
href='http://www.w3.org/TR/2002/WD-charmod-20020430'>CharModel</a>]. The W3C Text
normalization process affects only the data as
+ * it is being written; it does not alter the DOM's view of the document
+ * after serialization has completed.
+ * <p> Namespaces are fixed up during serialization, the serialization process
* will verify that namespace declarations, namespace prefixes and the
- * namespace URIs associated with Elements and Attributes are consistent. If
+ * namespace URIs associated with elements and attributes are consistent. If
* inconsistencies are found, the serialized form of the document will be
- * altered to remove them. The algorithm used for doing the namespace fixup
- * while serializing a document is a combination of the algorithms used for
- * lookupNamespaceURI and lookupNamespacePrefix . previous paragraph to be
- * defined closer here.
+ * altered to remove them. The method used for doing the namespace fixup
+ * while serializing a document is the algorithm defined in Appendix B.1
+ * "Namespace normalization" of [<a
href='http://www.w3.org/TR/2002/WD-DOM-Level-3-Core-20020114'>DOM Level 3 Core</a>].
previous paragraph to be defined closer
+ * here.
* <p>Any changes made affect only the namespace prefixes and declarations
* appearing in the serialized data. The DOM's view of the document is not
* altered by the serialization operation, and does not reflect any changes
* made to namespace declarations or prefixes in the serialized output.
* <p> While serializing a document the serializer will write out
* non-specified values (such as attributes whose <code>specified</code> is
- * <code>false</code>) if the <code>discard-default-content</code> feature
- * is set to <code>true</code>. If the <code>discard-default-content</code>
- * flag is set to <code>false</code> and a schema is used for validation,
- * the schema will be also used to determine if a value is specified or not.
- * If no schema is used, the <code>specified</code> flag on attribute nodes
- * is used to determine if attribute values should be written out.
+ * <code>false</code>) if the <code>discard-default-content</code> boolean
+ * parameter is set to <code>true</code>. If the
+ * <code>discard-default-content</code> flag is set to <code>false</code>
+ * and a schema is used for validation, the schema will be also used to
+ * determine if a value is specified or not. If no schema is used, the
+ * <code>specified</code> flag on attribute nodes is used to determine if
+ * attribute values should be written out.
* <p> Ref to Core spec (1.1.9, XML namespaces, 5th paragraph) entity ref
* description about warning about unbound entity refs. Entity refs are
* always serialized as <code>&foo;</code>, also mention this in the
* load part of this spec.
- * <p> <code>DOMWriter</code>s have a number of named features that can be
- * queried or set. The name of <code>DOMWriter</code> features must be valid
- * XML names. Implementation specific features (extensions) should choose an
- * implementation dependent prefix to avoid name collisions.
- * <p>Here is a list of features that must be recognized by all
- * implementations. Using these features does affect the <code>Node</code>
- * being serialized, only its serialized form is affected.
- * <dl>
- * <dt>
- * <code>"discard-default-content"</code></dt>
- * <dd> This feature is equivalent to the
- * one provided on <code>Document.setNormalizationFeature</code> in . </dd>
- * <dt>
- * <code>"canonical-form"</code></dt>
- * <dd>
- * <dl>
- * <dt><code>true</code></dt>
- * <dd>[optional] This formatting
- * writes the document according to the rules specified in . Setting this
- * feature to true will set the feature <code>"format-pretty-print"</code>
- * to false. </dd>
- * <dt><code>false</code></dt>
- * <dd>[required] (default) Do not canonicalize the
- * output. </dd>
- * </dl></dd>
- * <dt><code>"entities"</code></dt>
- * <dd> This feature is equivalent to the one
- * provided on <code>Document.setNormalizationFeature</code> in . </dd>
- * <dt>
- * <code>"format-pretty-print"</code></dt>
- * <dd>
- * <dl>
- * <dt><code>true</code></dt>
- * <dd>[optional] Formatting
- * the output by adding whitespace to produce a pretty-printed, indented,
- * human-readable form. The exact form of the transformations is not
- * specified by this specification. Setting this feature to true will set
- * the feature "canonical-form" to false. </dd>
- * <dt><code>false</code></dt>
- * <dd>[required] (
- * default) Don't pretty-print the result. </dd>
- * </dl></dd>
- * <dt><code>"namespaces"</code></dt>
- * <dd> This
- * feature is equivalent to the one provided on
- * <code>Document.setNormalizationFeature</code> in . </dd>
- * <dt>
- * <code>"normalize-characters"</code></dt>
- * <dd> This feature is equivalent to the one
- * provided on <code>Document.setNormalizationFeature</code> in . Unlike in
- * the Core, the default value for this feature is <code>true</code>. </dd>
- * <dt>
- * <code>"split-cdata-sections"</code></dt>
- * <dd> This feature is equivalent to the one
- * provided on <code>Document.setNormalizationFeature</code> in . </dd>
- * <dt>
- * <code>"validate"</code></dt>
- * <dd> This feature is equivalent to the one provided on
- * <code>Document.setNormalizationFeature</code> in . </dd>
- * <dt>
- * <code>"unknown-characters"</code></dt>
- * <dd>
- * <dl>
- * <dt><code>true</code></dt>
- * <dd>[required] (default)
- * If, while verifying full normalization when XML 1.1 is supported, a
- * character is encountered for which the normalization properties cannot be
- * determined, then ignore any possible denormalizations caused by these
- * characters. </dd>
- * <dt><code>false</code></dt>
- * <dd>[optional] Report an fatal error if a
- * character is encountered for which the processor can not determine the
- * normalization properties. </dd>
- * </dl></dd>
- * <dt><code>"whitespace-in-element-content"</code></dt>
- * <dd>
- * This feature is equivalent to the one provided on
- * <code>Document.setNormalizationFeature</code> in . </dd>
- * </dl>
- * <p>See also the <a
href='http://www.w3.org/TR/2002/WD-DOM-Level-3-LS-20020725'>Document Object Model
(DOM) Level 3 Load
-and Save Specification</a>.
+ * <p>See also the <a
href='http://www.w3.org/TR/2002/WD-DOM-Level-3-LS-20021022'>Document Object Model
(DOM) Level 3 Load and Save Specification</a>.
*/
+
public interface DOMWriter {
- /**
- * Set the state of a feature.
- * <br>The feature name has the same form as a DOM hasFeature string.
- * <br>It is possible for a <code>DOMWriter</code> to recognize a feature
- * name but to be unable to set its value.
- * @param name The feature name.
- * @param state The requested state of the feature (<code>true</code> or
- * <code>false</code>).
- * @exception DOMException
- * NOT_SUPPORTED_ERR: Raised when the <code>DOMWriter</code> recognizes
- * the feature name but cannot set the requested value.
- * <br>Raise a NOT_FOUND_ERR When the <code>DOMWriter</code> does not
- * recognize the feature name.
- */
- public void setFeature(String name,
- boolean state)
- throws DOMException;
/**
- * Query whether setting a feature to a specific value is supported.
- * <br>The feature name has the same form as a DOM hasFeature string.
- * @param name The feature name, which is a DOM has-feature style string.
- * @param state The requested state of the feature (<code>true</code> or
- * <code>false</code>).
- * @return <code>true</code> if the feature could be successfully set to
- * the specified value, or <code>false</code> if the feature is not
- * recognized or the requested value is not supported. The value of
- * the feature itself is not changed.
+ * The configuration used when a document is loaded.
+ * <br>In addition to the boolean parameters and parameters recognized in
+ * the Core module, the <code>DOMConfiguration</code> objects for
+ * <code>DOMWriter</code> adds, or modifies, the following boolean
+ * parameters:
+ * <dl>
+ * <dt><code>"entity-resolver"</code></dt>
+ * <dd> This parameter is
+ * equivalent to the <code>"entity-resolver"</code> parameter defined in
+ * <code>DOMBuilder.config</code>. </dd>
+ * <dt><code>"xml-declaration"</code></dt>
+ * <dd>
+ * <dl>
+ * <dt>
+ * <code>true</code></dt>
+ * <dd>[required] (default) If a <code>Document</code> Node
+ * or an <code>Entity</code> node is serialized, the XML declaration, or
+ * text declaration, should be included <code>Document.version</code>
+ * and/or an encoding is specified. </dd>
+ * <dt><code>false</code></dt>
+ * <dd>[required] Do not
+ * serialize the XML and text declarations. </dd>
+ * </dl></dd>
+ * <dt><code>"canonical-form"</code></dt>
+ * <dd>
+ * <dl>
+ * <dt>
+ * <code>true</code></dt>
+ * <dd>[optional] This formatting writes the document
+ * according to the rules specified in [<a
href='http://www.w3.org/TR/2001/REC-xml-c14n-20010315'>Canonical XML</a>]. Setting
this boolean parameter
+ * to true will set the boolean parameter
+ * <code>"format-pretty-print"</code> to false. </dd>
+ * <dt><code>false</code></dt>
+ * <dd>[
+ * required] (default) Do not canonicalize the output. </dd>
+ * </dl></dd>
+ * <dt>
+ * <code>"format-pretty-print"</code></dt>
+ * <dd>
+ * <dl>
+ * <dt><code>true</code></dt>
+ * <dd>[optional]
+ * Formatting the output by adding whitespace to produce a
+ * pretty-printed, indented, human-readable form. The exact form of the
+ * transformations is not specified by this specification. Setting this
+ * boolean parameter to true will set the boolean parameter
+ * "canonical-form" to false. </dd>
+ * <dt><code>false</code></dt>
+ * <dd>[required] (default)
+ * Don't pretty-print the result. </dd>
+ * </dl></dd>
+ * <dt><code>"normalize-characters"</code></dt>
+ * <dd>
+ * This boolean parameter is equivalent to the one defined by
+ * <code>DOMConfiguration</code> in [<a
href='http://www.w3.org/TR/2002/WD-DOM-Level-3-Core-20020114'>DOM Level 3 Core</a>].
Unlike in the Core, the default
+ * value for this boolean parameter is <code>true</code>. While DOM
+ * implementations are not required to implement the W3C Text
+ * Normalization defined in [<a
href='http://www.w3.org/TR/2002/WD-charmod-20020430'>CharModel</a>], this boolean
parameter must be activated
+ * by default if supported. </dd>
+ * <dt><code>"unknown-characters"</code></dt>
+ * <dd>
+ * <dl>
+ * <dt>
+ * <code>true</code></dt>
+ * <dd>[required] (default) If, while verifying full
+ * normalization when [<a
href='http://www.w3.org/TR/2002/CR-xml11-20021015/'>XML 1.1</a>] is supported, a
character is encountered for
+ * which the normalization properties cannot be determined, then ignore
+ * any possible denormalizations caused by these characters. </dd>
+ * <dt>
+ * <code>false</code></dt>
+ * <dd>[optional] Report an fatal error if a character is
+ * encountered for which the processor can not determine the
+ * normalization properties. </dd>
+ * </dl></dd>
+ * </dl>
*/
- public boolean canSetFeature(String name,
- boolean state);
- /**
- * Look up the value of a feature.
- * <br>The feature name has the same form as a DOM hasFeature string
- * @param name The feature name, which is a string with DOM has-feature
- * syntax.
- * @return The current state of the feature (<code>true</code> or
- * <code>false</code>).
- * @exception DOMException
- * NOT_FOUND_ERR: Raised when the <code>DOMWriter</code> does not
- * recognize the feature name.
- */
- public boolean getFeature(String name)
- throws DOMException;
+ public DOMConfiguration getConfig();
+
/**
* The character encoding in which the output will be written.
@@ -339,22 +300,6 @@
*/
public void setFilter(DOMWriterFilter filter);
- /**
- * The error handler that will receive error notifications during
- * serialization. The node where the error occured is passed to this
- * error handler, any modification to nodes from within an error
- * callback should be avoided since this will result in undefined,
- * implementation dependent behavior.
- */
- public DOMErrorHandler getErrorHandler();
- /**
- * The error handler that will receive error notifications during
- * serialization. The node where the error occured is passed to this
- * error handler, any modification to nodes from within an error
- * callback should be avoided since this will result in undefined,
- * implementation dependent behavior.
- */
- public void setErrorHandler(DOMErrorHandler errorHandler);
/**
* Write out the specified node as described above in the description of
1.6 +87 -95 xml-xerces/java/src/org/w3c/dom/ls/DOMBuilder.java
Index: DOMBuilder.java
===================================================================
RCS file: /home/cvs/xml-xerces/java/src/org/w3c/dom/ls/DOMBuilder.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- DOMBuilder.java 18 Sep 2002 22:03:17 -0000 1.5
+++ DOMBuilder.java 11 Dec 2002 16:15:26 -0000 1.6
@@ -15,7 +15,7 @@
import org.w3c.dom.Document;
import org.w3c.dom.Node;
import org.w3c.dom.DOMException;
-import org.apache.xerces.dom3.DOMErrorHandler;
+import org.apache.xerces.dom3.DOMConfiguration;
/**
* <strong>DOM Level 3 WD Experimental:
@@ -185,57 +185,94 @@
and Save Specification</a>.
*/
public interface DOMBuilder {
- /**
- * If a <code>DOMEntityResolver</code> has been specified, each time a
- * reference to an external entity is encountered the
- * <code>DOMBuilder</code> will pass the public and system IDs to the
- * entity resolver, which can then specify the actual source of the
- * entity.
- * <br> If this attribute is <code>null</code>, the resolution of entities
- * in the document is implementation dependent.
- */
- public DOMEntityResolver getEntityResolver();
- /**
- * If a <code>DOMEntityResolver</code> has been specified, each time a
- * reference to an external entity is encountered the
- * <code>DOMBuilder</code> will pass the public and system IDs to the
- * entity resolver, which can then specify the actual source of the
- * entity.
- * <br> If this attribute is <code>null</code>, the resolution of entities
- * in the document is implementation dependent.
+
+ /**
+ * The configuration used when a document is loaded. The values of
+ * parameters used to load a document are not passed automatically to
+ * the <code>DOMConfiguration</code> object used by the
+ * <code>Document</code> nodes. The DOM application is responsible for
+ * passing the parameters values from the <code>DOMConfiguration</code>
+ * object referenced from <code>DOMBuilder</code> to the
+ * <code>DOMConfiguration</code> object referenced from
+ * <code>Document</code>.
+ * <br> In addition to the boolean parameters and parameters recognized in
+ * the Core module, the <code>DOMConfiguration</code> objects for
+ * <code>DOMBuider</code> adds the following boolean parameters:
+ * <dl>
+ * <dt>
+ * <code>"entity-resolver"</code></dt>
+ * <dd>[required] A
+ * <code>DOMEntityResolver</code> object. If this parameter has been
+ * specified, each time a reference to an external entity is encountered
+ * the implementation will pass the public and system IDs to the entity
+ * resolver, which can then specify the actual source of the entity. If
+ * this parameter is not set, the resolution of entities in the document
+ * is implementation dependent. When the features "LS-Load" or
+ * "LS-Save" are supported, this parameter may also be supported by the
+ * <code>DOMConfiguration</code> object referenced from the
+ * <code>Document</code> node. </dd>
+ * <dt><code>"certified"</code></dt>
+ * <dd>
+ * <dl>
+ * <dt><code>true</code></dt>
+ * <dd>[
+ * optional] Assume, when XML 1.1 is supported, that the input is
+ * certified (see section 2.13 in [<a
href='http://www.w3.org/TR/2002/CR-xml11-20021015/'>XML 1.1</a>]). </dd>
+ * <dt><code>false</code></dt>
+ * <dd>[required] (
+ * default) Don't assume that the input is certified (see section 2.13
+ * in [<a href='http://www.w3.org/TR/2002/CR-xml11-20021015/'>XML 1.1</a>]).
</dd>
+ * </dl></dd>
+ * <dt><code>"charset-overrides-xml-encoding"</code></dt>
+ * <dd>
+ * <dl>
+ * <dt><code>true</code></dt>
+ * <dd>[
+ * required] (default) If a higher level protocol such as HTTP [<a
href='http://www.ietf.org/rfc/rfc2616.txt'>IETF RFC 2616</a>] provides
+ * an indication of the character encoding of the input stream being
+ * processed, that will override any encoding specified in the XML
+ * declaration or the Text declaration (see also [<a
href='http://www.w3.org/TR/2000/REC-xml-20001006'>XML 1.0</a>] 4.3.3 "Character
+ * Encoding in Entities"). Explicitly setting an encoding in the
+ * <code>DOMInputSource</code> overrides encodings from the protocol. </dd>
+ * <dt>
+ * <code>false</code></dt>
+ * <dd>[required] Any character set encoding information
+ * from higher level protocols is ignored by the parser. </dd>
+ * </dl></dd>
+ * <dt>
+ * <code>"supported-mediatypes-only"</code></dt>
+ * <dd>
+ * <dl>
+ * <dt><code>true</code></dt>
+ * <dd>[optional]
+ * Check that the media type of the parsed resource is a supported media
+ * type and call the error handler if an unsupported media type is
+ * encountered. The media types defined in [<a
href='http://www.ietf.org/rfc/rfc3023.txt'>IETF RFC 3023</a>] must be accepted. </dd>
+ * <dt>
+ * <code>false</code></dt>
+ * <dd>[required] (default) Don't check the media type,
+ * accept any type of data. </dd>
+ * </dl></dd>
+ * <dt><code>"unknown-characters"</code></dt>
+ * <dd>
+ * <dl>
+ * <dt>
+ * <code>true</code></dt>
+ * <dd>[required] (default) If, while verifying full
+ * normalization when [<a
href='http://www.w3.org/TR/2002/CR-xml11-20021015/'>XML 1.1</a>] is supported, a
processor encounters characters
+ * for which it cannot determine the normalization properties, then the
+ * processor will ignore any possible denormalizations caused by these
+ * characters. </dd>
+ * <dt><code>false</code></dt>
+ * <dd>[optional] Report an fatal error if a
+ * character is encountered for which the processor can not determine
+ * the normalization properties. </dd>
+ * </dl></dd>
+ * </dl>
*/
- public void setEntityResolver(DOMEntityResolver entityResolver);
- /**
- * In the event that an error is encountered in the XML document being
- * parsed, the <code>DOMDocumentBuilder</code> will call back to the
- * <code>errorHandler</code> with the error information. When the
- * document loading process calls the error handler the node closest to
- * where the error occured is passed to the error handler, if the
- * implementation is unable to pass the node where the error occures the
- * document Node is passed to the error handler. In addition to passing
- * the Node closest to to where the error occured, the implementation
- * should also pass any other valuable information to the error handler,
- * such as file name, line number, and so on. Mutations to the document
- * from within an error handler will result in implementation dependent
- * behaviour.
- */
- public DOMErrorHandler getErrorHandler();
- /**
- * In the event that an error is encountered in the XML document being
- * parsed, the <code>DOMDocumentBuilder</code> will call back to the
- * <code>errorHandler</code> with the error information. When the
- * document loading process calls the error handler the node closest to
- * where the error occured is passed to the error handler, if the
- * implementation is unable to pass the node where the error occures the
- * document Node is passed to the error handler. In addition to passing
- * the Node closest to to where the error occured, the implementation
- * should also pass any other valuable information to the error handler,
- * such as file name, line number, and so on. Mutations to the document
- * from within an error handler will result in implementation dependent
- * behaviour.
- */
- public void setErrorHandler(DOMErrorHandler errorHandler);
+ public DOMConfiguration getConfig();
+
/**
* When the application provides a filter, the parser will call out to
@@ -258,51 +295,6 @@
*/
public void setFilter(DOMBuilderFilter filter);
- /**
- * Set the state of a feature.
- * <br>The feature name has the same form as a DOM hasFeature string.
- * <br>It is possible for a <code>DOMBuilder</code> to recognize a feature
- * name but to be unable to set its value.
- * @param name The feature name.
- * @param state The requested state of the feature (<code>true</code> or
- * <code>false</code>).
- * @exception DOMException
- * NOT_SUPPORTED_ERR: Raised when the <code>DOMBuilder</code> recognizes
- * the feature name but cannot set the requested value.
- * <br>NOT_FOUND_ERR: Raised when the <code>DOMBuilder</code> does not
- * recognize the feature name.
- */
- public void setFeature(String name,
- boolean state)
- throws DOMException;
-
- /**
- * Query whether setting a feature to a specific value is supported.
- * <br>The feature name has the same form as a DOM hasFeature string.
- * @param name The feature name, which is a DOM has-feature style string.
- * @param state The requested state of the feature (<code>true</code> or
- * <code>false</code>).
- * @return <code>true</code> if the feature could be successfully set to
- * the specified value, or <code>false</code> if the feature is not
- * recognized or the requested value is not supported. The value of
- * the feature itself is not changed.
- */
- public boolean canSetFeature(String name,
- boolean state);
-
- /**
- * Look up the value of a feature.
- * <br>The feature name has the same form as a DOM hasFeature string
- * @param name The feature name, which is a string with DOM has-feature
- * syntax.
- * @return The current state of the feature (<code>true</code> or
- * <code>false</code>).
- * @exception DOMException
- * NOT_FOUND_ERR: Raised when the <code>DOMBuilder</code> does not
- * recognize the feature name.
- */
- public boolean getFeature(String name)
- throws DOMException;
/**
* Parse an XML document from a location identified by a URI reference .
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
