Most Web Services have input and output parameters that are of basic data types, such as String, Integer, or Decimal. Some services, however, use complex data types to represent entities such as employee information, product order, and so on.
If the Web Service you are going to use does not contain complex types, you may skip this section and continue to Definingthe dataslot mapping.
When a complex object is either passed as an input parameter to a Web Service, or is returned from the service as an output, the mapping between the CHARACTER type and the corresponding Java class must be defined in the Types and Mapping tab.
Note: Regardless of the public Web Service you use, the following section describes how to use complex data types in the Web Service Adapter.
Figure 22. Web Service Adapter Configurator - Types and Mapping tab
The Web Service Adapter Configurator makes its best effort to simplify your work, and it automatically defines the type mapping for every complex type it encounters. The automatically generated definition assumes the following:
Java class name is the same as the XML type localpart name
Java class is a JavaBean type object, whose fields can be manipulated with a set of set/get methods
Java class name is the same as the XML type localpart name