Table 1 illustrates the specification of multiple InputMessage elements and the resulting composite XML Schema.
| ServiceSpecification.xml | Composite XML Schema |
|---|---|
<InputMessage nativeTypeName="REQ-HEADER" xmlEleName="RequestHeader" lowerBound="1" upperBound="1"> <ItemSelectionArray ../> <InputMessage nativeTypeName="REQ-BODY" xmlEleName="REQ-BODY" lowerBound="1"upperBound="10"> <ItemSelectionArray ../> </InputMessage > <InputMessage nativeTypeName="REQ-SUM" xmlEleName="RequestSummary" lowerBound="1" upperBound="1"> <ItemSelectionArray ../> </InputMessage > <XsdSpecIn xsdEleName="ServiceRequest" ../> |
<complexType name="REQ_HEADER">
<sequence ../>
</complexType>
<complexType name="REQ_BODY">
<sequence ../>
</complexType>
<complexType name="REQ_SUM">
<sequence ../>
</complexType>
<complexType
name="EIS_COMPOSITE_MESSAGE">
<sequence>
<element name="RequestHeader"
type="p:REQ_HEADER"
minOccurs="1" maxOccurs="1" />
<element name="RequestBody"
type="p:REQ_BODY"
minOccurs="1" maxOccurs="10" />
<element name="RequestSummary"
type="p:REQ_SUMMARY"
minOccurs="1" maxOccurs="1" />
</sequence>
</complexType>
<element name="ServiceRequest"
type="p:EIS_COMPOSITE_MESSAGE" >
</element>
|
This section describes the Batch Processor limitations and restrictions on generation of composite XML Schemas from collections of language structures.
Multiple InputMessage and OutputMessages are not allowed if mapping files are specified instead of language source files (that is, meet-in-middle is not supported since this function deals with generation of XSDs).
Multiple InputOutputMessage elements are not supported. Use multiple InputMessage and OutputMessage elements instead.
A language structure may not be specified more than once in a series of InputMessage or OutputMessage elements. This means that an XML Schema complex type derived from a language structure cannot reappear later in an XML message with identical or different field level inclusions and/or exclusions.
All language structures specified on InputMessage and OutputMessage elements (nativeTypeName) must have unique names regardless of the language source file (importFile) they reside in.
All XML element names specified on InputMessage and OutputMessage elements (xmlEleName) must be unique with respective to the other InputMessage or OutputMessage elements. It is not an error to have a XML element name that appears both in a series of InputMessage and OutputMessage elements.
For example, an OCCURS DEPENDING ON (ODO) subject cannot refer to an ODO object in another structure.