--- old/src/java.xml/share/classes/org/w3c/dom/ls/LSParser.java 2017-12-11 12:46:40.890536445 -0800 +++ new/src/java.xml/share/classes/org/w3c/dom/ls/LSParser.java 2017-12-11 12:46:39.939443589 -0800 @@ -53,7 +53,8 @@ * corresponding DOM document structure. A LSParser instance * can be obtained by invoking the * DOMImplementationLS.createLSParser() method. - *

As specified in [DOM Level 3 Core] + *

As specified in + * [DOM Level 3 Core] * , when a document is first made available via the LSParser: *

*

Asynchronous LSParser objects are expected to also @@ -102,17 +105,18 @@ *

Note: All events defined in this specification use the * namespace URI "http://www.w3.org/2002/DOMLS". *

While parsing an input source, errors are reported to the application - * through the error handler (LSParser.domConfig's " - * error-handler" parameter). This specification does in no way try to define all possible + * through the error handler (LSParser.domConfig's + * "error-handler" + * parameter). This specification does in no way try to define all possible * errors that can occur while parsing XML, or any other markup, but some * common error cases are defined. The types (DOMError.type) of * errors and warnings defined by this specification are: *

*
* "check-character-normalization-failure" [error]
- *
Raised if - * the parameter " - * check-character-normalization" is set to true and a string is encountered that fails normalization + *
Raised if the parameter + * "check-character-normalization" + * is set to true and a string is encountered that fails normalization * checking.
*
"doctype-not-allowed" [fatal]
*
Raised if the @@ -127,8 +131,9 @@ *
Raised if a processing * instruction is encountered in a location where the base URI of the * processing instruction can not be preserved. One example of a case where - * this warning will be raised is if the configuration parameter " - * entities" is set to false and the following XML file is parsed: + * this warning will be raised is if the configuration parameter + * "entities" + * is set to false and the following XML file is parsed: *
  * <!DOCTYPE root [ <!ENTITY e SYSTEM 'subdir/myentity.ent' ]>
  * <root> &e; </root>
@@ -139,9 +144,9 @@ *
*
"unbound-prefix-in-entity" [warning]
*
An - * implementation dependent warning that may be raised if the configuration - * parameter " - * namespaces" is set to true and an unbound namespace prefix is + * implementation dependent warning that may be raised if the configuration parameter + * "namespaces" + * is set to true and an unbound namespace prefix is * encountered in an entity's replacement text. Raising this warning is not * enforced since some existing parsers may not recognize unbound namespace * prefixes in the replacement text of entities.
@@ -164,8 +169,8 @@ * are expected to raise implementation specific errors and warnings for any * other error and warning cases such as IO errors (file not found, * permission denied,...), XML well-formedness errors, and so on. - *

See also the Document Object Model (DOM) Level 3 Load -and Save Specification. + *

See also the + * Document Object Model (DOM) Level 3 Load and Save Specification. * * @since 1.5 */ @@ -180,8 +185,10 @@ * needed parameter values from this DOMConfiguration * object to the DOMConfiguration object referenced by the * Document object. - *
In addition to the parameters recognized in on the - * DOMConfiguration interface defined in [DOM Level 3 Core] + *
In addition to the parameters recognized in on the + * DOMConfiguration + * interface defined in + * [DOM Level 3 Core] * , the DOMConfiguration objects for LSParser * add or modify the following parameters: *

