Examples of DOMConfiguration

org.apache.xerces.dom3.DOMConfiguration
3.org/TR/2003/WD-DOM-Level-3-LS-20030226'>DOM Level 3 Load and Save] in the DOMParser and DOMSerializer interfaces.
The parameter names used by the DOMConfiguration object are defined throughout the DOM Level 3 specifications. Names are case-insensitives. To avoid possible conflicts, as a convention, names referring to parameters defined outside the DOM specification should be made unique. Because parameters are exposed as properties in the , names are recommended to follow the section 5.16 Identifiers of [Unicode] with the addition of the character '-' (HYPHEN-MINUS) but it is not enforced by the DOM implementation. DOM Level 3 Core Implementations are required to recognize all parameters defined in this specification. Some parameter values may also be required to be supported by the implementation. Refer to the definition of the parameter to know if a value must be supported or not.
Note: Parameters are similar to features and properties used in SAX2 [SAX].
The following list of parameters defined in the DOM:
"canonical-form"

true

[optional]Canonicalize the document according to the rules specified in [Canonical XML]. Note that this is limited to what can be represented in the DOM. In particular, there is no way to specify the order of the attributes in the DOM.This forces the following parameters to false: "entities ", "normalize-characters", "cdata-sections".This forces the following parameters to true: "namespaces", "namespace-declarations", " well-formed", "whitespace-in-element-content".Other parameters are not changed unless explicitly specified in the description of the parameters. In addition, the DocumentType node is removed from the tree if any and superfluous namespace declarations are removed from each element. Note that querying this parameter with getParameter cannot return true unless it has been set to true and the parameters described above are appropriately set.

false

[required] (default)Do not canonicalize the document.

"cdata-sections"

true

[required] (default)Keep CDATASection nodes in the document.

false

[required]Transform CDATASection nodes in the document into Text nodes. The new Text node is then combined with any adjacent Text node.

"check-character-normalization"

true

[optional] Check if the characters in the document are fully normalized according to the rules defined in [CharModel] supplemented by the definitions of relevant constructs from Section 2.13 of [XML 1.1].

false

[required] (default)Do not check if characters are normalized.

"comments"

true

[required] (default)Keep Comment nodes in the document.

false

[required]Discard Comment nodes in the document.

"datatype-normalization"

true

[required] Exposed schema-normalized values in the tree. Since this parameter requires to have schema information, the "validate" parameter will also be set to true. Having this parameter activated when "validate" is false has no effect and no schema-normalization will happen.
Note: Since the document contains the result of the XML 1.0 processing, this parameter does not apply to attribute value normalization as defined in section 3.3.3 of [XML 1.0] and is only meant for schema languages other than Document Type Definition (DTD).

false

[required] (default) Do not perform schema normalization on the tree.

"entities"

true

[required] (default)Keep EntityReference and Entity nodes in the document.

false

[required] Remove all EntityReference and Entity nodes from the document, putting the entity expansions directly in their place. Text nodes are normalized, as defined in Node.normalize. Only EntityReference nodes to non-defined entities are kept in the document, with their associated Entity nodes if any.

"error-handler"

[required] Contains a DOMErrorHandler object. If an error is encountered in the document, the implementation will call back the DOMErrorHandler registered using this parameter. When called, DOMError.relatedData will contain the closest node to where the error occurred. If the implementation is unable to determine the node where the error occurs, DOMError.relatedData will contain the Document node. Mutations to the document from within an error handler will result in implementation dependent behavior.

"infoset"

true

[required]Keep in the document the information defined in the XML Information Set [XML Information set] .This forces the following parameters to false: " validate-if-schema", "entities", "datatype-normalization", "cdata-sections ".This forces the following parameters to true: " namespace-declarations", "well-formed", "whitespace-in-element-content", " comments", "namespaces".Other parameters are not changed unless explicitly specified in the description of the parameters. Note that querying this parameter with getParameter returns true only if the individual parameters specified above are appropriately set.

false

Setting infoset to false has no effect.

"namespaces"

true

[required] (default) Perform the namespace processing as defined in .

false

[optional] Do not perform the namespace processing.

"namespace-declarations"

