Modified: websites/production/camel/content/cdi.html
==============================================================================
--- websites/production/camel/content/cdi.html (original)
+++ websites/production/camel/content/cdi.html Wed Mar 9 15:22:14 2016
@@ -86,11 +86,11 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="CDI-CamelCDI">Camel
CDI</h2><p>The Camel CDI component provides auto-configuration for Apache Camel
using CDI as dependency injection framework based
on <em>convention-over-configuration</em>. It auto-detects Camel routes
available in the application and provides beans for common Camel primitives
like <code>Endpoint</code>, <code>ProducerTemplate</code>
or <code>TypeConverter</code>. It implements standard <a shape="rect"
href="bean-integration.html">Camel bean integration</a> so that Camel
annotations like <code>@Consume</code>, <code>@Produce</code>
and <span style="color: rgb(0,0,0);"><code>@PropertyInject</code> can be
used seamlessly in CDI beans</span>. Besides, it bridges Camel events (e.g.
<code>RouteAddedEvent</code>,
<code>CamelContextStartedEvent</code>, <code>ExchangeCompletedEvent</code>,
...) as CDI events and provides a CDI events endpoint that can be used to
consume / produce CDI events
from / to Camel routes.</p><div class="confluence-information-macro
confluence-information-macro-information"><span class="aui-icon aui-icon-small
aui-iconfont-info confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>While the Camel CDI component is
available as of <strong>Camel 2.10</strong>, it's been rewritten in
<strong>Camel 2.17</strong> to better fit into the CDI programming model. Hence
some of the features like the Camel events to CDI events bridge and the CDI
events endpoint only apply starting Camel 2.17.</p></div></div><h3
id="CDI-Auto-configuredCamelcontext">Auto-configured Camel context</h3><p>Camel
CDI automatically deploys and configures a <code>CamelContext</code> bean.
That <code>CamelContext</code> bean is automatically instantiated, configured
and started (resp. stopped) when the CDI container initialises (resp. shuts
down). It can be injected in the application, e.g.:</p><div class="code panel
pdl" style="border-width
: 1px;"><div class="codeContent panelContent pdl">
+<div class="wiki-content maincontent"><h2 id="CDI-CamelCDI">Camel
CDI</h2><p>The Camel CDI component provides auto-configuration for Apache Camel
using CDI as dependency injection framework based
on <em>convention-over-configuration</em>. It auto-detects Camel routes
available in the application and provides beans for common Camel primitives
like <code>Endpoint</code>, <code>ProducerTemplate</code>
or <code>TypeConverter</code>. It implements standard <a shape="rect"
href="bean-integration.html">Camel bean integration</a> so that Camel
annotations like <code>@Consume</code>, <code>@Produce</code>
and <span style="color: rgb(0,0,0);"><code>@PropertyInject</code> can be
used seamlessly in CDI beans</span>. Besides, it bridges Camel events (e.g.
<code>RouteAddedEvent</code>,
<code>CamelContextStartedEvent</code>, <code>ExchangeCompletedEvent</code>,
...) as CDI events and provides a CDI events endpoint that can be used to
consume / produce CDI events
from / to Camel routes.</p><div class="confluence-information-macro
confluence-information-macro-information"><span class="aui-icon aui-icon-small
aui-iconfont-info confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>While the Camel CDI component is
available as of <strong>Camel 2.10</strong>, it's been rewritten in
<strong>Camel 2.17</strong> to better fit into the CDI programming model. Hence
some of the features like the Camel events to CDI events bridge and the CDI
events endpoint only apply starting Camel 2.17.</p></div></div><div
class="confluence-information-macro
confluence-information-macro-information"><span class="aui-icon aui-icon-small
aui-iconfont-info confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>More details on how to test Camel
CDI applications are available in <a shape="rect" href="cdi-testing.html">Camel
CDI testing</a>.</p></div></div><h3 id="CDI-Auto-configuredCamelcontext">Aut
o-configured Camel context</h3><p>Camel CDI automatically deploys and
configures a <code>CamelContext</code> bean. That
<code>CamelContext</code> bean is automatically instantiated, configured and
started (resp. stopped) when the CDI container initialises (resp. shuts down).
It can be injected in the application, e.g.:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[@Inject
CamelContext context;]]></script>
</div></div><p>That default <code>CamelContext</code> bean is qualified with
the built-in <code>@Default</code> qualifier, is
scoped <code>@ApplicationScoped</code> and is of type
<code>DefaultCamelContext</code>.</p><p>Note that this bean can be customised
programmatically and other Camel context beans can be deployed in the
application as well.</p><h3 id="CDI-Auto-detectingCamelroutes">Auto-detecting
Camel routes</h3><p>Camel CDI automatically collects all
the <code>RoutesBuilder</code> beans in the application, instantiates and
add them to the <code>CamelContext</code> bean instance when the CDI container
initialises. For example, adding a Camel route is as simple as declaring a
class, e.g.:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[class MyRouteBean extends RoutesBuilder {
+<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[class MyRouteBean extends RouteBuilder {
Â
@Override
public void configure() {
@@ -113,7 +113,7 @@ Endpoint endpoint;
TypeConverter converter;]]></script>
</div></div><h3 id="CDI-Camelcontextconfiguration">Camel context
configuration</h3><p>If you just want to change the name of the default
<code>CamelContext</code> bean, you can used the <code>@ContextName</code>
qualifier provided by Camel CDI, e.g.:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[@ContextName("camel-context")
-class MyRouteBean extends RoutesBuilder {
+class MyRouteBean extends RouteBuilder {
Â
@Override
public void configure() {
@@ -357,7 +357,7 @@ PlatformTransactionManager createTransac
void onContextStarted(@Observes @Manual CamelContextStartedEvent event) {
// Called after the the Camel context qualified with '@Manual' has
started
}]]></script>
-</div></div><p>Similarly, the <code>@Default</code> qualifier can be
used to observe Camel events for the <em>default</em> Camel context
if multiples contexts exist, e.g.:</p><div class="highlight
highlight-source-java"><p> </p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Similarly, the <code>@Default</code> qualifier can be
used to observe Camel events for the <em>default</em> Camel context
if multiples contexts exist, e.g.:</p><div class="highlight
highlight-source-java"><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[void onExchangeCompleted(@Observes @Default
ExchangeCompletedEvent event) {
// Called after the exchange 'event.getExchange()' processing has
completed
}]]></script>
@@ -473,7 +473,7 @@ for (CamelContext context : contexts)
context.setUseBreadcrumb(true);]]></script>
</div></div></div></div></div><h3 id="CDI-MavenArchetype">Maven
Archetype</h3><p>Among the available <a shape="rect"
href="camel-maven-archetypes.html">Camel Maven archetypes</a>, you can use the
provided <code>camel-archetype-cdi</code> to generate a Camel CDI
Maven project, e.g.:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
<script class="brush: bash; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[mvn archetype:generate
-DarchetypeGroupId=org.apache.camel.archetypes
-DarchetypeArtifactId=camel-archetype-cdi]]></script>
-</div></div><h3 id="CDI-Supportedcontainers">Supported containers</h3><p>The
Camel CDI component is compatible with any CDI 1.0, CDI 1.1 and CDI 1.2
compliant runtime. It's been successfully tested against the following
runtimes:</p><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh">Container</th><th colspan="1" rowspan="1"
class="confluenceTh">Version</th><th colspan="1" rowspan="1"
class="confluenceTh">Runtime</th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd">Weld SE</td><td colspan="1" rowspan="1"
class="confluenceTd"><code>1.1.28.Final</code></td><td colspan="1" rowspan="1"
class="confluenceTd">CDI 1.0 / Java SE 7</td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd">OpenWebBeans</td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>1.2.7</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd">CDI 1.0 / Java SE 7</td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd">Weld S
E</td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>2.3.3.Final</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd">CDI 1.2 / Java SE 7</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">OpenWebBeans</td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>1.6.3</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd">CDI 1.2 / Java SE 7</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">WildFly</td><td colspan="1"
rowspan="1" class="confluenceTd"><code>8.2.1.Final</code></td><td colspan="1"
rowspan="1" class="confluenceTd">CDI 1.2 / Java EE 7</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">WildFly</td><td colspan="1"
rowspan="1" class="confluenceTd"><code>9.0.1.Final</code></td><td colspan="1"
rowspan="1" class="confluenceTd">CDI 1.2 / Java EE 7</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">Karaf</td><td colspan="1"
rowspan="1" class="confluenceTd"><code>2.4.4</code></td><td colspan="1" rowspan=
"1" class="confluenceTd">CDI 1.2 / <span>OSGi 4 / PAX
CDI</span></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd">Karaf</td><td colspan="1" rowspan="1"
class="confluenceTd"><code>3.0.5</code></td><td colspan="1" rowspan="1"
class="confluenceTd">CDI 1.2 / <span>OSGi 5 / PAX CDI</span></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">Karaf</td><td colspan="1"
rowspan="1" class="confluenceTd"><code>4.0.4</code></td><td colspan="1"
rowspan="1" class="confluenceTd">CDI 1.2 / <span>OSGi 6 / PAX
CDI</span></td></tr></tbody></table></div><h3
id="CDI-Examples">Examples</h3><p>The following examples are available in the
<code>examples</code> directory of the Camel
project:</p><ul><li><code><code>camel-example-cdi</code></code> - illustrates
how to work with Camel using CDI to configure components, endpoints and
beans,</li><li><code>camel-example-cdi-metrics</code> - illustrates the
integration between Camel, Dropwizard Metrics and
CDI,</li><li><code>camel-example-cdi
-properties</code> - illustrates the integration between Camel,
DeltaSpike and CDI for configuration
properties,</li><li><code>camel-example-cdi-osgi</code> - a CDI
application using the SJMS component that can be executed inside an OSGi
container using PAX CDI,</li><li><code>camel-example-cdi-rest-servlet</code>
- illustrates the Camel REST DSL being used in a Web application that uses
CDI as dependency injection
framework,</li><li><code>camel-example-widget-gadget-cdi</code> - the Widget
and Gadget use-case from the EIP book implemented in Java with CDI dependency
Injection,</li><li><span><span><code>camel-example-swagger-cdi</code> -
a</span>n example using REST DSL and Swagger Java with CDI.</span></li></ul><h3
id="CDI-SeeAlso">See Also</h3><ul><li><a shape="rect" class="external-link"
href="http://www.cdi-spec.org"; rel="nofollow">CDI Web site</a></li><li><a
shape="rect" class="external-link" href="http://www.cdi-spec.org/ecosystem/";
rel="nofollow">CDI ecosystem</
a></li><li><a shape="rect" class="external-link"
href="https://github.com/astefanutti/further-cdi"; rel="nofollow">Going further
with CDI</a> (See Camel CDI section)</li></ul></div>
+</div></div><h3 id="CDI-Supportedcontainers">Supported containers</h3><p>The
Camel CDI component is compatible with any CDI 1.0, CDI 1.1 and CDI 1.2
compliant runtime. It's been successfully tested against the following
runtimes:</p><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh">Container</th><th colspan="1" rowspan="1"
class="confluenceTh">Version</th><th colspan="1" rowspan="1"
class="confluenceTh">Runtime</th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd">Weld SE</td><td colspan="1" rowspan="1"
class="confluenceTd"><code>1.1.28.Final</code></td><td colspan="1" rowspan="1"
class="confluenceTd">CDI 1.0 / Java SE 7</td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd">OpenWebBeans</td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>1.2.7</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd">CDI 1.0 / Java SE 7</td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd">Weld S
E</td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>2.3.3.Final</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd">CDI 1.2 / Java SE 7</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">OpenWebBeans</td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>1.6.3</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd">CDI 1.2 / Java SE 7</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">WildFly</td><td colspan="1"
rowspan="1" class="confluenceTd"><code>8.2.1.Final</code></td><td colspan="1"
rowspan="1" class="confluenceTd">CDI 1.2 / Java EE 7</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">WildFly</td><td colspan="1"
rowspan="1" class="confluenceTd"><code>9.0.1.Final</code></td><td colspan="1"
rowspan="1" class="confluenceTd">CDI 1.2 / Java EE 7</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">Karaf</td><td colspan="1"
rowspan="1" class="confluenceTd"><code>2.4.4</code></td><td colspan="1" rowspan=
"1" class="confluenceTd">CDI 1.2 / <span>OSGi 4 / PAX
CDI</span></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd">Karaf</td><td colspan="1" rowspan="1"
class="confluenceTd"><code>3.0.5</code></td><td colspan="1" rowspan="1"
class="confluenceTd">CDI 1.2 / <span>OSGi 5 / PAX CDI</span></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">Karaf</td><td colspan="1"
rowspan="1" class="confluenceTd"><code>4.0.4</code></td><td colspan="1"
rowspan="1" class="confluenceTd">CDI 1.2 / <span>OSGi 6 / PAX
CDI</span></td></tr></tbody></table></div><h3
id="CDI-Examples">Examples</h3><p>The following examples are available in the
<code>examples</code> directory of the Camel
project:</p><ul><li><code><code>camel-example-cdi</code></code> - illustrates
how to work with Camel using CDI to configure components, endpoints and
beans,</li><li><code>camel-example-cdi-metrics</code> - illustrates the
integration between Camel, Dropwizard Metrics and
CDI,</li><li><code>camel-example-cdi
-properties</code> - illustrates the integration between Camel,
DeltaSpike and CDI for configuration
properties,</li><li><code>camel-example-cdi-osgi</code> - a CDI
application using the SJMS component that can be executed inside an OSGi
container using PAX CDI,</li><li><code>camel-example-cdi-test</code> -
demonstrates the testing features that are provided as part of the integration
between Camel and CDI,</li><li><code>camel-example-cdi-rest-servlet</code>
- illustrates the Camel REST DSL being used in a Web application that uses
CDI as dependency injection
framework,</li><li><code>camel-example-widget-gadget-cdi</code> - the Widget
and Gadget use-case from the EIP book implemented in Java with CDI dependency
Injection,</li><li><span><span><code>camel-example-swagger-cdi</code> -
a</span>n example using REST DSL and Swagger Java with CDI.</span></li></ul><h3
id="CDI-SeeAlso">See Also</h3><ul><li><a shape="rect"
href="cdi-testing.html">Camel CDI Testing</a></li>
<li><a shape="rect" class="external-link" href="http://www.cdi-spec.org";
rel="nofollow">CDI Web site</a></li><li><a shape="rect" class="external-link"
href="http://www.cdi-spec.org/ecosystem/"; rel="nofollow">CDI
ecosystem</a></li><li><a shape="rect" class="external-link"
href="https://github.com/astefanutti/further-cdi"; rel="nofollow">Going further
with CDI</a> (See Camel CDI section)</li></ul></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/spring-web-services.html
==============================================================================
--- websites/production/camel/content/spring-web-services.html (original)
+++ websites/production/camel/content/spring-web-services.html Wed Mar 9
15:22:14 2016
@@ -96,18 +96,7 @@
</div></div><div class="confluence-information-macro
confluence-information-macro-information"><p
class="title">Dependencies</p><span class="aui-icon aui-icon-small
aui-iconfont-info confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>As of Camel 2.8 this component
ships with Spring-WS 2.0.x which (like the rest of Camel) requires Spring
3.0.x.</p><p>Earlier Camel versions shipped Spring-WS 1.5.9 which is compatible
with Spring 2.5.x and 3.0.x. In order to run earlier versions of
<code>camel-spring-ws</code> on Spring 2.5.x you need to add the
<code>spring-webmvc</code> module from Spring 2.5.x. In order to run Spring-WS
1.5.9 on Spring 3.0.x you need to exclude the OXM module from Spring 3.0.x as
this module is also included in Spring-WS 1.5.9 (see <a shape="rect"
class="external-link"
href="http://stackoverflow.com/questions/3313314/can-spring-ws-1-5-be-used-with-spring-3";
rel="nofollow">this post</a>)</p></div></div><h3 id="SpringWebService
s-URIformat">URI format</h3><p>The URI scheme for this component is as
follows</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[spring-ws:[mapping-type:]address[?options]
]]></script>
-</div></div><p>To expose a web service <strong>mapping-type</strong> needs to
be set to any of the following:</p><div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p> Mapping type </p></th><th
colspan="1" rowspan="1" class="confluenceTh"><p> Description
</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>rootqname</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Offers the option to map web service requests based on
the qualified name of the root element contained in the message.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>soapaction</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Used to map web service requests based on the SOAP
action specified in the header of the message. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>uri</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> In order to map web service
requests that target a specific URI. </p></td></tr><tr><td colspan="1"
rowspan="1"
class="confluenceTd"><p> <code>xpathresult</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> Used to map web service requests based on
the evaluation of an XPath <code>expression</code> against the incoming
message. The result of the evaluation should match the XPath result specified
in the endpoint URI. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>beanname</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> Allows you to reference an
<code>org.apache.camel.component.spring.ws.bean.CamelEndpointDispatcher</code>
object in order to integrate with existing (legacy) <a shape="rect"
class="external-link"
href="http://static.springsource.org/spring-ws/sites/1.5/reference/html/server.html#server-endpoint-mapping";
rel="nofollow">endpoint mappings</a> like
<code>PayloadRootQNameEndpointMapping</code>,
<code>SoapActionEndpointMapping</code>, etc </p></td></tr></tbody></table></div>
-</div><p>As a consumer the <strong>address</strong> should contain a value
relevant to the specified mapping-type (e.g. a SOAP action, XPath expression).
As a producer the address should be set to the URI of the web service your
calling upon.</p><p>You can append query <strong>options</strong> to the URI in
the following format,
<code>?option=value&option=value&...</code></p><h3
id="SpringWebServices-Options">Options</h3><div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p> Required? </p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>soapAction</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> No </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> SOAP action to include inside
a SOAP request when accessing remote web services </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>
<code>wsAddressingAction</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> No </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> WS-Addressing 1.0 action header to include when
accessing web services. The <code>To</code> header is set to the
<em>address</em> of the web service as specified in the endpoint URI (default
Spri
ng-WS behavior). </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>expression</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> Only when <em>mapping-type</em> is
<code>xpathresult</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> XPath expression to use in the process of mapping web
service requests, should match the result specified by <code>xpathresult</code>
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>timeout</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> No </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.10:</strong> Sets the socket read
timeout (in milliseconds) while invoking a webservice using the producer, see
<a shape="rect" class="external-link"
href="http://docs.oracle.com/javase/6/docs/api/java/net/URLConnection.html#setReadTimeout(int)"
rel="nofollow">URLConnection.setReadTimeout()</a> and <a shape="rect"
class="external-
link"
href="http://static.springsource.org/spring-ws/site/apidocs/org/springframework/ws/transport/http/CommonsHttpMessageSender.html#setReadTimeout(int)"
rel="nofollow">CommonsHttpMessageSender.setReadTimeout()</a>.  This
option works when using the built-in message sender
implementations: <em>CommonsHttpMessageSender</em> and <em>HttpUrlConnectionMessageSender</em>.
 One of these implementations will be used by default for HTTP based
