New in release 3.3.x
This release includes the following enchancements:
- Compliance of the Adapter for Web Services (the connector,
the WSDL ODA, and the SOAP data handler) with the WS-I Basic Profile
1.0 specifications released in August, 2003.
- Support for SOAP version 1.2; a new SOAP data handler meta-object
property (see MO_DataHandler_DefaultSOAPConfig) and a new WSDL ODA
property (see Table 47) allow
you to specify SOAP 1.2 or 1.1.
- The WSDL ODA allows you to reuse business object names based
on the same schema to reduce the total number of artifacts needed
for deployment. For further information, see Table 47.
- The WSDL ODA and SOAP data handler support all possible values
for maxOccurs on sequence, choice, and group. For further information,
see maxOccurs indicator on sequence, choice, group and all.
- If you have not specified a value for java.protocol.handler.pkgs,
the connector uses the default value during initialization. For
further information, see JSSE.
- The HTTP protocol listener supports requests with any Accept
header values; if necessary, the validation of the header can be
delegated to the collaboration.
- The minimum value has changed for the connector-specific property WorkerThreadCount.
For further information, see WorkerThreadCount.
- The adapter supports TextMessage and BytesMessage payload types
for inbound and outbound messages in SOAP/JMS listeners and handlers.
- In the case of synchronous event processing by SOAP/HTTP(S)
listeners, when a response is not populated by a collaboration,
the ContentType portion of the Content-Type HTTP header of the response
will be set to the ContentType of the request.
As of version 3.3.x, the adapter is not supported on Solaris
7, so references to that platform version have been deleted from
this guide.
