NonStop SOAP 4.1 User's Manual

</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
For this conversion, NonStop SOAP 4 server uses DDLMapping.xml file to convert the request
data to character buffer and response character buffer to XML. The server uses data definition
structures stored in DDLMapping.xml file and their qualified names as a key for mapping.
The considerations for using comment names in DDL Definition are:
1. More than one alternate name for the same field cannot be used in the DDL definition file.
2. You must use the DDL field name as a reference along with SOAP DDL comment.
Support for Multiple DDL Definitions
You can use multiple DDL definitions in a single SOAP request or response. You can implement
this feature by specifying multiple <DDLDefinitionName> elements in a <RequestInfo> or
<ResponseInfo> element in the SDL file.
The following example illustrates the use of separate DDL definitions A1 and A2:
DDL Definition:
DEFINITION A1
02 A11 PIC X(10000)
02 A12 PIC X(20000)
END
DEFINITION A2
02 A21 PIC X(10000)
02 A22 PIC X(20000)
END
To specify that the Inter Process Communication (IPC) contains both definitions, A1 and A2, one
after another, specify each of them by using <DDLDefinitionName> elements in the
<RequestInfo> element:
<RequestInfo>
<DDLDefinitionName>A1</DDLDefinitionName>
<DDLDefinitionName>A2</DDLDefinitionName>
</RequestInfo>
The generated SOAP message contains the following XML structure:
<Req>
<A1>
<A11>temp</A11>
<A12>temp</A12>
</A1>
<A2>
<A21>temp</A21>
<A22>temp</A22>
</A2>
</Req>
234 NonStop SOAP 4 Features