@@ -190,7 +197,8 @@ *
*
*
true
- *
[optional] (default) If a higher level protocol such as HTTP [IETF RFC 2616] provides an + *
[optional] (default) If a higher level protocol such as HTTP + * [IETF RFC 2616] 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 section 4.3.3, @@ -206,7 +214,8 @@ *
*
* true
- *
[optional] Throw a fatal "doctype-not-allowed" error if a doctype node is found while parsing the document. This is + *
[optional] Throw a fatal "doctype-not-allowed" error + * if a doctype node is found while parsing the document. This is * useful when dealing with things like SOAP envelopes where doctype * nodes are not allowed.
*
false
@@ -218,14 +227,17 @@ *
*
* true
- *
[required] (default) If, while verifying full normalization when [XML 1.1] is + *
[required] (default) If, while verifying full normalization when + * [XML 1.1] 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. - * This parameter is ignored for [XML 1.0].
+ * This parameter is ignored for [XML 1.0]. + *
*
* false
- *
[optional] Report an fatal "unknown-character-denormalization" error if a character is encountered for which the processor cannot + *
[optional] Report an fatal "unknown-character-denormalization" + * error if a character is encountered for which the processor cannot * determine the normalization properties.
*
*
"infoset"
@@ -238,7 +250,8 @@ *
*
*
true
- *
[required] (default) Perform the namespace processing as defined in [XML Namespaces] + *
[required] (default) Perform the namespace processing as defined in + * [XML Namespaces] * and [XML Namespaces 1.1] * .
*
false
@@ -259,7 +272,8 @@ * true *
[optional] Check that the media type of the parsed resource is a supported media * type. If an unsupported media type is encountered, a fatal error of - * type "unsupported-media-type" will be raised. The media types defined in [IETF RFC 3023] must always + * type "unsupported-media-type" will be raised. The media types defined in + * [IETF RFC 3023] must always * be accepted.
*
false
*
[required] (default) Accept any media type.
@@ -294,8 +308,8 @@ * terminate the parsing early. *
The filter is invoked after the operations requested by the * DOMConfiguration parameters have been applied. For - * example, if " - * validate" is set to true, the validation is done before invoking the + * example, if "validate" + * is set to true, the validation is done before invoking the * filter. */ public LSParserFilter getFilter(); @@ -306,8 +320,8 @@ * terminate the parsing early. *
The filter is invoked after the operations requested by the * DOMConfiguration parameters have been applied. For - * example, if " - * validate" is set to true, the validation is done before invoking the + * example, if "validate" + * is set to true, the validation is done before invoking the * filter. */ public void setFilter(LSParserFilter filter); @@ -340,15 +354,18 @@ * @exception LSException * PARSE_ERR: Raised if the LSParser was unable to load * the XML document. DOM applications should attach a - * DOMErrorHandler using the parameter " - * error-handler" if they wish to get details on the error. + * DOMErrorHandler using the parameter + * "error-handler" + * if they wish to get details on the error. */ public Document parse(LSInput input) throws DOMException, LSException; /** - * Parse an XML document from a location identified by a URI reference [IETF RFC 2396]. If the URI - * contains a fragment identifier (see section 4.1 in [IETF RFC 2396]), the + * Parse an XML document from a location identified by a URI reference + * [IETF RFC 2396]. If the URI + * contains a fragment identifier (see section 4.1 in + * [IETF RFC 2396]), the * behavior is not defined by this specification, future versions of * this specification may define the behavior. * @param uri The location of the XML document to be read. @@ -364,8 +381,9 @@ * @exception LSException * PARSE_ERR: Raised if the LSParser was unable to load * the XML document. DOM applications should attach a - * DOMErrorHandler using the parameter " - * error-handler" if they wish to get details on the error. + * DOMErrorHandler using the parameter + * "error-handler" + * if they wish to get details on the error. */ public Document parseURI(String uri) throws DOMException, LSException; @@ -431,14 +449,17 @@ * LSParser is asynchronous (LSParser.async is * true). *
If an error occurs while parsing, the caller is notified through - * the ErrorHandler instance associated with the " - * error-handler" parameter of the DOMConfiguration. + * the ErrorHandler instance associated with the + * "error-handler" + * parameter of the DOMConfiguration. *
When calling parseWithContext, the values of the * following configuration parameters will be ignored and their default - * values will always be used instead: " - * validate", " - * validate-if-schema", and " - * element-content-whitespace". Other parameters will be treated normally, and the parser is expected + * values will always be used instead: + * "validate", + * "validate-if-schema", + * and + * "element-content-whitespace". + * Other parameters will be treated normally, and the parser is expected * to call the LSParserFilter just as if a whole document * was parsed. * @param input The LSInput from which the source document @@ -463,7 +484,8 @@ * @exception DOMException * HIERARCHY_REQUEST_ERR: Raised if the content cannot replace, be * inserted before, after, or as a child of the context node (see also - * Node.insertBefore or Node.replaceChild in [DOM Level 3 Core] + * Node.insertBefore or Node.replaceChild in + * [DOM Level 3 Core] * ). *
NOT_SUPPORTED_ERR: Raised if the LSParser doesn't * support this method, or if the context node is of type @@ -479,8 +501,9 @@ * @exception LSException * PARSE_ERR: Raised if the LSParser was unable to load * the XML fragment. DOM applications should attach a - * DOMErrorHandler using the parameter " - * error-handler" if they wish to get details on the error. + * DOMErrorHandler using the parameter + * "error-handler" + * if they wish to get details on the error. */ public Node parseWithContext(LSInput input, Node contextArg,