Rules and Guidelines for Creating Web Service Definitions
Rules and Guidelines for Creating Web Service Definitions
Use the following rules and guidelines when you import or create web service source and target definitions:
Use a WSDL for elements with complex relationships.
To create a web service source or target definitions with a complex element relationship, first create a WSDL to define the element hierarchy and then import the source or target definition from the WSDL. Use a WSDL to create a web service source or target definition that contain multiple occurrences of elements or that contain elements of complex type.
Use a WSDL with a global element.
When you import a definition from a WSDL that has no global element, the Designer cannot create a root view in the web service definition. The Designer displays a message that there is no global element.
Use a WSDL to create targets with fault views.
If you want the target definition to have fault views for specific data error, use a WSDL to create the web service target definition.
The input and output message in the WSDL must have the same encoding style.
If you import web service source and target definition from a WSDL, the encoding style for the input and output messages must be the same. If the input message uses the RPC/SOAP Encoded style, the output message must also use the RPC/SOAP Encoded style. If the input message uses the Document/Literal style, the output message must also use the Document/Literal style.