true

[required] (default) Include namespace declaration attributes, specified or defaulted from the schema, in the document. See also the sections "Declaring Namespaces" in [XML Namespaces] and [XML Namespaces 1.1] .

false

[required]Discard all namespace declaration attributes. The namespace prefixes ( Node.prefix) are retained even if this parameter is set to false.

"normalize-characters"

true

[optional] Fully normalize the characters in the document according to the rules defined in [CharModel] supplemented by the definitions of relevant constructs from Section 2.13 of [XML 1.1].

false

[required] (default)Do not perform character normalization.

"schema-location"

[optional] Represent a DOMString object containing a list of URIs, separated by whitespaces (characters matching the nonterminal production S defined in section 2.3 [XML 1.0]), that represents the schemas against which validation should occur, i.e. the current schema. The types of schemas referenced in this list must match the type specified with schema-type, otherwise the behavior of an implementation is undefined. The schemas specified using this property take precedence to the schema information specified in the document itself. For namespace aware schema, if a schema specified using this property and a schema specified in the document instance (i.e. using the schemaLocation attribute) in a schema document (i.e. using schema import mechanisms) share the same targetNamespace, the schema specified by the user using this property will be used. If two schemas specified using this property share the same targetNamespace or have no namespace, the behavior is implementation dependent. If no location has been provided, this parameter is null.
Note: It is illegal to set the "schema-location" parameter if the "schema-type" parameter value is not set. It is strongly recommended that Document.documentURI will be set so that an implementation can successfully resolve any external entities referenced.

"schema-type"

[optional] Represent a DOMString object containing an absolute URI and representing the type of the schema language used to validate a document against. Note that no lexical checking is done on the absolute URI. If this parameter is not set, a default value may be provided by the implementation, based on the schema languages supported and on the schema language used at load time. If no value is provided, this parameter is null.
Note: For XML Schema [XML Schema Part 1] , applications must use the value "http://www.w3.org/2001/XMLSchema". For XML DTD [XML 1.0], applications must use the value "http://www.w3.org/TR/REC-xml". Other schema languages are outside the scope of the W3C and therefore should recommend an absolute URI in order to use this method.

"split-cdata-sections"

true

[required] (default)Split CDATA sections containing the CDATA section termination marker ']]>'. When a CDATA section is split a warning is issued with a DOMError.type equals to "cdata-sections-splitted" and DOMError.relatedData equals to the first CDATASection node in document order resulting from the split.

false

[required]Signal an error if a CDATASection contains an unrepresentable character.

"validate"
true

[optional] Require the validation against a schema (i.e. XML schema, DTD, any other type or representation of schema) of the document as it is being normalized as defined by [XML 1.0]. If validation errors are found, or no schema was found, the error handler is notified. Schema-normalized values will not be exposed according to the schema in used unless the parameter "datatype-normalization" is true. This parameter will reevaluate:

Attribute nodes with Attr.specified equals to false, as specified in the description of the Attr interface;

The result of the method Text.isWhitespaceInElementContent() for all Text nodes;

The result of the method Attr.isId() for all Attr nodes;

The attributes Element.schemaTypeInfo and Attr.schemaTypeInfo.

Note: "validate-if-schema" and "validate" are mutually exclusive, setting one of them to true will set the other one to false. Applications should also consider setting the parameter "well-formed" to true, which is the default for that option, when validating the document.

false

[required] (default) Do not accomplish schema processing, including the internal subset processing. Note that validation might still happen if " "validate-if-schema" is true.
"validate-if-schema"

true

[optional]Enable validation only if a declaration for the document element can be found in a schema (independently of where it is found, i.e. XML schema, DTD, or any other type or representation of schema). If validation is enabled, this parameter has the same behavior as the parameter "validate" set to true.
Note: "validate-if-schema" and "validate" are mutually exclusive, setting one of them to true will set the other one to false.

false

[required] (default) No schema processing should be performed if the document has a schema, including internal subset processing. Note that validation must still happen if "validate" is true.

"well-formed"
true

[required] (default) Check if all nodes are XML well formed according to the XML version in use in Document.xmlVersion:

