Table of Contents

Search

  1. Preface
  2. Web Services
  3. SOAP Web Services
  4. WSDL Data Object
  5. Schema Object
  6. How to Create a SOAP Web Service
  7. Operation Mappings
  8. Parsing Web Service SOAP Messages
  9. Generating Web Service SOAP Messages
  10. Web Service Consumer Transformation
  11. REST Web Services
  12. How to Create a REST Web Service
  13. REST Web Service Consumer Transformation
  14. REST and SOAP Web Service Administration
  15. Datatype Compatibility

Web Services Guide

Web Services Guide

Types and Elements

Types and Elements

When you create a web service from a WSDL data object, the WSDL data object defines the elements and element types for each operation. When you manually create an web service, you can define the elements or use types from schema objects to define the elements.
If operation components include anyType elements, any elements, anyAttribute attributes, derived type elements, or substitution groups, you must choose one or more types, elements, or attributes when you configure the operation mapping. For example, if the operation input includes an anyType element, choose the one or more types when you configure the Input transformation.
When you use a schema object to define element types, the Developer tool includes the schema object in the WSDL of the web service. When you delete the schema object or delete the link to the schema object in the web service WSDL, the Developer tool changes the element type of elements that were defined by the schema object to xs:string. You can update the element type to another type.
When you manually create a web service, the web service requires a unique generated prefix value for each namespace that it uses to define operation components. For example, if a web service uses schema object schemaA and schema object schemaB to define types, schemaA and schema B cannot have the same generated prefix value for any namespace.