Available as of Camel 2.3
SOAP is a Data Format which uses JAXB2 and JAX-WS annotations to marshal and unmarshal SOAP payloads. It provides the basic features of Apache CXF without need for the CXF Stack.
Supported SOAP versions
SOAP 1.1 is supported by default. SOAP 1.2 is supported from Camel 2.11 onwards.
Namespace prefix mapping
An element name strategy is used for two purposes. The first is to find a xml element name for a given object and soap action when marshaling the object into a SOAP message. The second is to find an Exception class for a given soap fault name.
Uses a fixed qName that is configured on instantiation. Exception lookup is not supported
Uses the name and namespace from the @XMLType annotation of the given type. If no namespace is set then package-info is used. Exception lookup is not supported
Uses information from a webservice interface to determine the type name and to find the exception class for a SOAP fault
If you have generated the web service stub code with cxf-codegen or a similar tool then you probably will want to use the ServiceInterfaceStrategy. In the case you have no annotated service interface you should use QNameStrategy or TypeNameStrategy.
Using the Java DSL
The following example uses a named DataFormat of soap which is configured with the package com.example.customerservice to initialize the JAXBContext. The second parameter is the ElementNameStrategy. The route is able to marshal normal objects as well as exceptions. (Note the below just sends a SOAP Envelope to a queue. A web service provider would actually need to be listening to the queue for a SOAP call to actually occur, in which case it would be a one way SOAP request. If you need request reply then you should look at the next example.)
As the SOAP dataformat inherits from the JAXB dataformat most settings apply here as well
Using SOAP 1.2
Available as of Camel 2.11
When using XML DSL there is a version attribute you can set on the <soapjaxb> element.
And in the Camel route
Available as of Camel 2.8.1
Multi-part SOAP messages are supported by the ServiceInterfaceStrategy. The ServiceInterfaceStrategy must be initialized with a service interface definition that is annotated in accordance with JAX-WS 2.2 and meets the requirements of the Document Bare style. The target method must meet the following criteria, as per the JAX-WS specification: 1) it must have at most one
in/out non-header parameter, 2) if it has a return type other than
void it must have no
out non-header parameters, 3) if it it has a return type of
void it must have at most one
out non-header parameter.
The ServiceInterfaceStrategy should be initialized with a boolean parameter that indicates whether the mapping strategy applies to the request parameters or response parameters.
The payload parameters for a multi-part request are initiazlied using a
BeanInvocation object that reflects the signature of the target operation. The camel-soap DataFormat maps the content in the
BeanInvocation to fields in the SOAP header and body in accordance with the JAX-WS mapping when the
marshal() processor is invoked.
A multi-part soap response may include an element in the soap body and will have one or more elements in the soap header. The camel-soap DataFormat will unmarshall the element in the soap body (if it exists) and place it onto the body of the out message in the exchange. Header elements will not be marshaled into their JAXB mapped object types. Instead, these elements are placed into the camel out message header
org.apache.camel.dataformat.soap.UNMARSHALLED_HEADER_LIST. The elements will appear either as element instance values, or as JAXBElement values, depending upon the setting for the
ignoreJAXBElement property. This property is inherited from camel-jaxb.
You can also have the camel-soap DataFormate ignore header content all-together by setting the
ignoreUnmarshalledHeaders value to
Holder Object mapping
JAX-WS specifies the use of a type-parameterized
javax.xml.ws.Holder object for
Out parameters. A
Holder object may be used when building the
BeanInvocation, or you may use an instance of the parameterized-type directly. The camel-soap DataFormat marshals Holder values in accordance with the JAXB mapping for the class of the
Holder's value. No mapping is provided for
Holder objects in an unmarshalled response.
The following route supports marshalling the request and unmarshalling a response or fault.
The below snippet creates a proxy for the service interface and makes a SOAP call to the above route.
Using the following route sets up a webservice server that listens on jms queue customerServiceQueue and processes requests using the class CustomerServiceImpl. The customerServiceImpl of course should implement the interface CustomerService. Instead of directly instantiating the server class it could be defined in a spring context as a regular bean.
To use the SOAP dataformat in your camel routes you need to add the following dependency to your pom.