services unless you customize the Spring WS configuration options supplied to
the component.  If you are using a non-standard sender, it is assumed that
you will handle your own timeout configuration.<br clear="none"
class="atl-forced-newline">
-<strong>Camel 2.12:</strong> The built-in message
sender <em>HttpComponentsMessageSender</em> is considered
<strong>instead of</strong> <em>CommonsHttpMessageSender</em> which
has been deprecated, see <a shape="rect" class="external-link"
href="http://static.springsource.org/spring-ws/site/apidocs/org/springframework/ws/transport/http/HttpComponentsMessageSender.html#setReadTimeout(int)"
rel="nofollow">HttpComponentsMessageSender.setReadTimeout()</a>.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>sslContextParameters</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> No </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.10:</strong> Reference to
an <code>org.apache.camel.util.jsse.SSLContextParameters</code>
in the <a shape="rect" class="external-link"
href="http://camel.apache.org/registry.html";>Registry</a>.  See <a
shape="rect" class="external-link" h
ref="http://camel.apache.org/http4.html#HTTP4-UsingtheJSSEConfigurationUtility";>Using
the JSSE Configuration Utility</a>.  This option works when using the
built-in message sender
implementations: <em>CommonsHttpMessageSender</em> and <em>HttpUrlConnectionMessageSender</em>.
 One of these implementations will be used by default for HTTP based
