Trading Networks 10.3 | Administering and Monitoring B2B Transactions | Service Development Help | Working with Web Services | About Provider Web Service Descriptors | Service Signature Requirements for Service First Provider Web Service Descriptors
 
Service Signature Requirements for Service First Provider Web Service Descriptors
 
Using XML Namespaces with Prefixes with Fields in Service Signatures
Handling Incomplete Service Signatures Using Wrapper Services
When you create a service first provider web service descriptor, you select one or more services to use as operations. The service signature becomes the input and output messages for the operations in the WSDL document. However, Integration Server allows constructs within service signatures that cannot be represented in certain web service style/use combinations.
When adding a service to or creating a service first provider web service descriptor, Integration Server verifies that the service signature can be represented in the style/use specified for the web service descriptor. If a service signature does not meet the style/use signature requirements, Integration Server will not add the service as an operation. Or, in the case of creating a service first provider WSD, Integration Server will not create the WSD.
Following, is a list of service signature restrictions and requirements for each style/use. Note that this list may not be exhaustive.
Signature Restrictions for Document/Literal
*body fields are not allowed at the top level
@attribute fields (fields starting with the “@” symbol) are not allowed at the top level
String table fields are not allowed
Signature Restrictions for RPC/Encoded
* body fields are not allowed
@attribute fields are not allowed (fields starting with the “@” symbol)
Top-level fields cannot be namespace qualified
Top-level field names cannot be in the format prefix:localName
Signature Restrictions for RPC/Literal
*body fields are not allowed at the top level
@attribute fields (fields starting with the “@” symbol) are not allowed at the top level
String table fields are not allowed
List fields (String List, Document List, Document Reference List, and Object List) are not allowed at the top level
Duplicate field names (identically named fields) are not allowed at the top level
Top-level fields cannot be namespace qualified
Top-level field names cannot be in the format prefix:localName