Differences Between XML Document Types and IS Document Types
In addition to improved namespace handling and support for XML schema constructs such as nested model groups, repeating model groups, and any attribute, XML document types and IS document types have the following differences:
XML document types can be created from XML schema definitions only.
Integration Server uses the names in an XML Schema definition to name the generated IS assets, including the XML document types. This is unlike IS document types where you can specify the name of the first IS document type generated from an XML schema definition but
Integration Server creates the names of any subsequent IS document types.
XML document types do not use prefixes from the XML schema definition in the names of XML document types. XML fields, or fields withing XML document types. Instead IS uses the following format for XML document type names, XML field names, and names of fields within XML document types:
NCName#
NamespaceURI .
Integration Server document types use prefixes from the XML schema definition in field (variable) names.
In XML document types, attribute names do not include the @ symbol to indicate that it is an attribute.
XML document types do not contain
*body,
*doctype, or
*any fields.
XML document types provide improved handling of identically named fields at the same level. In XML document types,
Integration Server maintains a particle ID for each field. To view the particle ID, hover the cursor over the name of the field.
Designer displays properties for the field including the following for the name: {
ID}
NCName#
NamespaceURI where
ID is a number representing the occurrence of the field in the document type or the pipeline. For example, {2}myLocalName#myNamespaceName indicates the second occurrence of a field named myLocalName#myNamespaceName.
In IS document types, all occurrences of identically named fields at the same level are collected into a single array. This approach may not preserve order during runtime.
Note: Integration Server creates arrays for XML document types when an individual element has a maxOccurs greater than 1. If there are two fields named myLocalName#myNamespaceName and each has a maxOccurs greater than 1, Integration Server creates {1}myLocalName#myNamespaceName as an array and {2}myLocalName#myNamespaceName as an array.
The contents of XML document types and XML fields cannot be edited.
A Document Reference or Document Reference List variable contained in an IS document type or in a service signature can reference an XML document type that corresponds to a complex type definition or a root XML document type only.