services unless you customize the Spring WS configuration options supplied to
the component.  If you are using a non-standard sender, it is assumed that
you will handle your own TLS configuration.<br clear="none"
class="atl-forced-newline">
-<strong>Camel 2.12:</strong> The built-in message
sender <em>HttpComponentsMessageSender</em> is considered
<strong>instead of</strong> <em>CommonsHttpMessageSender</em> which
has been deprecated. </p></td></tr></tbody></table></div>
-</div><h4 id="SpringWebServices-Registrybasedoptions">Registry based
options</h4><p>The following options can be specified in the registry (most
likely a Spring ApplicationContext) and referenced from the endpoint URI using
the # notation.</p><div class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p> Required? </p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>
<code>webServiceTemplate</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> No </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Option to provide a custom <a shape="rect"
class="external-link"
href="http://static.springsource.org/spring-ws/sites/1.5/apidocs/org/springframework/ws/client/core/WebServiceTemplate.html";
rel="nofollow">WebServiceTemplate</a>. This allows for full control over
client-side web services handling; like adding a custom interceptor or
specifying a fault resolver, message sender or message factory.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>messageSender</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> No </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> Option to provide a custom <a
shape="rect" class="external-link"
href="http://static.springsource.org/spring-ws/sites/1.5/apidocs/org/springframework/ws/transport/WebServiceMessageSender.html";
rel="nofollow">WebServiceMessageSender</a>. For example to perform
authentication or use alternative transports </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>messageFactory</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> No </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> Option to provide a custom <a shape="rect"
class="external-link"
href="http://static.springsource.org/spring-ws/sites/1.5/apidocs/org/springframework/ws/WebServiceMessageFactory.html";
rel="nofollow">WebServiceMessageFactory</a>. For example when you want Apache
Axiom to handle web service messages instead of SAAJ </p></td></tr><tr><td co
lspan="1" rowspan="1" class="confluenceTd"><p> <code>transformerFactory</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> No </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> Option to override default
TransformerFactory. The provided transformer factory must be of type
<code>javax.xml.transform.TransformerFactory</code> </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>endpointMapping</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Only when
<em>mapping-type</em> is <code>rootqname</code>, <code>soapaction</code>,
<code>uri</code> or <code>xpathresult</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> Reference to an instance of
<code>org.apache.camel.component.spring.ws.bean.CamelEndpointMapping</code> in
the Registry/ApplicationContext. Only one bean is required in the registry to
serve all Camel/Spring-WS endpoints. This bean is auto-discovered by the <a
shape="rect" class="external-
link"
href="http://static.springsource.org/spring-ws/sites/1.5/apidocs/org/springframework/ws/server/MessageDispatcher.html";
rel="nofollow">MessageDispatcher</a> and used to map requests to Camel
endpoints based on characteristics specified on the endpoint (like root QName,
SOAP action, etc) </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>messageFilter</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> No </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>Camel 2.10.3</strong> Option to provide a
custom MessageFilter. For example when you want to process your headers or
attachments by your own. </p></td></tr></tbody></table></div>
-
-</div><h3 id="SpringWebServices-Messageheaders">Message headers</h3><div
class="confluenceTableSmall">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>
<code>CamelSpringWebserviceEndpointUri</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> String </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> URI of the web service your accessing as a
client, overrides <em>address</em> part of the endpoint URI
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>CamelSpringWebserviceSoapAction</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> String </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> Header to specify the SOAP action of the
message, overrides <code>soapAction</code> option if present
</p></td></tr><tr><td colspan="1
" rowspan="1" class="confluenceTd"><p>
<code>CamelSpringWebserviceAddressingAction</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> URI </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Use this header to specify the WS-Addressing action of
the message, overrides <code>wsAddressingAction</code> option if present
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>CamelSpringWebserviceSoapHeader</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> Source </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11.1:</strong> Use this
header to specify/access the SOAP headers of the message.
</p></td></tr></tbody></table></div>
-</div><h2 id="SpringWebServices-Accessingwebservices">Accessing web
services</h2><p>To call a web service at <code><a shape="rect"
class="external-link" href="http://foo.com/bar";
rel="nofollow">http://foo.com/bar</a></code> simply define a route:</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><p>To expose a web service <strong>mapping-type</strong> needs to
be set to any of the following:</p><div class="confluenceTableSmall"><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1"
rowspan="1" class="confluenceTh"><p>Mapping type</p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>rootqname</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Offers the option to map web service
requests based on the qualified name of the root element contained in the
message.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>soapaction</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Used to map web service requests based on
the SOAP action specified in the header of the message.</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>uri</code></p></td><td
colspan="1" rowspan="1" cl
ass="confluenceTd"><p>In order to map web service requests that target a
specific URI.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>xpathresult</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Used to map web service requests based on
the evaluation of an XPath <code>expression</code> against the incoming
message. The result of the evaluation should match the XPath result specified
in the endpoint URI.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>beanname</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Allows you to reference an
<code>org.apache.camel.component.spring.ws.bean.CamelEndpointDispatcher</code>
object in order to integrate with existing (legacy) <a shape="rect"
class="external-link"
href="http://static.springsource.org/spring-ws/sites/1.5/reference/html/server.html#server-endpoint-mapping";
rel="nofollow">endpoint mappings</a> like
<code>PayloadRootQNameEndpointMapping</code>,
<code>SoapActionEndpointMapping</code>,
etc</p></td></tr></tbody></table></div></div><p>As a consumer the
<strong>address</strong> should contain a value relevant to the specified
mapping-type (e.g. a SOAP action, XPath expression). As a producer the address
should be set to the URI of the web service your calling upon.</p><p>You can
append query <strong>options</strong> to the URI in the following format,
<code>?option=value&option=value&...</code></p><h3
id="SpringWebServices-Options">Options</h3><div
class="confluenceTableSmall"><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Required?</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>soapAction</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1" rowsp
an="1" class="confluenceTd"><p>SOAP action to include inside a SOAP request
when accessing remote web services</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>wsAddressingAction</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>WS-Addressing 1.0 action header to include when
accessing web services. The <code>To</code> header is set to the
<em>address</em> of the web service as specified in the endpoint URI (default
Spring-WS behavior).</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd">outputAction</td><td colspan="1" rowspan="1"
class="confluenceTd">No</td><td colspan="1" rowspan="1"
class="confluenceTd"><p><span style="color: rgb(0,0,0);">Signifies the value
for the response WS-Addressing Action<span style="color:
rgb(119,183,103);"> </span>header that is provided by the
method.</span> </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"
>faultAction</td><td colspan="1" rowspan="1" class="confluenceTd">No</td><td
>colspan="1" rowspan="1" class="confluenceTd"><p><span style="color:
>rgb(0,0,0);"><span style="line-height: 1.42857;">Signifies the value for the
>faultAction response WS-Addressing</span><span style="line-height:
>1.42857;"><span style="color: rgb(119,183,103);"> </span></span><span
>style="line-height: 1.42857;">Fault Action</span><span style="line-height:
>1.42857;"> </span><span style="line-height: 1.42857;">header that is
>provided by the method.</span></span></p></td></tr><tr><td colspan="1"
>rowspan="1" class="confluenceTd">faultTo</td><td colspan="1" rowspan="1"
>class="confluenceTd"><span>No</span></td><td colspan="1" rowspan="1"
>class="confluenceTd"><span style="color: rgb(0,0,0);">Signifies the value for
>the faultAction response WS-Addressing FaultTo header that is provided by the
>method.</span></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd">replyTo</td><td colspan="1" rowspan="1
" class="confluenceTd"><span>No</span></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><span style="color: rgb(0,0,0);">Signifies the value
for the replyTo response WS-Addressing<span style="color:
rgb(119,183,103);"> </span>ReplyTo header that is provided by the
method.</span></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>expression</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Only when <em>mapping-type</em> is
<code>xpathresult</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>XPath expression to use in the process of mapping web
service requests, should match the result specified by
<code>xpathresult</code></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>timeout</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.10:</strong> Sets the socket read
timeout (in milliseconds) while inv
oking a webservice using the producer, see <a shape="rect"
class="external-link"
href="http://docs.oracle.com/javase/6/docs/api/java/net/URLConnection.html#setReadTimeout(int)"
rel="nofollow">URLConnection.setReadTimeout()</a> and <a shape="rect"
class="external-link"
href="http://static.springsource.org/spring-ws/site/apidocs/org/springframework/ws/transport/http/CommonsHttpMessageSender.html#setReadTimeout(int)"
rel="nofollow">CommonsHttpMessageSender.setReadTimeout()</a>.  This
option works when using the built-in message sender
implementations: <em>CommonsHttpMessageSender</em> and <em>HttpUrlConnectionMessageSender</em>.
 One of these implementations will be used by default for HTTP based
