ad21074_.htm |
Last updated Friday, 21 July 2017The XMLNSC parser is a flexible, general-purpose XML parser that offers high performance XML parsing and optional XML Schema validation.
The XMLNSC parser has a range of options that make it suitable for most XML processing requirements. Some of these options are only available in the XMLNSC parser.
Although the XMLNSC parser is capable of parsing XML documents without an XML Schema, extra features of the parser become available when it operates in model-driven mode. In model-driven mode, the XMLNSC parser is guided by an XML Schema, which describes the shape of the message tree (the logical model).
XML Schemas are created automatically from the content of a message set when the message set is added to a broker archive (BAR) file. The XML Schemas are deployed to the broker and used by the XMLNSC parser to validate your XML messages. Validation is fully compliant with the XML Schema 1.0 specification.
For guidance on when to use the XMLNSC domain and parser, see Which XML parser should you use?.
If you want the XMLNSC domain to parse a message, select Message Domain as XMLNSC on the appropriate node in the message flow. Additionally, if you want the XMLNSC parser to validate your messages, perform the additional steps that are described in XMLNSC validation.
| Feature | Present | Description |
|---|---|---|
| Namespace support | Yes | Namespace information is used if it is present. No user configuration is required. See XML parsers namespace support. |
| On-demand parsing | Yes | See Parsing on demand. |
| Compact message tree | Yes | Less memory is used when building a message tree from an XML document. See Manipulating messages in the XMLNSC domain. |
| Opaque parsing | Yes | One or more elements can be parsed opaquely. See XMLNSC opaque parsing. |
| Ultra high performance | Yes | The architecture of the XMLNSC parser means that the parser's use of processor resources is significantly less than that of the other XML parsers. |
| Validation | Yes | See the table that follows this one. |
| Inline DTD support | Partial | Inline DTDs are processed but discarded. See XMLNSC DTD support. |
| XML Data Model compliance | Partial | The compact nature of the message tree means that some XPath queries are not supported. |
The following features are only available when message validation is enabled. See XMLNSC validation.
| Feature | Description |
|---|---|
| Message validation | Validates compliance with the XML Schema 1.0 specification. |
| xsi:nil support | Sets the value of an element to NULL if it has xsi:nil=”true” and the XML Schema indicates that it is nillable. |
| Default value support | Sets the value of an empty element, or missing attribute, to its default value, according to XML Schema rules. |
| Use correct simple types | Allows the use of the simple types that are defined in the XML Schema when building the message tree. |
| Base64 support | Converts base64 data to BLOB when parsing. Converts BLOB to base64 when writing. |
If you specify the SOAP domain as the owner of a SOAP Web Services message, the SOAP parser invokes the XMLNSC parser in model-driven mode to parse the XML content of the SOAP message.
If you specify the DataObject domain as the owner of a WebSphere® Adapter message, and the message is written to a destination other than a WebSphere Adapter, the DataObject parser invokes the XMLNSC parser to write the message as XML.
Last updated Friday, 21 July 2017