check if the attribute Node.nodeName contains invalid characters according to its node type and generate a DOMError of type "wf-invalid-character-in-node-name" if necessary;

check if the text content inside Attr, Element, Comment, Text, CDATASection nodes for invalid characters and generate a DOMError of type "wf-invalid-character" if necessary;

check if the data inside ProcessingInstruction nodes for invalid characters and generate a DOMError of type "wf-invalid-character" if necessary;

false

[optional] Do not check for XML well-formedness.
"whitespace-in-element-content"

true

[required] (default)Keep all whitespaces in the document.

false

[optional] Discard all Text nodes that contain whitespaces in element content. The implementation is expected to use the method Text.isWhitespaceInElementContent to determine if a Text node should be discarded or not.
The resolution of the system identifiers associated with entities is done using Document.documentURI. However, when the feature "LS" defined in [DOM Level 3 Load and Save] is supported by the DOM implementation, the parameter "resource-resolver" can also be used on DOMConfiguration objects attached to Document nodes. If this parameter is set, Document.normalizeDocument() will invoke the entity resolver instead of using Document.documentURI.
See also the Document Object Model (DOM) Level 3 Core Specification. @since DOM Level 3
org.w3c.dom.DOMConfiguration
3.org/TR/2003/WD-DOM-Level-3-LS-20030226'>DOM Level 3 Load and Save] in the DOMParser and DOMSerializer interfaces.
The parameter names used by the DOMConfiguration object are defined throughout the DOM Level 3 specifications. Names are case-insensitives. To avoid possible conflicts, as a convention, names referring to parameters defined outside the DOM specification should be made unique. Because parameters are exposed as properties in the , names are recommended to follow the section 5.16 Identifiers of [Unicode] with the addition of the character '-' (HYPHEN-MINUS) but it is not enforced by the DOM implementation. DOM Level 3 Core Implementations are required to recognize all parameters defined in this specification. Some parameter values may also be required to be supported by the implementation. Refer to the definition of the parameter to know if a value must be supported or not.
Note: Parameters are similar to features and properties used in SAX2 [SAX].
The following list of parameters defined in the DOM:
"canonical-form"

true

[optional]Canonicalize the document according to the rules specified in [Canonical XML]. Note that this is limited to what can be represented in the DOM. In particular, there is no way to specify the order of the attributes in the DOM.This forces the following parameters to false: "entities ", "normalize-characters", "cdata-sections".This forces the following parameters to true: "namespaces", "namespace-declarations", " well-formed", "whitespace-in-element-content".Other parameters are not changed unless explicitly specified in the description of the parameters. In addition, the DocumentType node is removed from the tree if any and superfluous namespace declarations are removed from each element. Note that querying this parameter with getParameter cannot return true unless it has been set to true and the parameters described above are appropriately set.

false

[required] (default)Do not canonicalize the document.

"cdata-sections"

true

[required] (default)Keep CDATASection nodes in the document.

false

[required]Transform CDATASection nodes in the document into Text nodes. The new Text node is then combined with any adjacent Text node.

"check-character-normalization"

true

[optional] Check if the characters in the document are fully normalized according to the rules defined in [CharModel] supplemented by the definitions of relevant constructs from Section 2.13 of [XML 1.1].

false

[required] (default)Do not check if characters are normalized.

"comments"

true

[required] (default)Keep Comment nodes in the document.

false

[required]Discard Comment nodes in the document.

"datatype-normalization"

true

[required] Exposed schema-normalized values in the tree. Since this parameter requires to have schema information, the "validate" parameter will also be set to true. Having this parameter activated when "validate" is false has no effect and no schema-normalization will happen.
Note: Since the document contains the result of the XML 1.0 processing, this parameter does not apply to attribute value normalization as defined in section 3.3.3 of [XML 1.0] and is only meant for schema languages other than Document Type Definition (DTD).

false

[required] (default) Do not perform schema normalization on the tree.

"entities"

true

[required] (default)Keep EntityReference and Entity nodes in the document.

false

[required] Remove all EntityReference and Entity nodes from the document, putting the entity expansions directly in their place. Text nodes are normalized, as defined in Node.normalize. Only EntityReference nodes to non-defined entities are kept in the document, with their associated Entity nodes if any.