services unless you customize the Spring WS configuration options supplied to
the component.  If you are using a non-standard sender, it is assumed that
you will handle your own timeout configuration.<br clear="none"
class="atl-forced-newline"> <strong>Camel 2.12:
</strong> The built-in message
sender <em>HttpComponentsMessageSender</em> is considered
<strong>instead of</strong> <em>CommonsHttpMessageSender</em> which
has been deprecated, see <a shape="rect" class="external-link"
href="http://static.springsource.org/spring-ws/site/apidocs/org/springframework/ws/transport/http/HttpComponentsMessageSender.html#setReadTimeout(int)"
rel="nofollow">HttpComponentsMessageSender.setReadTimeout()</a>.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>sslContextParameters</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.10:</strong> Reference
to an <code>org.apache.camel.util.jsse.SSLContextParameters</code>
in the <a shape="rect" class="external-link"
href="http://camel.apache.org/registry.html";>Registry</a>.  See <a
shape="rect" class="external-link" href="http://camel.apache.
org/http4.html#HTTP4-UsingtheJSSEConfigurationUtility">Using the JSSE
Configuration Utility</a>.  This option works when using the built-in
message sender
implementations: <em>CommonsHttpMessageSender</em> and <em>HttpUrlConnectionMessageSender</em>.
 One of these implementations will be used by default for HTTP based
