[CONF] Apache Camel > SOAP

[confluence]

SOAP Page edited by Christian Schneider SOAP (Available in Camel >= 2.3.0) SOAP is a Data Format which uses JAXB2 and JAX-WS to marshal and unmarshal SOAP payloads. It provides the basic features of Apache CXF without need for the CXF Stack. ElementNameStrategy 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 marshalling the object into a SOAP message. The second is to find an Exception class for a given soap fault name. Strategy Usage QNameStrategy Uses a fixed qName that is configured on instantiation. Exception lookup is not supported TypeNameStrategy 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 ServiceInterfaceStrategy 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 For example the following 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. SoapJaxbDataFormat soap = new SoapJaxbDataFormat("com.example.customerservice", new ServiceNameStrategy(CustomerService.class)); from("direct:start") .marshal(soap) .to("jms:myQueue"); See also As the SOAP dataformat inherits from the JAXB dataformat most settings apply here as well Examples Webservice client This snippet shows how to create a proxy for a service interface that sends requests to a direct endpoint and is also able to receive the response. Endpoint startEndpoint = context.getEndpoint("direct:customerServiceClient"); ClassLoader classLoader = Thread.currentThread().getContextClassLoader(); CustomerService proxy = ProxyHelper.createProxy(startEndpoint, classLoader, CustomerService.class); GetCustomersByNameResponse response = proxy.getCustomersByName(new GetCustomersByName()); This route supports marshalling the request and unmarshalling response or fault. SoapJaxbDataFormat soap = new SoapJaxbDataFormat("com.example.customerservice", new ServiceNameStrategy(CustomerService.class)); from("direct:customerServiceClient") .onException(Exception.class) .handled(true) .unmarshal(soap) .end() .marshal(soap) .to("http://myserver/customerservice") .unmarshal(soapDataFormat); Webservice Server 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 of course be defined in a spring context as a regular bean. SoapJaxbDataFormat soap = new SoapJaxbDataFormat("com.example.customerservice", new ServiceNameStrategy(CustomerService.class)); CustomerService serverBean = new CustomerServiceImpl(); from("jms://queue:customerServiceQueue") .onException(Exception.class) .handled(true) .marshal(soap) .end() .unmarshal(soap) .bean(serverBean) .marshal(soapDataFormat); Dependencies To use the SOAP dataformat in your camel routes you need to add the following dependency to your pom. <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-soap</artifactId> <version>1.6.0</version> </dependency> Change Notification Preferences View Online | View Change | Add Comment