"error-handler"

[required] Contains a DOMErrorHandler object. If an error is encountered in the document, the implementation will call back the DOMErrorHandler registered using this parameter. When called, DOMError.relatedData will contain the closest node to where the error occurred. If the implementation is unable to determine the node where the error occurs, DOMError.relatedData will contain the Document node. Mutations to the document from within an error handler will result in implementation dependent behavior.

"infoset"

true

[required]Keep in the document the information defined in the XML Information Set [XML Information set] .This forces the following parameters to false: " validate-if-schema", "entities", "datatype-normalization", "cdata-sections ".This forces the following parameters to true: " namespace-declarations", "well-formed", "whitespace-in-element-content", " comments", "namespaces".Other parameters are not changed unless explicitly specified in the description of the parameters. Note that querying this parameter with getParameter returns true only if the individual parameters specified above are appropriately set.

false

Setting infoset to false has no effect.

"namespaces"

true

[required] (default) Perform the namespace processing as defined in .

false

[optional] Do not perform the namespace processing.

"namespace-declarations"

true

[required] (default) Include namespace declaration attributes, specified or defaulted from the schema, in the document. See also the sections "Declaring Namespaces" in [XML Namespaces] and [XML Namespaces 1.1] .

false

[required]Discard all namespace declaration attributes. The namespace prefixes ( Node.prefix) are retained even if this parameter is set to false.

"normalize-characters"

true

[optional] Fully normalize the characters in the document according to the rules defined in [CharModel] supplemented by the definitions of relevant constructs from Section 2.13 of [XML 1.1].

false

[required] (default)Do not perform character normalization.

"schema-location"

[optional] Represent a DOMString object containing a list of URIs, separated by whitespaces (characters matching the nonterminal production S defined in section 2.3 [XML 1.0]), that represents the schemas against which validation should occur, i.e. the current schema. The types of schemas referenced in this list must match the type specified with schema-type, otherwise the behavior of an implementation is undefined. The schemas specified using this property take precedence to the schema information specified in the document itself. For namespace aware schema, if a schema specified using this property and a schema specified in the document instance (i.e. using the schemaLocation attribute) in a schema document (i.e. using schema import mechanisms) share the same targetNamespace, the schema specified by the user using this property will be used. If two schemas specified using this property share the same targetNamespace or have no namespace, the behavior is implementation dependent. If no location has been provided, this parameter is null.
Note: It is illegal to set the "schema-location" parameter if the "schema-type" parameter value is not set. It is strongly recommended that Document.documentURI will be set so that an implementation can successfully resolve any external entities referenced.

"schema-type"

[optional] Represent a DOMString object containing an absolute URI and representing the type of the schema language used to validate a document against. Note that no lexical checking is done on the absolute URI. If this parameter is not set, a default value may be provided by the implementation, based on the schema languages supported and on the schema language used at load time. If no value is provided, this parameter is null.
Note: For XML Schema [XML Schema Part 1] , applications must use the value "http://www.w3.org/2001/XMLSchema". For XML DTD [XML 1.0], applications must use the value "http://www.w3.org/TR/REC-xml". Other schema languages are outside the scope of the W3C and therefore should recommend an absolute URI in order to use this method.

"split-cdata-sections"

true

[required] (default)Split CDATA sections containing the CDATA section termination marker ']]>'. When a CDATA section is split a warning is issued with a DOMError.type equals to "cdata-sections-splitted" and DOMError.relatedData equals to the first CDATASection node in document order resulting from the split.

false

[required]Signal an error if a CDATASection contains an unrepresentable character.

"validate"
true

[optional] Require the validation against a schema (i.e. XML schema, DTD, any other type or representation of schema) of the document as it is being normalized as defined by [XML 1.0]. If validation errors are found, or no schema was found, the error handler is notified. Schema-normalized values will not be exposed according to the schema in used unless the parameter "datatype-normalization" is true. This parameter will reevaluate:

Attribute nodes with Attr.specified equals to false, as specified in the description of the Attr interface;

The result of the method Text.isWhitespaceInElementContent() for all Text nodes;