services unless you customize the Spring WS configuration options supplied to
the component.  If you are using a non-standard sender, it is assumed that
you will handle your own TLS configuration.<br clear="none"
class="atl-forced-newline"> <strong>Camel 2.12:</strong> The built-in
message sender <em>HttpComponentsMessageSender</em> is considered
<strong>instead of</strong> <em>CommonsHttpMessageSender</em> which
has been deprecated.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>webServiceTemplate</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>No</p></td><td colspan=
"1" rowspan="1" class="confluenceTd"><p>Option to provide a custom <a
shape="rect" class="external-link"
href="http://static.springsource.org/spring-ws/sites/1.5/apidocs/org/springframework/ws/client/core/WebServiceTemplate.html";
rel="nofollow">WebServiceTemplate</a>. This allows for full control over
client-side web services handling; like adding a custom interceptor or
specifying a fault resolver, message sender or message
factory.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>messageSender</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Option to provide a custom <a shape="rect"
class="external-link"
href="http://static.springsource.org/spring-ws/sites/1.5/apidocs/org/springframework/ws/transport/WebServiceMessageSender.html";
rel="nofollow">WebServiceMessageSender</a>. For example to perform
authentication or use alternative transports</p></td></tr><tr><td colspan="1" ro
wspan="1" class="confluenceTd"><p><code>messageFactory</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Option to provide a custom <a shape="rect"
class="external-link"
href="http://static.springsource.org/spring-ws/sites/1.5/apidocs/org/springframework/ws/WebServiceMessageFactory.html";
rel="nofollow">WebServiceMessageFactory</a>. For example when you want Apache
Axiom to handle web service messages instead of SAAJ</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>endpointMapping</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Only when <em>mapping-type</em> is
<code>rootqname</code>, <code>soapaction</code>, <code>uri</code> or
<code>xpathresult</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Reference to an instance of <code><a shape="rect"
class="external-link" href="http://org.apache.camel.component.spring.ws";
rel="nofollow">org.apache.c
amel.component.spring.ws</a>.bean.CamelEndpointMapping</code> in the
Registry/ApplicationContext. Only one bean is required in the registry to serve
all Camel/Spring-WS endpoints. This bean is auto-discovered by the <a
shape="rect" class="external-link"
href="http://static.springsource.org/spring-ws/sites/1.5/apidocs/org/springframework/ws/server/MessageDispatcher.html";
rel="nofollow">MessageDispatcher</a> and used to map requests to Camel
endpoints based on characteristics specified on the endpoint (like root QName,
SOAP action, etc)</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd">endpointDispatcher</td><td colspan="1" rowspan="1"
class="confluenceTd">No</td><td colspan="1" rowspan="1"
class="confluenceTd"> Spring {@link <a shape="rect" class="external-link"
href="http://org.springframework.ws";
rel="nofollow">org.springframework.ws</a>.server.endpoint.MessageEndpoint} for
dispatching messages received by Spring-WS to a Camel endpoint, to integrate
with existi
ng (legacy) endpoint mappings like PayloadRootQNameEndpointMapping,
SoapActionEndpointMapping, etc.</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>messageFilter</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>Camel 2.10.3</strong> Option to provide a
custom MessageFilter. For example when you want to process your headers or
attachments by your own.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd">messageIdStrategy</td><td colspan="1" rowspan="1"
class="confluenceTd">No</td><td colspan="1" rowspan="1" class="confluenceTd">A
custom MessageIdStrategy to control generation of unique message
ids</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><span>webServiceEndpointUri</span></td><td colspan="1"
rowspan="1" class="confluenceTd">No</td><td colspan="1" rowspan="1"
class="confluenceTd">The default Web Service endpoint uri to use for the
producer</
td></tr></tbody></table></div></div><h4
id="SpringWebServices-Messageheaders">Message headers</h4><div
class="confluenceTableSmall"><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>CamelSpringWebserviceEndpointUri</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>String</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>URI of the web service your accessing as a
client, overrides <em>address</em> part of the endpoint
URI</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>CamelSpringWebserviceSoapAction</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>String</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Header to specify t
he SOAP action of the message, overrides <code>soapAction</code> option if
present</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><span style="color:
rgb(0,0,0);">CamelSpringWebserviceSoapHeader</span></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><span>Source</span></td><td colspan="1"
rowspan="1" class="confluenceTd"><strong>Camel 2.11.1:</strong><span> Use this
header to specify/access the SOAP headers of the
message.</span></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>CamelSpringWebserviceAddressingAction</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>URI</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Use this header to specify the
WS-Addressing action of the message, overrides <code>wsAddressingAction</code>
option if present</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><span style="color:
rgb(0,0,0);">CamelSpringWebserviceAddressingFaultTo</span></p></td><td cols
pan="1" rowspan="1" class="confluenceTd">URI</td><td colspan="1" rowspan="1"
class="confluenceTd"><span>Use this header to specify the </span> <span
style="color: rgb(0,0,0);">WS-Addressing FaultTo <span>, overrides faultTo
option if present</span></span></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><span style="color:
rgb(0,0,0);">CamelSpringWebserviceAddressingReplyTo</span></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><span>URI</span></td><td
colspan="1" rowspan="1" class="confluenceTd"><span>Use this header to specify
the </span><span> </span><span style="color: rgb(0,0,0);">WS-Addressing
ReplyTo , overrides replyTo option if present</span></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p><span style="color:
rgb(0,0,0);">CamelSpringWebserviceAddressingOutputAction</span></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><span>URI</span></td><td
colspan="1" rowspan="1" class="confluenceTd"><span style="color: rgb(0,
0,0);"><span>Use this header to specify the</span> WS-Addressing Action<span
style="color: rgb(0,0,0);"> , overrides outputAction option if
present</span></span></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><span style="color:
rgb(0,0,0);">CamelSpringWebserviceAddressingFaultAction</span></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><span>URI</span></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><span style="color:
rgb(0,0,0);">Use this header to specify the</span><span style="color:
rgb(0,0,0);"> WS-Addressing <span style="color: rgb(0,0,0);">Fault
Action</span></span><span style="color: rgb(0,0,0);"> , overrides faultAction
option if present</span></p></td></tr></tbody></table></div></div><h2
id="SpringWebServices-Accessingwebservices">Accessing web services</h2><p>To
call a web service at <code><a shape="rect" class="external-link"
href="http://foo.com/bar"; rel="nofollow">http://foo.com/bar</a></code> simply
define a route:</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
<script class="brush: java; gutter: false; theme: Default"
type="syntaxhighlighter"><![CDATA[from("direct:example").to("spring-ws:http://foo.com/bar")
]]></script>
</div></div><p>And sent a message:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
