NonStop SOAP 4.1 User's Manual

WSDL2PWY Limitations
The NonStop SOAP 4 WSDL2PWY tool is used to generate the Pathway service artifacts for
contract-first development approach. This tool has some deviations from the WSDL specification
and some limitations, which are discussed in this section.
Table 26 lists the XML schema definitions, which deviate from WSDL specification and WSDL2PWY
tool behavior for these XML schema definitions.
Table 15 XML schema definitions, which deviate from WSDL specification
WSDL2PWY behaviorWSDL specificationXML schema definitions
Tool parses the WSDL and generates
element with type axiom_node_t *,
which results in a compilation error
Elements cannot have
simpleContent or
complexContent
Elements having complexContent
and simpleContent
Generates either pointer (for unbounded
data elements) or an array
maxOccurs must be 1 and
minOccurs must be either 0 or 1 for
elements within <all>
maxOccurs != 1 or minOccurs
>1 for elements within <all>
Ignores such attributes without returning
any error
Attributes can have only simpleTypeAttributes having complexContent,
simpleContent or complexType
Generates variables for attributesAttributes along with
complexContent or
simpleContent are not allowed
Attributes along with
complexContent
orsimpleContent
The following XML schema definitions are part of the WSDL specification but are not supported
by WSDL2PWY tool:
• <any> element type. For example,
<xsd:any minoccurs=”0” maxoccurs=”unbounded”/>
• Nested <group> or <choice> or <sequence> elements. For example,
<xsd:element name="ele1" type="xsd:string”/>
<xsd:element name="ele2" type="xsd:int”/>
<xsd:group name="group1”>
<xsd:choice>
<xsd:element name="ele3" type="xsd:string”/>
<xsd:element name="ele4" type="xsd:string”/>
</xsd:choice>
</xs:group>
</xsd:sequence>
• Substitution group. For example,
<xs:element name="name" type="xs:string”/>
<xs:element name="navn" substitutionGroup="name”/>
• <extension> element. For example,
<xsd:extension base="xsd:decimal”>
<xsd:attribute name="my_attri" type="tns1:internationalPrice1" use="optional”/>
<xsd:attribute name="currency" type="xsd:int" use="optional”/>
</xsd:extension>
The following parameters are not supported by contract-first development approach, but are
supported by service-first development approach. In contract-first development approach, these
parameters are ignored if they are present in services.xml file.
• stringTermination = NullTerminated/NonNULL
• responseType = strict/lenient
210 NonStop SOAP Tools