The result of the method Attr.isId() for all Attr nodes;

The attributes Element.schemaTypeInfo and Attr.schemaTypeInfo.

Note: "validate-if-schema" and "validate" are mutually exclusive, setting one of them to true will set the other one to false. Applications should also consider setting the parameter "well-formed" to true, which is the default for that option, when validating the document.

false

[required] (default) Do not accomplish schema processing, including the internal subset processing. Note that validation might still happen if " "validate-if-schema" is true.
"validate-if-schema"

true

[optional]Enable validation only if a declaration for the document element can be found in a schema (independently of where it is found, i.e. XML schema, DTD, or any other type or representation of schema). If validation is enabled, this parameter has the same behavior as the parameter "validate" set to true.
Note: "validate-if-schema" and "validate" are mutually exclusive, setting one of them to true will set the other one to false.

false

[required] (default) No schema processing should be performed if the document has a schema, including internal subset processing. Note that validation must still happen if "validate" is true.

"well-formed"
true

[required] (default) Check if all nodes are XML well formed according to the XML version in use in Document.xmlVersion:

check if the attribute Node.nodeName contains invalid characters according to its node type and generate a DOMError of type "wf-invalid-character-in-node-name" if necessary;

check if the text content inside Attr, Element, Comment, Text, CDATASection nodes for invalid characters and generate a DOMError of type "wf-invalid-character" if necessary;

check if the data inside ProcessingInstruction nodes for invalid characters and generate a DOMError of type "wf-invalid-character" if necessary;

false

[optional] Do not check for XML well-formedness.
"whitespace-in-element-content"

true

[required] (default)Keep all whitespaces in the document.

false

[optional] Discard all Text nodes that contain whitespaces in element content. The implementation is expected to use the method Text.isWhitespaceInElementContent to determine if a Text node should be discarded or not.
The resolution of the system identifiers associated with entities is done using Document.documentURI. However, when the feature "LS" defined in [DOM Level 3 Load and Save] is supported by the DOM implementation, the parameter "resource-resolver" can also be used on DOMConfiguration objects attached to Document nodes. If this parameter is set, Document.normalizeDocument() will invoke the entity resolver instead of using Document.documentURI.
See also the Document Object Model (DOM) Level 3 Core Specification. @since DOM Level 3

Examples of org.w3c.dom.DOMConfiguration

            }
        });
        
        
        if (serializerParams != null) {
            DOMConfiguration serializerDOMConfig = serializer.getDomConfig();
            for (String key : serializerParams.keySet()) {
                serializerDOMConfig.setParameter(key, serializerParams.get(key));
            }
        }
        
        return serializer;
    }

View Full Code Here

Examples of org.w3c.dom.DOMConfiguration

                (DOMImplementationLS)registry.getDOMImplementation("LS-Load");


            // create DOMBuilder
            builder = impl.createDOMBuilder(DOMImplementationLS.MODE_SYNCHRONOUS, null);
            
            DOMConfiguration config = builder.getConfig();


            // create Error Handler
            DOMErrorHandler errorHandler = new DOM3();
            
            // create filter
            DOMBuilderFilter filter = new DOM3();
            
            builder.setFilter(filter);


            // set error handler
            config.setParameter("error-handler", errorHandler);




            // set validation feature
            //config.setParameter("validate", Boolean.FALSE);
            config.setParameter("validate",Boolean.TRUE);
            
            // set schema language
            config.setParameter("schema-type", "http://www.w3.org/2001/XMLSchema");
            //config.setParameter("psvi",Boolean.TRUE);
            //config.setParameter("schema-type","http://www.w3.org/TR/REC-xml");
            
            // set schema location
            config.setParameter("schema-location","personal.xsd");
            
            // parse document
            System.out.println("Parsing "+argv[0]+"...");
            Document doc = builder.parseURI(argv[0]);


            // set error handler on the Document
            config = doc.getConfig();
            
            config.setParameter("error-handler", errorHandler);


            // set validation feature
            config.setParameter("validate", Boolean.TRUE);
            config.setParameter("schema-type", "http://www.w3.org/2001/XMLSchema");
            //config.setParameter("schema-type","http://www.w3.org/TR/REC-xml");
            config.setParameter("schema-location","data/personal.xsd");
            
            // remove comments from the document
            config.setParameter("comments", Boolean.FALSE);


            System.out.println("Normalizing document... ");
            doc.normalizeDocument();




            // create DOMWriter
            DOMWriter domWriter = impl.createDOMWriter();
            
            System.out.println("Serializing document... ");
            config = domWriter.getConfig();
            config.setParameter("xml-declaration", Boolean.FALSE);
            //config.setParameter("validate",errorHandler);


            // serialize document to standard output
            domWriter.writeNode(System.out, doc);

