Show Table of Contents
13.9.8. SOAP Operation Parameters
The SOAP operation parameters are supplied in either of these two ways:
- as a map instance set on the default body location
(Message.getBody().add(Map)) - as a map instance set on in a named body location
(Message.getBody().add(String, Map)), where the name of that body location is specified as the value of the "paramsLocation" action property.
The parameter map itself can also be populated in one of two ways:
- With a set of Objects of any type. In this case a Smooks config has to be specified in action attribute SmooksRequestMapper and Smooks is used to make the Java-to-Java conversion
- With a set of String-based key-value pairs(<String, Object>), where the key is the name of the SOAP parameter as specified in wsdls (or in generated class) to be populated with the key's value. SOAP Response Message Consumption
The SOAP response object instance can be is attached to the message in one of the following ways:
- On the default body location (Message.getBody().add(Map))
- On in a named body location (Message.getBody().add(String, Map)), where the name of that body location is specified as the value of the "responseLocation" action property.
The response object instance can also be populated (from the SOAP response) in either one of two ways:
- With a set of objects of any type. In this case, a Smooks config have to be specified in action attribute SmooksResponseMapper and Smooks is used to make the Java-to-Java conversion
- With a set of String based key-value pairs(<String, Object>), where the key is the name of the SOAP answer as specified in wsdls (or in generated class) to be populated with the key's value. JAX-WS Handler for the SOAP Request/Response
For examples of using the SOAPClient please refer to the following quick starts:
- webservice_consumer_wise, shows basic usage.
- webservice_consumer_wise2, shows how to use'SmooksRequestMapper' and 'SmooksResponseMapper'.
- webservice_consumer_wise3, shows how to use 'smooks-handler-config'.
- webservice_consomer_wise4, shows usage of 'custom-handlers'.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.