- Implementation Note:
Implementation Specific Features and PropertiesIn addition to the standard features and properties described within the public APIs of this module, the JDK implementation supports a further number of implementation specific features and properties. This section describes the naming convention, System Properties, jaxp.properties, scope and order, and processors to which a property applies. A table listing the implementation specific features and properties which the implementation currently supports can be found at the end of this note.
Naming ConventionThe names of the features and properties are fully qualified, composed of a prefix and name.
PrefixThe prefix for JDK properties is defined as:
NameA name may consist of one or multiple words that are case-sensitive. All letters of the first word are in lowercase, while the first letter of each subsequent word is capitalized.
An example of a property that indicates whether an XML document is standalone would thus have a format:
System PropertiesA property may have a corresponding System Property that has the same name except for the prefix as shown above. A System Property should be set prior to the creation of a processor and may be cleared afterwards.
jaxp.propertiesA system property can be specified in the
jaxp.propertiesfile to set the behavior for all invocations of the JDK. The format is
system-property-name=value. For example:
For details about the JAXP configuration file
jaxp.properties, refer to
Scope and OrderThe
XMLConstants.FEATURE_SECURE_PROCESSINGfeature (hereafter referred to as secure processing) is required for XML processors including DOM, SAX, Schema Validation, XSLT, and XPath. Any properties flagged as
"security: yes"(hereafter referred to as security properties) in table Features And Properties are enforced when secure processing is set to true. Such enforcement includes setting security features to true and limits to the defined values shown in the table. The property values will not be affected, however, when setting secure processing to false.
When the Java Security Manager is present, secure processing is set to true and can not be turned off. The security properties are therefore enforced.
Properties specified in the jaxp.properties file affect all invocations of the JDK, and will override their default values, or those that may have been set by secure processing.
System properties, when set, affect the invocation of the JDK and override the default settings or those that may have been set in jaxp.properties or by secure processing.
JAXP properties specified through JAXP factories or processors (e.g. SAXParser) take preference over system properties, the jaxp.properties file, as well as secure processing.
Processor SupportFeatures and properties may be supported by one or more processors. The following table lists the processors by IDs that can be used for reference.
Processors ID Name How to set the property DOM DOM Parser
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
SAX SAX Parser
SAXParserFactory spf = SAXParserFactory.newInstance();
SAXParser parser = spf.newSAXParser();
StAX StAX Parser
XMLInputFactory xif = XMLInputFactory.newInstance();
Validation XML Validation API
SchemaFactory schemaFactory = SchemaFactory.newInstance(schemaLanguage);
Transform XML Transform API
TransformerFactory factory = TransformerFactory.newInstance();
DOMLS DOM Load and Save
LSSerializer serializer = domImplementation.createLSSerializer();
Implementation Specific Features and PropertiesThis section lists features and properties supported by the JDK implementation.
Features and Properties Name  Description System Property  jaxp.properties  Value  Security  Supported Processor  Since  Type Value Default isStandalone indicates that the serializer should treat the output as a standalone document. The property can be used to ensure a newline is written after the XML declaration. Unlike the property
xml-declaration, this property does not have an effect on whether an XML declaration should be written out.
yes yes boolean true/false false No DOMLS 17
 The name of a property. The fully-qualified name, prefix + name, should be used when setting the property.
 A value "yes" indicates there is a corresponding System Property for the property, "no" otherwise.
 The value must be exactly as listed in this table, case-sensitive. The value type for the corresponding System Property is String. For boolean type, the system property is true only if it is "true" and false otherwise.
 A value "yes" indicates the property is a Security Property. Refer to the Scope and Order on how secure processing may affect the value of a Security Property.
 One or more processors that support the property. The values of the field are IDs described in table Processors.
 Indicates the initial release the property is introduced.
- Module Graph:
Exports Package Description javax.xmlDefines constants for XML processing. javax.xml.catalogProvides the classes for implementing XML Catalogs OASIS Standard V1.1, 7 October 2005. javax.xml.datatypeDefines XML/Java Type Mappings. javax.xml.namespaceDefines XML Namespace processing. javax.xml.parsersProvides the classes for processing XML documents with a SAX (Simple API for XML) parser or a DOM (Document Object Model) Document builder. javax.xml.streamDefines interfaces and classes for the Streaming API for XML (StAX). javax.xml.stream.eventsDefines event interfaces for the Streaming API for XML (StAX). javax.xml.stream.utilProvides utility classes for the Streaming API for XML (StAX). javax.xml.transformDefines the generic APIs for processing transformation instructions, and performing a transformation from source to result. javax.xml.transform.domProvides DOM specific transformation classes. javax.xml.transform.saxProvides SAX specific transformation classes. javax.xml.transform.staxProvides StAX specific transformation classes. javax.xml.transform.streamProvides stream and URI specific transformation classes. javax.xml.validationProvides an API for validation of XML documents. javax.xml.xpathProvides an object-model neutral API for the evaluation of XPath expressions and access to the evaluation environment. org.w3c.domProvides the interfaces for the Document Object Model (DOM). org.w3c.dom.bootstrapProvides a factory for obtaining instances of
org.w3c.dom.eventsProvides interfaces for DOM Level 2 Events. org.w3c.dom.lsProvides interfaces for DOM Level 3 Load and Save. org.w3c.dom.rangesProvides interfaces for DOM Level 2 Range. org.w3c.dom.traversalProvides interfaces for DOM Level 2 Traversal. org.w3c.dom.viewsProvides interfaces for DOM Level 2 Views. org.xml.saxProvides the core SAX APIs. org.xml.sax.extProvides interfaces to SAX2 facilities that conformant SAX drivers won't necessarily support. org.xml.sax.helpersProvides helper classes, including support for bootstrapping SAX-based applications.
Uses Type Description DatatypeFactoryFactory that creates new
Objects that map XML to/from Java
DocumentBuilderFactoryDefines a factory API that enables applications to obtain a parser that produces DOM object trees from XML documents. SAXParserFactoryDefines a factory API that enables applications to configure and obtain a SAX based parser to parse XML documents. SchemaFactoryFactory that creates
TransformerFactoryA TransformerFactory instance can be used to create
XMLEventFactoryThis interface defines a utility class for creating instances of XMLEvents XMLInputFactoryDefines an abstract implementation of a factory for getting streams. XMLOutputFactoryDefines an abstract implementation of a factory for getting XMLEventWriters and XMLStreamWriters. XMLReaderInterface for reading an XML document using callbacks. XPathFactoryAn
XPathFactoryinstance can be used to create