View Full Code Here

Examples of org.w3c.dom.DOMConfiguration

                (DOMImplementationLS)registry.getDOMImplementation("LS");


            // create DOMBuilder
            builder = impl.createLSParser(DOMImplementationLS.MODE_SYNCHRONOUS, null);
            
            DOMConfiguration config = builder.getDomConfig();


            // create Error Handler
            DOMErrorHandler errorHandler = new DOM3();
            
            // create filter
            LSParserFilter filter = new DOM3();
            
            builder.setFilter(filter);


            // set error handler
            config.setParameter("error-handler", errorHandler);




            // set validation feature
            //config.setParameter("validate", Boolean.FALSE);
            config.setParameter("validate",Boolean.TRUE);
            
            // set schema language
            config.setParameter("schema-type", "http://www.w3.org/2001/XMLSchema");
            //config.setParameter("psvi",Boolean.TRUE);
            //config.setParameter("schema-type","http://www.w3.org/TR/REC-xml");
            
            // set schema location
            config.setParameter("schema-location","personal.xsd");
            
            // parse document
            System.out.println("Parsing "+argv[0]+"...");
            Document doc = builder.parseURI(argv[0]);


            // set error handler on the Document
            config = doc.getDomConfig();
            
            config.setParameter("error-handler", errorHandler);


            // set validation feature
            config.setParameter("validate", Boolean.TRUE);
            config.setParameter("schema-type", "http://www.w3.org/2001/XMLSchema");
            //config.setParameter("schema-type","http://www.w3.org/TR/REC-xml");
            config.setParameter("schema-location","data/personal.xsd");
            
            // remove comments from the document
            config.setParameter("comments", Boolean.FALSE);


            System.out.println("Normalizing document... ");
            doc.normalizeDocument();




            // create DOMWriter
            LSSerializer domWriter = impl.createLSSerializer();
            
            System.out.println("Serializing document... ");
            config = domWriter.getDomConfig();
            config.setParameter("xml-declaration", Boolean.FALSE);
            //config.setParameter("validate",errorHandler);


            // serialize document to standard output
            //domWriter.writeNode(System.out, doc);
            LSOutput dOut = new DOMOutputImpl();

View Full Code Here

Examples of org.w3c.dom.DOMConfiguration

  }
  
  private static Document parse(LSInput input, boolean validateIfSchema) {
    DOMImplementationLS impl = getDOMImpl();
    LSParser parser = impl.createLSParser(DOMImplementationLS.MODE_SYNCHRONOUS, null);
    DOMConfiguration config = parser.getDomConfig();
    config.setParameter("element-content-whitespace", false);
    config.setParameter("namespaces", true);
    config.setParameter("validate-if-schema", validateIfSchema);
    return parser.parse(input);
  }

View Full Code Here

Examples of org.w3c.dom.DOMConfiguration

    config.setParameter("validate-if-schema", validateIfSchema);
    return parser.parse(input);
  }  


  public static void validate(Document d, String schema, DOMErrorHandler handler) {
    DOMConfiguration config = d.getDomConfig();
    config.setParameter("schema-type", "http://www.w3.org/2001/XMLSchema");
    config.setParameter("validate", true);
    config.setParameter("schema-location", schema);
    config.setParameter("resource-resolver", new ClasspathResourceResolver());
    config.setParameter("error-handler", handler);
    d.normalizeDocument();
  }

View Full Code Here

