[CONF] Apache Camel > spring ws example

[confluence]

spring ws example Page edited by Richard Kettelerij Comment: CAMEL-3472 add example of Spring Web Services component Changes (4) ... {code} This The {{endpointMapping}} bean is a Spring-WS [endpoint mapping|http://static.springsource.org/spring-ws/sites/1.5/reference/html/server.html#server-endpoint-mapping] that maps incoming messages to the appropriate Camel routes. You'll only need to define a _single_ {{CamelEndpointMapping}}, regardless of the number of Camel routes implementing using Spring-WS endpoints. The above endpoint mapping {{endpointMapping}} bean is automatically picked up by the {{MessageDispatcherServlet}} declared in {{web.xml}}: {code:XML} <servlet> ... <servlet-class>org.springframework.ws.transport.http.MessageDispatcherServlet</servlet-class> </servlet> {code} Since the servlet is named {{spring-ws}} it will look for a file named {{/WEB-INF/spring-ws-servlet.xml}}. {code} Full Content Spring Web Services Example Available as of Camel 2.6 This example shows how to expose a SOAP-based web service using Camel and Spring Web Services. Running the example The example is included in the distribution at examples/camel-example-spring-ws. To start the example use Maven: mvn clean install jetty:run This will expose a web service on http://localhost:8080/increment. With the help of a tool such as Soap-UI it's easy to sent messages to this endpoint. There's a ready to use SOAP-UI project available at examples/camel-example-spring-ws/client. Code walk through The Camel route exposing the above web service is defined as: JaxbDataFormat jaxb = new JaxbDataFormat(false); jaxb.setContextPath("org.apache.camel.example.server.model"); from("spring-ws:rootqname:{http://camel.apache.org/example/increment}incrementRequest?endpointMapping=#endpointMapping") .unmarshal(jaxb) .process(new IncrementProcessor()) .marshal(jaxb); Taking a closer look at the URI reveals that this route consumes messages with a certain rootqname. In this case it listens for messages with root element incrementRequest defined in the http://camel.apache.org/example/increment namespace. These XML messages are unmarshalled to objects using Camel's Data Format support (JAXB in this case). After processing the resulting object is marshalled back to XML and returned to the client as a response. Further notice that the URI contains a reference to an endpointMapping in the Registry. Since we're using Spring the registry is a Spring ApplicationContext defined in spring-ws-servlet.xml. This file contains the following bean: <bean id="endpointMapping" class="org.apache.camel.component.spring.ws.bean.CamelEndpointMapping"> <property name="interceptors"> <list> <ref local="validatingInterceptor" /> <ref local="loggingInterceptor" /> </list> </property> </bean> The endpointMapping bean is a Spring-WS endpoint mapping that maps incoming messages to appropriate Camel routes. You'll only need to define a single CamelEndpointMapping, regardless of the number of Camel routes using Spring-WS endpoints. The above endpointMapping bean is automatically picked up by the MessageDispatcherServlet declared in web.xml: <servlet> <servlet-name>spring-ws</servlet-name> <servlet-class>org.springframework.ws.transport.http.MessageDispatcherServlet</servlet-class> </servlet> Since the servlet is named {{spring-ws}} it will look for a file named {{/WEB-INF/spring-ws-servlet.xml}}. Change Notification Preferences View Online | View Changes | Add Comment