Examples of org.w3c.dom.DOMConfiguration


  public static String serialize(Document document) {
    DOMImplementationLS impl = getDOMImpl();
    LSSerializer serializer = impl.createLSSerializer();
    // document.normalizeDocument();
    DOMConfiguration config = serializer.getDomConfig();
    config.setParameter("xml-declaration", true);
    config.setParameter("format-pretty-print", true);
    LSOutput output = impl.createLSOutput();
    output.setEncoding("UTF-8");
    Writer writer = new StringWriter();
    output.setCharacterStream(writer);
    serializer.write(document, output);

View Full Code Here

Examples of org.w3c.dom.DOMConfiguration

            }
        });
        
        
        if (serializerParams != null) {
            DOMConfiguration serializerDOMConfig = serializer.getDomConfig();
            for (String key : serializerParams.keySet()) {
                serializerDOMConfig.setParameter(key, serializerParams.get(key));
            }
        }
        
        return serializer;
    }

View Full Code Here

Examples of org.w3c.dom.DOMConfiguration

    if (domImplementation.hasFeature("LS", "3.0")
        && domImplementation.hasFeature("Core", "2.0")) {
      DOMImplementationLS domImplementationLS = (DOMImplementationLS) domImplementation
          .getFeature("LS", "3.0");
      LSSerializer lsSerializer = domImplementationLS.createLSSerializer();
      DOMConfiguration domConfiguration = lsSerializer.getDomConfig();
      if (domConfiguration.canSetParameter("format-pretty-print", Boolean.TRUE)) {
        lsSerializer.getDomConfig().setParameter("format-pretty-print", Boolean.TRUE);
        LSOutput lsOutput = domImplementationLS.createLSOutput();
        lsOutput.setEncoding("UTF-8");
        StringWriter stringWriter = new StringWriter();
        lsOutput.setCharacterStream(stringWriter);

View Full Code Here

Examples of org.w3c.dom.DOMConfiguration

        super(dbf);
    }


    protected void runTest() throws Throwable {
        Document document = dbf.newDocumentBuilder().newDocument();
        DOMConfiguration domConfig = document.getDomConfig();
        assertEquals(Boolean.FALSE, domConfig.getParameter("canonical-form"));
        assertEquals(Boolean.TRUE, domConfig.getParameter("cdata-sections"));
        assertEquals(Boolean.FALSE, domConfig.getParameter("check-character-normalization"));
        assertEquals(Boolean.TRUE, domConfig.getParameter("comments"));
        assertEquals(Boolean.FALSE, domConfig.getParameter("datatype-normalization"));
        assertEquals(Boolean.TRUE, domConfig.getParameter("element-content-whitespace"));
        assertEquals(Boolean.TRUE, domConfig.getParameter("entities"));
        assertEquals(Boolean.TRUE, domConfig.getParameter("namespaces"));
        assertEquals(Boolean.TRUE, domConfig.getParameter("namespace-declarations"));
        assertEquals(Boolean.FALSE, domConfig.getParameter("normalize-characters"));
        assertEquals(Boolean.TRUE, domConfig.getParameter("split-cdata-sections"));
        assertEquals(Boolean.FALSE, domConfig.getParameter("validate"));
        assertEquals(Boolean.FALSE, domConfig.getParameter("validate-if-schema"));
        assertEquals(Boolean.TRUE, domConfig.getParameter("well-formed"));
    }

View Full Code Here

Examples of org.w3c.dom.DOMConfiguration


    protected void runTest() throws Throwable {
        Document document = dbf.newDocumentBuilder().newDocument();
        Element element = document.createElementNS("urn:ns", "root");
        document.appendChild(element);
        DOMConfiguration domConfig = document.getDomConfig();
        domConfig.setParameter("split-cdata-sections", Boolean.FALSE);
        domConfig.setParameter("well-formed", Boolean.FALSE);
        domConfig.setParameter("namespaces", Boolean.TRUE);
        document.normalizeDocument();
        NamedNodeMap attributes = element.getAttributes();
        assertEquals(1, attributes.getLength());
        Attr attr = (Attr)attributes.item(0);
        assertNull(attr.getPrefix());

View Full Code Here

0 1 2 3 4 5

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.