You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by bu...@apache.org on 2014/03/16 16:19:30 UTC
svn commit: r901844 - in /websites/production/camel/content:
book-cookbook.html book-in-one-page.html cache/main.pageCache
camel-transport-for-cxf.html cxf-example.html
Author: buildbot
Date: Sun Mar 16 15:19:30 2014
New Revision: 901844
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/book-cookbook.html
websites/production/camel/content/book-in-one-page.html
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/camel-transport-for-cxf.html
websites/production/camel/content/cxf-example.html
Modified: websites/production/camel/content/book-cookbook.html
==============================================================================
--- websites/production/camel/content/book-cookbook.html (original)
+++ websites/production/camel/content/book-cookbook.html Sun Mar 16 15:19:30 2014
@@ -2957,24 +2957,8 @@ from("file:data/in").process(n
<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[from("jms:Orders").to("jms:Consumer.A", "jms:Consumer.B", ...); ]]></script>
</div></div></li><li>for consumer A consume from <strong>jms:Consumer.A</strong></li></ul>
-<h2 id="Bookcookbook-What'stheCamelTransportforCXF">What's the Camel Transport for CXF</h2>
-
-<p>In CXF you offer or consume a webservice by defining it´s address. The first part of the address specifies the protocol to use. For example address="http://localhost:9000" in an endpoint configuration means your service will be offered using the http protocol on port 9000 of localhost. When you integrate Camel Tranport into CXF you get a new transport "camel". So you can specify address="camel://direct:MyEndpointName" to bind the CXF service address to a camel direct endpoint.</p>
-
-<p>Technically speaking Camel transport for CXF is a component which implements the <a shape="rect" class="external-link" href="http://cwiki.apache.org/CXF20DOC/cxf-architecture.html#CXFArchitecture-Transports">CXF transport API</a> with the Camel core library. This allows you to use camel´s routing engine and integration patterns support smoothly together with your CXF services.</p>
-
-
-<h2 id="Bookcookbook-IntegrateCamelintoCXFtransportlayer">Integrate Camel into CXF transport layer</h2>
-
-<p>To include the Camel Tranport into your CXF bus you use the CamelTransportFactory. You can do this in Java as well as in Spring.</p>
-
-<h3 id="Bookcookbook-SettinguptheCamelTransportinSpring">Setting up the Camel Transport in Spring</h3>
-
-<p>You can use the following snippet in your applicationcontext if you want to configure anything special. If you only want to activate the camel transport you do not have to do anything in your application context. As soon as you include the camel-cxf-transport jar (or camel-cxf.jar if your camel version is less than 2.7.x) in your app cxf will scan the jar and load a CamelTransportFactory for you. </p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-<!-- you don't need to specify the CamelTransportFactory configuration as it is auto load by CXF bus -->
+<h2 id="Bookcookbook-What'stheCamelTransportforCXF">What's the Camel Transport for CXF</h2><p>In CXF you offer or consume a webservice by defining it´s address. The first part of the address specifies the protocol to use. For example address="http://localhost:9000" in an endpoint configuration means your service will be offered using the http protocol on port 9000 of localhost. When you integrate Camel Tranport into CXF you get a new transport "camel". So you can specify address="camel://direct:MyEndpointName" to bind the CXF service address to a camel direct endpoint.</p><p>Technically speaking Camel transport for CXF is a component which implements the <a shape="rect" class="external-link" href="http://cwiki.apache.org/CXF20DOC/cxf-architecture.html#CXFArchitecture-Transports">CXF transport API</a> with the Camel core library. This allows you to easily use camel´s routing engine and integration patterns support together with your CXF services.</p><h2 id="Bookcookbook-Int
egrateCamelintoCXFtransportlayer">Integrate Camel into CXF transport layer</h2><p>To include the Camel Tranport into your CXF bus you use the CamelTransportFactory. You can do this in Java as well as in Spring.</p><h3 id="Bookcookbook-SettinguptheCamelTransportinSpring">Setting up the Camel Transport in Spring</h3><p>You can use the following snippet in your applicationcontext if you want to configure anything special. If you only want to activate the camel transport you do not have to do anything in your application context. As soon as you include the camel-cxf-transport jar (or camel-cxf.jar if your camel version is less than 2.7.x) in your app, cxf will scan the jar and load a CamelTransportFactory for you.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[<!-- you don't need to specify the CamelTransportFactory configuration as it is auto load by CXF bus -->
<bean class="org.apache.camel.component.cxf.transport.CamelTransportFactory">
<property name="bus" ref="cxf" />
<property name="camelContext" ref="camelContext" />
@@ -2992,14 +2976,8 @@ from("file:data/in").process(n
</property>
</bean>
]]></script>
-</div></div>
-
-<h3 id="Bookcookbook-IntegratingtheCamelTransportinaprogrammaticway">Integrating the Camel Transport in a programmatic way</h3>
-
-<p>Camel transport provides a setContext method that you could use to set the Camel context into the transport factory. If you want this factory take effect, you need to register the factory into the CXF bus. Here is a full example for you.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-import org.apache.cxf.Bus;
+</div></div><h3 id="Bookcookbook-IntegratingtheCamelTransportinaprogrammaticway">Integrating the Camel Transport in a programmatic way</h3><p>Camel transport provides a setContext method that you could use to set the Camel context into the transport factory. If you want this factory take effect, you need to register the factory into the CXF bus. Here is a full example for you.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[import org.apache.cxf.Bus;
import org.apache.cxf.BusFactory;
import org.apache.cxf.transport.ConduitInitiatorManager;
import org.apache.cxf.transport.DestinationFactoryManager;
@@ -3023,17 +3001,8 @@ dfm.registerDestinationFactory(CamelTran
// set or bus as the default bus for cxf
BusFactory.setDefaultBus(bus);
]]></script>
-</div></div>
-
-<h2 id="Bookcookbook-ConfigurethedestinationandconduitwithSpring">Configure the destination and conduit with Spring</h2>
-
-<h3 id="Bookcookbook-Namespace">Namespace</h3>
-
-<p>The elements used to configure an Camel transport endpoint are defined in the namespace <code><a shape="rect" href="http://cxf.apache.org/transports/camel">http://cxf.apache.org/transports/camel</a></code>. It is commonly referred to using the prefix <code>camel</code>. In order to use the Camel transport configuration elements you will need to add the lines shown below to the beans element of your endpoint's configuration file. In addition, you will need to add the configuration elements' namespace to the <code>xsi:schemaLocation</code> attribute.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Adding the Configuration Namespace</b></div><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-<beans ...
+</div></div><h2 id="Bookcookbook-ConfigurethedestinationandconduitwithSpring">Configure the destination and conduit with Spring</h2><h3 id="Bookcookbook-Namespace">Namespace</h3><p>The elements used to configure an Camel transport endpoint are defined in the namespace <code><a shape="rect" href="http://cxf.apache.org/transports/camel">http://cxf.apache.org/transports/camel</a></code>. It is commonly referred to using the prefix <code>camel</code>. In order to use the Camel transport configuration elements, you will need to add the lines shown below to the beans element of your endpoint's configuration file. In addition, you will need to add the configuration elements' namespace to the <code>xsi:schemaLocation</code> attribute.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Adding the Configuration Namespace</b></div><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[<beans ...
xmlns:camel="http://cxf.apache.org/transports/camel
...
xsi:schemaLocation="...
@@ -3041,16 +3010,8 @@ BusFactory.setDefaultBus(bus);
http://cxf.apache.org/transports/camel.xsd
...>
]]></script>
-</div></div>
-
-<h3 id="Bookcookbook-Thedestinationelement">The <code>destination</code> element</h3>
-
-<p>You configure an Camel transport server endpoint using the <code>camel:destination</code> element and its children. The <code>camel:destination</code> element takes a single attribute, <code>name</code>, the specifies the WSDL port element that corresponds to the endpoint. The value for the <code>name</code> attribute takes the form <em>portQName</em><code>.camel-destination</code>. The example below shows the <code>camel:destination</code> element that would be used to add configuration for an endpoint that was specified by the WSDL fragment <code><port binding="widgetSOAPBinding" name="widgetSOAPPort></code> if the endpoint's target namespace was <code><a shape="rect" class="external-link" href="http://widgets.widgetvendor.net" rel="nofollow">http://widgets.widgetvendor.net</a></code>.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>camel:destination Element</b></div><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-
-...
+</div></div><h3 id="Bookcookbook-Thedestinationelement">The <code>destination</code> element</h3><p>You configure an Camel transport server endpoint using the <code>camel:destination</code> element and its children. The <code>camel:destination</code> element takes a single attribute, <code>name</code>, the specifies the WSDL port element that corresponds to the endpoint. The value for the <code>name</code> attribute takes the form <em>portQName</em><code>.camel-destination</code>. The example below shows the <code>camel:destination</code> element that would be used to add configuration for an endpoint that was specified by the WSDL fragment <code><port binding="widgetSOAPBinding" name="widgetSOAPPort></code> if the endpoint's target namespace was <code><a shape="rect" class="external-link" href="http://widgets.widgetvendor.net" rel="nofollow">http://widgets.widgetvendor.net</a></code>.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader
pdl" style="border-bottom-width: 1px;"><b>camel:destination Element</b></div><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[...
<camel:destination name="{http://widgets/widgetvendor.net}widgetSOAPPort.http-destination>
<camelContext id="context" xmlns="http://activemq.apache.org/camel/schema/spring">
<route>
@@ -3065,20 +3026,8 @@ BusFactory.setDefaultBus(bus);
...
]]></script>
-</div></div>
-
-<p>The <code>camel:destination</code> element for Spring has a number of child elements that specify configuration information. They are described below.</p>
-
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Element</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>camel-spring:camelContext</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>You can specify the camel context in the camel destination</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>camel:camelContextRef</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The camel context id which you want inject into the camel destination</p></td></tr></tbody></table></div>
-
-
-
-<h3 id="Bookcookbook-Theconduitelement">The <code>conduit</code> element</h3>
-
-<p>You configure an Camel transport client using the <code>camel:conduit</code> element and its children. The <code>camel:conduit</code> element takes a single attribute, <code>name</code>, that specifies the WSDL port element that corresponds to the endpoint. The value for the <code>name</code> attribute takes the form <em>portQName</em><code>.camel-conduit</code>. For example, the code below shows the <code>camel:conduit</code> element that would be used to add configuration for an endpoint that was specified by the WSDL fragment <code><port binding="widgetSOAPBinding" name="widgetSOAPPort></code> if the endpoint's target namespace was <code><a shape="rect" class="external-link" href="http://widgets.widgetvendor.net" rel="nofollow">http://widgets.widgetvendor.net</a></code>.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>http-conf:conduit Element</b></div><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-...
+</div></div><p>The <code>camel:destination</code> element for Spring has a number of child elements that specify configuration information. They are described below.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Element</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>camel-spring:camelContext</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>You can specify the camel context in the camel destination</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>camel:camelContextRef</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The camel context id which you want inject into the camel destination</p></td></tr></tbody></table></div><h3 id="Bookcookbook-Theconduitelement">The <code>conduit</code> element</h3><p>You configure a Camel transport client using the <code
>camel:conduit</code> element and its children. The <code>camel:conduit</code> element takes a single attribute, <code>name</code>, that specifies the WSDL port element that corresponds to the endpoint. The value for the <code>name</code> attribute takes the form <em>portQName</em><code>.camel-conduit</code>. For example, the code below shows the <code>camel:conduit</code> element that would be used to add configuration for an endpoint that was specified by the WSDL fragment <code><port binding="widgetSOAPBinding" name="widgetSOAPPort></code> if the endpoint's target namespace was <code><a shape="rect" class="external-link" href="http://widgets.widgetvendor.net" rel="nofollow">http://widgets.widgetvendor.net</a></code>.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>http-conf:conduit Element</b></div><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[...
<camelContext id="conduit_context" xmlns="http://activemq.apache.org/camel/schema/spring">
<route>
<from uri="direct:EndpointA" />
@@ -3100,21 +3049,8 @@ BusFactory.setDefaultBus(bus);
</camel:conduit>
...
]]></script>
-</div></div>
-
-<p>The <code>camel:conduit</code> element has a number of child elements that specify configuration information. They are described below.</p>
-
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Element</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>camel-spring:camelContext</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>You can specify the camel context in the camel conduit</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>camel:camelContextRef</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The camel context id which you want inject into the camel conduit</p></td></tr></tbody></table></div>
-
-
-<h2 id="Bookcookbook-ConfigurethedestinationandconduitwithBlueprint">Configure the destination and conduit with Blueprint</h2>
-
-<p>From <strong>Camel 2.11.x</strong>, Camel Transport supports to be configured with Blueprint</p>
-
-<p>If you are using blueprint, you should use the the namespace <code><a shape="rect" href="http://cxf.apache.org/transports/camel/blueprint">http://cxf.apache.org/transports/camel/blueprint</a></code> and import the schema like the blow.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Adding the Configuration Namespace for blueprint</b></div><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-<beans ...
+</div></div><p>The <code>camel:conduit</code> element has a number of child elements that specify configuration information. They are described below.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Element</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>camel-spring:camelContext</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>You can specify the camel context in the camel conduit</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>camel:camelContextRef</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The camel context id which you want inject into the camel conduit</p></td></tr></tbody></table></div><h2 id="Bookcookbook-ConfigurethedestinationandconduitwithBlueprint">Configure the destination and conduit with Blueprint</h2><p>From <strong>Camel 2.11.x</s
trong>, Camel Transport supports to be configured with Blueprint</p><p>If you are using blueprint, you should use the the namespace <code><a shape="rect" href="http://cxf.apache.org/transports/camel/blueprint">http://cxf.apache.org/transports/camel/blueprint</a></code> and import the schema like the blow.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Adding the Configuration Namespace for blueprint</b></div><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[<beans ...
xmlns:camel="http://cxf.apache.org/transports/camel/blueprint"
...
xsi:schemaLocation="...
@@ -3122,20 +3058,11 @@ BusFactory.setDefaultBus(bus);
http://cxf.apache.org/schmemas/blueprint/camel.xsd
...>
]]></script>
-</div></div>
-
-<p>In blueprint <code>camel:conduit</code> <code>camel:destination</code> only has one camelContextId attribute, they doesn't support to specify the camel context in the camel destination.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
- <camel:conduit id="*.camel-conduit" camelContextId="camel1" />
+</div></div><p>In blueprint <code>camel:conduit</code> <code>camel:destination</code> only has one camelContextId attribute, they doesn't support to specify the camel context in the camel destination.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ <camel:conduit id="*.camel-conduit" camelContextId="camel1" />
<camel:destination id="*.camel-destination" camelContextId="camel1" />
]]></script>
-</div></div>
-
-<h2 id="Bookcookbook-ExampleUsingCamelasaloadbalancerforCXF">Example Using Camel as a load balancer for CXF</h2>
-
-<p>This example show how to use the camel load balance feature in CXF, and you need load the configuration file in CXF and publish the endpoints on the address "camel://direct:EndpointA" and "camel://direct:EndpointB"</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h2 id="Bookcookbook-ExampleUsingCamelasaloadbalancerforCXF">Example Using Camel as a load balancer for CXF</h2><p>This example shows how to use the camel load balancing feature in CXF. You need to load the configuration file in CXF and publish the endpoints on the address "camel://direct:EndpointA" and "camel://direct:EndpointB"</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -3171,11 +3098,7 @@ BusFactory.setDefaultBus(bus);
</beans>
]]></script>
-</div></div>
-
-<h2 id="Bookcookbook-CompleteHowtoandExampleforattachingCameltoCXF">Complete Howto and Example for attaching Camel to CXF</h2>
-
-<p><a shape="rect" href="better-jms-transport-for-cxf-webservice-using-apache-camel.html">Better JMS Transport for CXF Webservice using Apache Camel</a> </p>
+</div></div><h2 id="Bookcookbook-CompleteHowtoandExampleforattachingCameltoCXF">Complete Howto and Example for attaching Camel to CXF</h2><p><a shape="rect" href="better-jms-transport-for-cxf-webservice-using-apache-camel.html">Better JMS Transport for CXF Webservice using Apache Camel</a> </p>
<h2 id="Bookcookbook-Introduction">Introduction</h2>
<p>When sending an <a shape="rect" href="exchange.html">Exchange</a> to an <a shape="rect" href="endpoint.html">Endpoint</a> you can either use a <a shape="rect" href="routes.html">Route</a> or a <a shape="rect" href="producertemplate.html">ProducerTemplate</a>. This works fine in many scenarios. However you may need to guarantee that an exchange is delivered to the same endpoint that you delivered a previous exchange on. For example in the case of delivering a batch of exchanges to a <a shape="rect" href="mina.html">MINA</a> socket you may need to ensure that they are all delivered through the same socket connection. Furthermore once the batch of exchanges have been delivered the protocol requirements may be such that you are responsible for closing the socket.</p>
Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Sun Mar 16 15:19:30 2014
@@ -3941,24 +3941,8 @@ from("file:data/in").process(n
<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[from("jms:Orders").to("jms:Consumer.A", "jms:Consumer.B", ...); ]]></script>
</div></div></li><li>for consumer A consume from <strong>jms:Consumer.A</strong></li></ul>
-<h2 id="BookInOnePage-What'stheCamelTransportforCXF">What's the Camel Transport for CXF</h2>
-
-<p>In CXF you offer or consume a webservice by defining it´s address. The first part of the address specifies the protocol to use. For example address="http://localhost:9000" in an endpoint configuration means your service will be offered using the http protocol on port 9000 of localhost. When you integrate Camel Tranport into CXF you get a new transport "camel". So you can specify address="camel://direct:MyEndpointName" to bind the CXF service address to a camel direct endpoint.</p>
-
-<p>Technically speaking Camel transport for CXF is a component which implements the <a shape="rect" class="external-link" href="http://cwiki.apache.org/CXF20DOC/cxf-architecture.html#CXFArchitecture-Transports">CXF transport API</a> with the Camel core library. This allows you to use camel´s routing engine and integration patterns support smoothly together with your CXF services.</p>
-
-
-<h2 id="BookInOnePage-IntegrateCamelintoCXFtransportlayer">Integrate Camel into CXF transport layer</h2>
-
-<p>To include the Camel Tranport into your CXF bus you use the CamelTransportFactory. You can do this in Java as well as in Spring.</p>
-
-<h3 id="BookInOnePage-SettinguptheCamelTransportinSpring">Setting up the Camel Transport in Spring</h3>
-
-<p>You can use the following snippet in your applicationcontext if you want to configure anything special. If you only want to activate the camel transport you do not have to do anything in your application context. As soon as you include the camel-cxf-transport jar (or camel-cxf.jar if your camel version is less than 2.7.x) in your app cxf will scan the jar and load a CamelTransportFactory for you. </p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-<!-- you don't need to specify the CamelTransportFactory configuration as it is auto load by CXF bus -->
+<h2 id="BookInOnePage-What'stheCamelTransportforCXF">What's the Camel Transport for CXF</h2><p>In CXF you offer or consume a webservice by defining it´s address. The first part of the address specifies the protocol to use. For example address="http://localhost:9000" in an endpoint configuration means your service will be offered using the http protocol on port 9000 of localhost. When you integrate Camel Tranport into CXF you get a new transport "camel". So you can specify address="camel://direct:MyEndpointName" to bind the CXF service address to a camel direct endpoint.</p><p>Technically speaking Camel transport for CXF is a component which implements the <a shape="rect" class="external-link" href="http://cwiki.apache.org/CXF20DOC/cxf-architecture.html#CXFArchitecture-Transports">CXF transport API</a> with the Camel core library. This allows you to easily use camel´s routing engine and integration patterns support together with your CXF services.</p><h2 id="BookInOnePage-I
ntegrateCamelintoCXFtransportlayer">Integrate Camel into CXF transport layer</h2><p>To include the Camel Tranport into your CXF bus you use the CamelTransportFactory. You can do this in Java as well as in Spring.</p><h3 id="BookInOnePage-SettinguptheCamelTransportinSpring">Setting up the Camel Transport in Spring</h3><p>You can use the following snippet in your applicationcontext if you want to configure anything special. If you only want to activate the camel transport you do not have to do anything in your application context. As soon as you include the camel-cxf-transport jar (or camel-cxf.jar if your camel version is less than 2.7.x) in your app, cxf will scan the jar and load a CamelTransportFactory for you.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[<!-- you don't need to specify the CamelTransportFactory configuration as it is auto load by CXF bus -->
<bean class="org.apache.camel.component.cxf.transport.CamelTransportFactory">
<property name="bus" ref="cxf" />
<property name="camelContext" ref="camelContext" />
@@ -3976,14 +3960,8 @@ from("file:data/in").process(n
</property>
</bean>
]]></script>
-</div></div>
-
-<h3 id="BookInOnePage-IntegratingtheCamelTransportinaprogrammaticway">Integrating the Camel Transport in a programmatic way</h3>
-
-<p>Camel transport provides a setContext method that you could use to set the Camel context into the transport factory. If you want this factory take effect, you need to register the factory into the CXF bus. Here is a full example for you.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-import org.apache.cxf.Bus;
+</div></div><h3 id="BookInOnePage-IntegratingtheCamelTransportinaprogrammaticway">Integrating the Camel Transport in a programmatic way</h3><p>Camel transport provides a setContext method that you could use to set the Camel context into the transport factory. If you want this factory take effect, you need to register the factory into the CXF bus. Here is a full example for you.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[import org.apache.cxf.Bus;
import org.apache.cxf.BusFactory;
import org.apache.cxf.transport.ConduitInitiatorManager;
import org.apache.cxf.transport.DestinationFactoryManager;
@@ -4007,17 +3985,8 @@ dfm.registerDestinationFactory(CamelTran
// set or bus as the default bus for cxf
BusFactory.setDefaultBus(bus);
]]></script>
-</div></div>
-
-<h2 id="BookInOnePage-ConfigurethedestinationandconduitwithSpring">Configure the destination and conduit with Spring</h2>
-
-<h3 id="BookInOnePage-Namespace">Namespace</h3>
-
-<p>The elements used to configure an Camel transport endpoint are defined in the namespace <code><a shape="rect" href="http://cxf.apache.org/transports/camel">http://cxf.apache.org/transports/camel</a></code>. It is commonly referred to using the prefix <code>camel</code>. In order to use the Camel transport configuration elements you will need to add the lines shown below to the beans element of your endpoint's configuration file. In addition, you will need to add the configuration elements' namespace to the <code>xsi:schemaLocation</code> attribute.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Adding the Configuration Namespace</b></div><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-<beans ...
+</div></div><h2 id="BookInOnePage-ConfigurethedestinationandconduitwithSpring">Configure the destination and conduit with Spring</h2><h3 id="BookInOnePage-Namespace">Namespace</h3><p>The elements used to configure an Camel transport endpoint are defined in the namespace <code><a shape="rect" href="http://cxf.apache.org/transports/camel">http://cxf.apache.org/transports/camel</a></code>. It is commonly referred to using the prefix <code>camel</code>. In order to use the Camel transport configuration elements, you will need to add the lines shown below to the beans element of your endpoint's configuration file. In addition, you will need to add the configuration elements' namespace to the <code>xsi:schemaLocation</code> attribute.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Adding the Configuration Namespace</b></div><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[<beans ...
xmlns:camel="http://cxf.apache.org/transports/camel
...
xsi:schemaLocation="...
@@ -4025,16 +3994,8 @@ BusFactory.setDefaultBus(bus);
http://cxf.apache.org/transports/camel.xsd
...>
]]></script>
-</div></div>
-
-<h3 id="BookInOnePage-Thedestinationelement">The <code>destination</code> element</h3>
-
-<p>You configure an Camel transport server endpoint using the <code>camel:destination</code> element and its children. The <code>camel:destination</code> element takes a single attribute, <code>name</code>, the specifies the WSDL port element that corresponds to the endpoint. The value for the <code>name</code> attribute takes the form <em>portQName</em><code>.camel-destination</code>. The example below shows the <code>camel:destination</code> element that would be used to add configuration for an endpoint that was specified by the WSDL fragment <code><port binding="widgetSOAPBinding" name="widgetSOAPPort></code> if the endpoint's target namespace was <code><a shape="rect" class="external-link" href="http://widgets.widgetvendor.net" rel="nofollow">http://widgets.widgetvendor.net</a></code>.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>camel:destination Element</b></div><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-
-...
+</div></div><h3 id="BookInOnePage-Thedestinationelement">The <code>destination</code> element</h3><p>You configure an Camel transport server endpoint using the <code>camel:destination</code> element and its children. The <code>camel:destination</code> element takes a single attribute, <code>name</code>, the specifies the WSDL port element that corresponds to the endpoint. The value for the <code>name</code> attribute takes the form <em>portQName</em><code>.camel-destination</code>. The example below shows the <code>camel:destination</code> element that would be used to add configuration for an endpoint that was specified by the WSDL fragment <code><port binding="widgetSOAPBinding" name="widgetSOAPPort></code> if the endpoint's target namespace was <code><a shape="rect" class="external-link" href="http://widgets.widgetvendor.net" rel="nofollow">http://widgets.widgetvendor.net</a></code>.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeade
r pdl" style="border-bottom-width: 1px;"><b>camel:destination Element</b></div><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[...
<camel:destination name="{http://widgets/widgetvendor.net}widgetSOAPPort.http-destination>
<camelContext id="context" xmlns="http://activemq.apache.org/camel/schema/spring">
<route>
@@ -4049,20 +4010,8 @@ BusFactory.setDefaultBus(bus);
...
]]></script>
-</div></div>
-
-<p>The <code>camel:destination</code> element for Spring has a number of child elements that specify configuration information. They are described below.</p>
-
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Element</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>camel-spring:camelContext</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>You can specify the camel context in the camel destination</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>camel:camelContextRef</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The camel context id which you want inject into the camel destination</p></td></tr></tbody></table></div>
-
-
-
-<h3 id="BookInOnePage-Theconduitelement">The <code>conduit</code> element</h3>
-
-<p>You configure an Camel transport client using the <code>camel:conduit</code> element and its children. The <code>camel:conduit</code> element takes a single attribute, <code>name</code>, that specifies the WSDL port element that corresponds to the endpoint. The value for the <code>name</code> attribute takes the form <em>portQName</em><code>.camel-conduit</code>. For example, the code below shows the <code>camel:conduit</code> element that would be used to add configuration for an endpoint that was specified by the WSDL fragment <code><port binding="widgetSOAPBinding" name="widgetSOAPPort></code> if the endpoint's target namespace was <code><a shape="rect" class="external-link" href="http://widgets.widgetvendor.net" rel="nofollow">http://widgets.widgetvendor.net</a></code>.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>http-conf:conduit Element</b></div><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-...
+</div></div><p>The <code>camel:destination</code> element for Spring has a number of child elements that specify configuration information. They are described below.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Element</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>camel-spring:camelContext</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>You can specify the camel context in the camel destination</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>camel:camelContextRef</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The camel context id which you want inject into the camel destination</p></td></tr></tbody></table></div><h3 id="BookInOnePage-Theconduitelement">The <code>conduit</code> element</h3><p>You configure a Camel transport client using the <cod
e>camel:conduit</code> element and its children. The <code>camel:conduit</code> element takes a single attribute, <code>name</code>, that specifies the WSDL port element that corresponds to the endpoint. The value for the <code>name</code> attribute takes the form <em>portQName</em><code>.camel-conduit</code>. For example, the code below shows the <code>camel:conduit</code> element that would be used to add configuration for an endpoint that was specified by the WSDL fragment <code><port binding="widgetSOAPBinding" name="widgetSOAPPort></code> if the endpoint's target namespace was <code><a shape="rect" class="external-link" href="http://widgets.widgetvendor.net" rel="nofollow">http://widgets.widgetvendor.net</a></code>.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>http-conf:conduit Element</b></div><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[...
<camelContext id="conduit_context" xmlns="http://activemq.apache.org/camel/schema/spring">
<route>
<from uri="direct:EndpointA" />
@@ -4084,21 +4033,8 @@ BusFactory.setDefaultBus(bus);
</camel:conduit>
...
]]></script>
-</div></div>
-
-<p>The <code>camel:conduit</code> element has a number of child elements that specify configuration information. They are described below.</p>
-
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Element</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>camel-spring:camelContext</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>You can specify the camel context in the camel conduit</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>camel:camelContextRef</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The camel context id which you want inject into the camel conduit</p></td></tr></tbody></table></div>
-
-
-<h2 id="BookInOnePage-ConfigurethedestinationandconduitwithBlueprint">Configure the destination and conduit with Blueprint</h2>
-
-<p>From <strong>Camel 2.11.x</strong>, Camel Transport supports to be configured with Blueprint</p>
-
-<p>If you are using blueprint, you should use the the namespace <code><a shape="rect" href="http://cxf.apache.org/transports/camel/blueprint">http://cxf.apache.org/transports/camel/blueprint</a></code> and import the schema like the blow.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Adding the Configuration Namespace for blueprint</b></div><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-<beans ...
+</div></div><p>The <code>camel:conduit</code> element has a number of child elements that specify configuration information. They are described below.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Element</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>camel-spring:camelContext</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>You can specify the camel context in the camel conduit</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>camel:camelContextRef</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The camel context id which you want inject into the camel conduit</p></td></tr></tbody></table></div><h2 id="BookInOnePage-ConfigurethedestinationandconduitwithBlueprint">Configure the destination and conduit with Blueprint</h2><p>From <strong>Camel 2.11.x</
strong>, Camel Transport supports to be configured with Blueprint</p><p>If you are using blueprint, you should use the the namespace <code><a shape="rect" href="http://cxf.apache.org/transports/camel/blueprint">http://cxf.apache.org/transports/camel/blueprint</a></code> and import the schema like the blow.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Adding the Configuration Namespace for blueprint</b></div><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[<beans ...
xmlns:camel="http://cxf.apache.org/transports/camel/blueprint"
...
xsi:schemaLocation="...
@@ -4106,20 +4042,11 @@ BusFactory.setDefaultBus(bus);
http://cxf.apache.org/schmemas/blueprint/camel.xsd
...>
]]></script>
-</div></div>
-
-<p>In blueprint <code>camel:conduit</code> <code>camel:destination</code> only has one camelContextId attribute, they doesn't support to specify the camel context in the camel destination.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
- <camel:conduit id="*.camel-conduit" camelContextId="camel1" />
+</div></div><p>In blueprint <code>camel:conduit</code> <code>camel:destination</code> only has one camelContextId attribute, they doesn't support to specify the camel context in the camel destination.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ <camel:conduit id="*.camel-conduit" camelContextId="camel1" />
<camel:destination id="*.camel-destination" camelContextId="camel1" />
]]></script>
-</div></div>
-
-<h2 id="BookInOnePage-ExampleUsingCamelasaloadbalancerforCXF">Example Using Camel as a load balancer for CXF</h2>
-
-<p>This example show how to use the camel load balance feature in CXF, and you need load the configuration file in CXF and publish the endpoints on the address "camel://direct:EndpointA" and "camel://direct:EndpointB"</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h2 id="BookInOnePage-ExampleUsingCamelasaloadbalancerforCXF">Example Using Camel as a load balancer for CXF</h2><p>This example shows how to use the camel load balancing feature in CXF. You need to load the configuration file in CXF and publish the endpoints on the address "camel://direct:EndpointA" and "camel://direct:EndpointB"</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -4155,11 +4082,7 @@ BusFactory.setDefaultBus(bus);
</beans>
]]></script>
-</div></div>
-
-<h2 id="BookInOnePage-CompleteHowtoandExampleforattachingCameltoCXF">Complete Howto and Example for attaching Camel to CXF</h2>
-
-<p><a shape="rect" href="better-jms-transport-for-cxf-webservice-using-apache-camel.html">Better JMS Transport for CXF Webservice using Apache Camel</a> </p>
+</div></div><h2 id="BookInOnePage-CompleteHowtoandExampleforattachingCameltoCXF">Complete Howto and Example for attaching Camel to CXF</h2><p><a shape="rect" href="better-jms-transport-for-cxf-webservice-using-apache-camel.html">Better JMS Transport for CXF Webservice using Apache Camel</a> </p>
<h2 id="BookInOnePage-Introduction.2">Introduction</h2>
<p>When sending an <a shape="rect" href="exchange.html">Exchange</a> to an <a shape="rect" href="endpoint.html">Endpoint</a> you can either use a <a shape="rect" href="routes.html">Route</a> or a <a shape="rect" href="producertemplate.html">ProducerTemplate</a>. This works fine in many scenarios. However you may need to guarantee that an exchange is delivered to the same endpoint that you delivered a previous exchange on. For example in the case of delivering a batch of exchanges to a <a shape="rect" href="mina.html">MINA</a> socket you may need to ensure that they are all delivered through the same socket connection. Furthermore once the batch of exchanges have been delivered the protocol requirements may be such that you are responsible for closing the socket.</p>
@@ -4262,11 +4185,11 @@ While not actual tutorials you might fin
</div>
</div>
<h2 id="BookInOnePage-Preface">Preface</h2><p>This tutorial aims to guide the reader through the stages of creating a project which uses Camel to facilitate the routing of messages from a JMS queue to a <a shape="rect" class="external-link" href="http://www.springramework.org" rel="nofollow">Spring</a> service. The route works in a synchronous fashion returning a response to the client.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1394792359518 {padding: 0px;}
-div.rbtoc1394792359518 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1394792359518 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1394983094887 {padding: 0px;}
+div.rbtoc1394983094887 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1394983094887 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1394792359518">
+/*]]>*/</style></p><div class="toc-macro rbtoc1394983094887">
<ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-JmsRemoting-TutorialonSpringRemotingwithJMS">Tutorial on Spring Remoting with JMS</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-Preface">Preface</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-Prerequisites">Prerequisites</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-Distribution">Distribution</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-About">About</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-CreatetheCamelProject">Create the Camel Project</a>
<ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-JmsRemoting-UpdatethePOMwithDependencies">Update the POM with Dependencies</a></li></ul>
</li><li><a shape="rect" href="#Tutorial-JmsRemoting-WritingtheServer">Writing the Server</a>
@@ -6452,11 +6375,11 @@ So we completed the last piece in the pi
<style type="text/css">/*<![CDATA[*/
-div.rbtoc1394792359809 {padding: 0px;}
-div.rbtoc1394792359809 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1394792359809 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1394983095334 {padding: 0px;}
+div.rbtoc1394983095334 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1394983095334 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="toc-macro rbtoc1394792359809">
+/*]]>*/</style><div class="toc-macro rbtoc1394983095334">
<ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-AXIS-Camel-TutorialusingAxis1.4withApacheCamel">Tutorial using Axis 1.4 with Apache Camel</a>
<ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-AXIS-Camel-Prerequisites">Prerequisites</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-Distribution">Distribution</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-Introduction">Introduction</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-SettinguptheprojecttorunAxis">Setting up the project to run Axis</a>
<ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-AXIS-Camel-Maven2">Maven 2</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-wsdl">wsdl</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-ConfiguringAxis">Configuring Axis</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-RunningtheExample">Running the Example</a></li></ul>
@@ -21680,11 +21603,11 @@ template.send("direct:alias-verify&
</div>
</div>
<p>The <strong>cxf:</strong> component provides integration with <a shape="rect" href="http://cxf.apache.org">Apache CXF</a> for connecting to JAX-WS services hosted in CXF.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1394792362543 {padding: 0px;}
-div.rbtoc1394792362543 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1394792362543 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1394983114693 {padding: 0px;}
+div.rbtoc1394983114693 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1394983114693 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1394792362543">
+/*]]>*/</style></p><div class="toc-macro rbtoc1394983114693">
<ul class="toc-indentation"><li><a shape="rect" href="#CXF-CXFComponent">CXF Component</a>
<ul class="toc-indentation"><li><a shape="rect" href="#CXF-URIformat">URI format</a></li><li><a shape="rect" href="#CXF-Options">Options</a>
<ul class="toc-indentation"><li><a shape="rect" href="#CXF-Thedescriptionsofthedataformats">The descriptions of the dataformats</a>
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/camel-transport-for-cxf.html
==============================================================================
--- websites/production/camel/content/camel-transport-for-cxf.html (original)
+++ websites/production/camel/content/camel-transport-for-cxf.html Sun Mar 16 15:19:30 2014
@@ -86,24 +86,8 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="CamelTransportforCXF-What'stheCamelTransportforCXF">What's the Camel Transport for CXF</h2>
-
-<p>In CXF you offer or consume a webservice by defining it´s address. The first part of the address specifies the protocol to use. For example address="http://localhost:9000" in an endpoint configuration means your service will be offered using the http protocol on port 9000 of localhost. When you integrate Camel Tranport into CXF you get a new transport "camel". So you can specify address="camel://direct:MyEndpointName" to bind the CXF service address to a camel direct endpoint.</p>
-
-<p>Technically speaking Camel transport for CXF is a component which implements the <a shape="rect" class="external-link" href="http://cwiki.apache.org/CXF20DOC/cxf-architecture.html#CXFArchitecture-Transports">CXF transport API</a> with the Camel core library. This allows you to use camel´s routing engine and integration patterns support smoothly together with your CXF services.</p>
-
-
-<h2 id="CamelTransportforCXF-IntegrateCamelintoCXFtransportlayer">Integrate Camel into CXF transport layer</h2>
-
-<p>To include the Camel Tranport into your CXF bus you use the CamelTransportFactory. You can do this in Java as well as in Spring.</p>
-
-<h3 id="CamelTransportforCXF-SettinguptheCamelTransportinSpring">Setting up the Camel Transport in Spring</h3>
-
-<p>You can use the following snippet in your applicationcontext if you want to configure anything special. If you only want to activate the camel transport you do not have to do anything in your application context. As soon as you include the camel-cxf-transport jar (or camel-cxf.jar if your camel version is less than 2.7.x) in your app cxf will scan the jar and load a CamelTransportFactory for you. </p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-<!-- you don't need to specify the CamelTransportFactory configuration as it is auto load by CXF bus -->
+<div class="wiki-content maincontent"><h2 id="CamelTransportforCXF-What'stheCamelTransportforCXF">What's the Camel Transport for CXF</h2><p>In CXF you offer or consume a webservice by defining it´s address. The first part of the address specifies the protocol to use. For example address="http://localhost:9000" in an endpoint configuration means your service will be offered using the http protocol on port 9000 of localhost. When you integrate Camel Tranport into CXF you get a new transport "camel". So you can specify address="camel://direct:MyEndpointName" to bind the CXF service address to a camel direct endpoint.</p><p>Technically speaking Camel transport for CXF is a component which implements the <a shape="rect" class="external-link" href="http://cwiki.apache.org/CXF20DOC/cxf-architecture.html#CXFArchitecture-Transports">CXF transport API</a> with the Camel core library. This allows you to easily use camel´s routing engine and integration patterns support together with
your CXF services.</p><h2 id="CamelTransportforCXF-IntegrateCamelintoCXFtransportlayer">Integrate Camel into CXF transport layer</h2><p>To include the Camel Tranport into your CXF bus you use the CamelTransportFactory. You can do this in Java as well as in Spring.</p><h3 id="CamelTransportforCXF-SettinguptheCamelTransportinSpring">Setting up the Camel Transport in Spring</h3><p>You can use the following snippet in your applicationcontext if you want to configure anything special. If you only want to activate the camel transport you do not have to do anything in your application context. As soon as you include the camel-cxf-transport jar (or camel-cxf.jar if your camel version is less than 2.7.x) in your app, cxf will scan the jar and load a CamelTransportFactory for you.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[<!-- you don't need to specify the CamelTransportFactory configuration as it is auto load by CXF bus -->
<bean class="org.apache.camel.component.cxf.transport.CamelTransportFactory">
<property name="bus" ref="cxf" />
<property name="camelContext" ref="camelContext" />
@@ -121,14 +105,8 @@
</property>
</bean>
]]></script>
-</div></div>
-
-<h3 id="CamelTransportforCXF-IntegratingtheCamelTransportinaprogrammaticway">Integrating the Camel Transport in a programmatic way</h3>
-
-<p>Camel transport provides a setContext method that you could use to set the Camel context into the transport factory. If you want this factory take effect, you need to register the factory into the CXF bus. Here is a full example for you.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-import org.apache.cxf.Bus;
+</div></div><h3 id="CamelTransportforCXF-IntegratingtheCamelTransportinaprogrammaticway">Integrating the Camel Transport in a programmatic way</h3><p>Camel transport provides a setContext method that you could use to set the Camel context into the transport factory. If you want this factory take effect, you need to register the factory into the CXF bus. Here is a full example for you.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[import org.apache.cxf.Bus;
import org.apache.cxf.BusFactory;
import org.apache.cxf.transport.ConduitInitiatorManager;
import org.apache.cxf.transport.DestinationFactoryManager;
@@ -152,17 +130,8 @@ dfm.registerDestinationFactory(CamelTran
// set or bus as the default bus for cxf
BusFactory.setDefaultBus(bus);
]]></script>
-</div></div>
-
-<h2 id="CamelTransportforCXF-ConfigurethedestinationandconduitwithSpring">Configure the destination and conduit with Spring</h2>
-
-<h3 id="CamelTransportforCXF-Namespace">Namespace</h3>
-
-<p>The elements used to configure an Camel transport endpoint are defined in the namespace <code><a shape="rect" href="http://cxf.apache.org/transports/camel">http://cxf.apache.org/transports/camel</a></code>. It is commonly referred to using the prefix <code>camel</code>. In order to use the Camel transport configuration elements you will need to add the lines shown below to the beans element of your endpoint's configuration file. In addition, you will need to add the configuration elements' namespace to the <code>xsi:schemaLocation</code> attribute.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Adding the Configuration Namespace</b></div><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-<beans ...
+</div></div><h2 id="CamelTransportforCXF-ConfigurethedestinationandconduitwithSpring">Configure the destination and conduit with Spring</h2><h3 id="CamelTransportforCXF-Namespace">Namespace</h3><p>The elements used to configure an Camel transport endpoint are defined in the namespace <code><a shape="rect" href="http://cxf.apache.org/transports/camel">http://cxf.apache.org/transports/camel</a></code>. It is commonly referred to using the prefix <code>camel</code>. In order to use the Camel transport configuration elements, you will need to add the lines shown below to the beans element of your endpoint's configuration file. In addition, you will need to add the configuration elements' namespace to the <code>xsi:schemaLocation</code> attribute.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Adding the Configuration Namespace</b></div><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[<beans ...
xmlns:camel="http://cxf.apache.org/transports/camel
...
xsi:schemaLocation="...
@@ -170,16 +139,8 @@ BusFactory.setDefaultBus(bus);
http://cxf.apache.org/transports/camel.xsd
...>
]]></script>
-</div></div>
-
-<h3 id="CamelTransportforCXF-Thedestinationelement">The <code>destination</code> element</h3>
-
-<p>You configure an Camel transport server endpoint using the <code>camel:destination</code> element and its children. The <code>camel:destination</code> element takes a single attribute, <code>name</code>, the specifies the WSDL port element that corresponds to the endpoint. The value for the <code>name</code> attribute takes the form <em>portQName</em><code>.camel-destination</code>. The example below shows the <code>camel:destination</code> element that would be used to add configuration for an endpoint that was specified by the WSDL fragment <code><port binding="widgetSOAPBinding" name="widgetSOAPPort></code> if the endpoint's target namespace was <code><a shape="rect" class="external-link" href="http://widgets.widgetvendor.net" rel="nofollow">http://widgets.widgetvendor.net</a></code>.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>camel:destination Element</b></div><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-
-...
+</div></div><h3 id="CamelTransportforCXF-Thedestinationelement">The <code>destination</code> element</h3><p>You configure an Camel transport server endpoint using the <code>camel:destination</code> element and its children. The <code>camel:destination</code> element takes a single attribute, <code>name</code>, the specifies the WSDL port element that corresponds to the endpoint. The value for the <code>name</code> attribute takes the form <em>portQName</em><code>.camel-destination</code>. The example below shows the <code>camel:destination</code> element that would be used to add configuration for an endpoint that was specified by the WSDL fragment <code><port binding="widgetSOAPBinding" name="widgetSOAPPort></code> if the endpoint's target namespace was <code><a shape="rect" class="external-link" href="http://widgets.widgetvendor.net" rel="nofollow">http://widgets.widgetvendor.net</a></code>.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader pan
elHeader pdl" style="border-bottom-width: 1px;"><b>camel:destination Element</b></div><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[...
<camel:destination name="{http://widgets/widgetvendor.net}widgetSOAPPort.http-destination>
<camelContext id="context" xmlns="http://activemq.apache.org/camel/schema/spring">
<route>
@@ -194,20 +155,8 @@ BusFactory.setDefaultBus(bus);
...
]]></script>
-</div></div>
-
-<p>The <code>camel:destination</code> element for Spring has a number of child elements that specify configuration information. They are described below.</p>
-
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Element</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>camel-spring:camelContext</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>You can specify the camel context in the camel destination</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>camel:camelContextRef</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The camel context id which you want inject into the camel destination</p></td></tr></tbody></table></div>
-
-
-
-<h3 id="CamelTransportforCXF-Theconduitelement">The <code>conduit</code> element</h3>
-
-<p>You configure an Camel transport client using the <code>camel:conduit</code> element and its children. The <code>camel:conduit</code> element takes a single attribute, <code>name</code>, that specifies the WSDL port element that corresponds to the endpoint. The value for the <code>name</code> attribute takes the form <em>portQName</em><code>.camel-conduit</code>. For example, the code below shows the <code>camel:conduit</code> element that would be used to add configuration for an endpoint that was specified by the WSDL fragment <code><port binding="widgetSOAPBinding" name="widgetSOAPPort></code> if the endpoint's target namespace was <code><a shape="rect" class="external-link" href="http://widgets.widgetvendor.net" rel="nofollow">http://widgets.widgetvendor.net</a></code>.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>http-conf:conduit Element</b></div><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-...
+</div></div><p>The <code>camel:destination</code> element for Spring has a number of child elements that specify configuration information. They are described below.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Element</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>camel-spring:camelContext</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>You can specify the camel context in the camel destination</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>camel:camelContextRef</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The camel context id which you want inject into the camel destination</p></td></tr></tbody></table></div><h3 id="CamelTransportforCXF-Theconduitelement">The <code>conduit</code> element</h3><p>You configure a Camel transport client using t
he <code>camel:conduit</code> element and its children. The <code>camel:conduit</code> element takes a single attribute, <code>name</code>, that specifies the WSDL port element that corresponds to the endpoint. The value for the <code>name</code> attribute takes the form <em>portQName</em><code>.camel-conduit</code>. For example, the code below shows the <code>camel:conduit</code> element that would be used to add configuration for an endpoint that was specified by the WSDL fragment <code><port binding="widgetSOAPBinding" name="widgetSOAPPort></code> if the endpoint's target namespace was <code><a shape="rect" class="external-link" href="http://widgets.widgetvendor.net" rel="nofollow">http://widgets.widgetvendor.net</a></code>.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>http-conf:conduit Element</b></div><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[...
<camelContext id="conduit_context" xmlns="http://activemq.apache.org/camel/schema/spring">
<route>
<from uri="direct:EndpointA" />
@@ -229,21 +178,8 @@ BusFactory.setDefaultBus(bus);
</camel:conduit>
...
]]></script>
-</div></div>
-
-<p>The <code>camel:conduit</code> element has a number of child elements that specify configuration information. They are described below.</p>
-
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Element</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>camel-spring:camelContext</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>You can specify the camel context in the camel conduit</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>camel:camelContextRef</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The camel context id which you want inject into the camel conduit</p></td></tr></tbody></table></div>
-
-
-<h2 id="CamelTransportforCXF-ConfigurethedestinationandconduitwithBlueprint">Configure the destination and conduit with Blueprint</h2>
-
-<p>From <strong>Camel 2.11.x</strong>, Camel Transport supports to be configured with Blueprint</p>
-
-<p>If you are using blueprint, you should use the the namespace <code><a shape="rect" href="http://cxf.apache.org/transports/camel/blueprint">http://cxf.apache.org/transports/camel/blueprint</a></code> and import the schema like the blow.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Adding the Configuration Namespace for blueprint</b></div><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-<beans ...
+</div></div><p>The <code>camel:conduit</code> element has a number of child elements that specify configuration information. They are described below.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Element</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>camel-spring:camelContext</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>You can specify the camel context in the camel conduit</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>camel:camelContextRef</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The camel context id which you want inject into the camel conduit</p></td></tr></tbody></table></div><h2 id="CamelTransportforCXF-ConfigurethedestinationandconduitwithBlueprint">Configure the destination and conduit with Blueprint</h2><p>From <strong>Camel 2
.11.x</strong>, Camel Transport supports to be configured with Blueprint</p><p>If you are using blueprint, you should use the the namespace <code><a shape="rect" href="http://cxf.apache.org/transports/camel/blueprint">http://cxf.apache.org/transports/camel/blueprint</a></code> and import the schema like the blow.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Adding the Configuration Namespace for blueprint</b></div><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[<beans ...
xmlns:camel="http://cxf.apache.org/transports/camel/blueprint"
...
xsi:schemaLocation="...
@@ -251,20 +187,11 @@ BusFactory.setDefaultBus(bus);
http://cxf.apache.org/schmemas/blueprint/camel.xsd
...>
]]></script>
-</div></div>
-
-<p>In blueprint <code>camel:conduit</code> <code>camel:destination</code> only has one camelContextId attribute, they doesn't support to specify the camel context in the camel destination.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
- <camel:conduit id="*.camel-conduit" camelContextId="camel1" />
+</div></div><p>In blueprint <code>camel:conduit</code> <code>camel:destination</code> only has one camelContextId attribute, they doesn't support to specify the camel context in the camel destination.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ <camel:conduit id="*.camel-conduit" camelContextId="camel1" />
<camel:destination id="*.camel-destination" camelContextId="camel1" />
]]></script>
-</div></div>
-
-<h2 id="CamelTransportforCXF-ExampleUsingCamelasaloadbalancerforCXF">Example Using Camel as a load balancer for CXF</h2>
-
-<p>This example show how to use the camel load balance feature in CXF, and you need load the configuration file in CXF and publish the endpoints on the address "camel://direct:EndpointA" and "camel://direct:EndpointB"</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h2 id="CamelTransportforCXF-ExampleUsingCamelasaloadbalancerforCXF">Example Using Camel as a load balancer for CXF</h2><p>This example shows how to use the camel load balancing feature in CXF. You need to load the configuration file in CXF and publish the endpoints on the address "camel://direct:EndpointA" and "camel://direct:EndpointB"</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -300,11 +227,7 @@ BusFactory.setDefaultBus(bus);
</beans>
]]></script>
-</div></div>
-
-<h2 id="CamelTransportforCXF-CompleteHowtoandExampleforattachingCameltoCXF">Complete Howto and Example for attaching Camel to CXF</h2>
-
-<p><a shape="rect" href="better-jms-transport-for-cxf-webservice-using-apache-camel.html">Better JMS Transport for CXF Webservice using Apache Camel</a> </p></div>
+</div></div><h2 id="CamelTransportforCXF-CompleteHowtoandExampleforattachingCameltoCXF">Complete Howto and Example for attaching Camel to CXF</h2><p><a shape="rect" href="better-jms-transport-for-cxf-webservice-using-apache-camel.html">Better JMS Transport for CXF Webservice using Apache Camel</a> </p></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/cxf-example.html
==============================================================================
--- websites/production/camel/content/cxf-example.html (original)
+++ websites/production/camel/content/cxf-example.html Sun Mar 16 15:19:30 2014
@@ -86,26 +86,11 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h1 id="CXFExample-CXFExample">CXF Example</h1>
-
-<h2 id="CXFExample-CXFexampleforroutingmessageswithdifferenttransports">CXF example for routing messages with different transports</h2>
-
-<p>The <a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/camel/trunk/examples/camel-example-cxf/src/main/java/org/apache/camel/example/cxf/httptojms/CamelCxfExample.java?view=markup">Camel CXF example</a> is a demo of the camel-cxf component to show how to route messages between CXF endpoints, with one endpoint consuming a SOAP over HTTP request while the other providing a SOAP over JMS request for the actual CXF Service endpoint. The Camel router just routs the SOAP over HTTP CXF client request to the SOAP over JMS CXF service.</p>
-
-<p>To run the example see instructions in the <code>README.txt</code> file in the <code>camel-example-cxf</code> directory under <code>examples</code>.</p>
-
-
-<p>We start with creating a <a shape="rect" href="camelcontext.html">CamelContext</a> - which is a container for <a shape="rect" href="components.html">Components</a>, <a shape="rect" href="routes.html">Routes</a> etc:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="wiki-content maincontent"><h1 id="CXFExample-CXFExample">CXF Example</h1><h2 id="CXFExample-CXFexampleforroutingmessageswithdifferenttransports">CXF example for routing messages with different transports</h2><p>The <a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/camel/trunk/examples/camel-example-cxf/src/main/java/org/apache/camel/example/cxf/httptojms/CamelCxfExample.java?view=markup">Camel CXF example</a> is a demo of the camel-cxf component to show how to route messages between CXF endpoints, with one endpoint consuming a SOAP over HTTP request while the other providing a SOAP over JMS request for the actual CXF Service endpoint. The Camel router just routs the SOAP over HTTP CXF client request to the SOAP over JMS CXF service.</p><p>To run the example see instructions in the <code>README.txt</code> file in the <code>camel-example-cxf</code> directory under <code>examples</code>.</p><p>We start with creating a <a shape="rect" href="camelcontex
t.html">CamelContext</a> - which is a container for <a shape="rect" href="components.html">Components</a>, <a shape="rect" href="routes.html">Routes</a> etc:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
CamelContext context = new DefaultCamelContext();
]]></script>
-</div></div>
-
-<p>Here is code for starting the JMS broker and the CXF server: </p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Here is code for starting the JMS broker and the CXF server:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
JmsBroker broker = new JmsBroker();
Server server = new Server();
@@ -113,11 +98,7 @@ try {
broker.start();
server.start();
]]></script>
-</div></div>
-
-<p>Now we setup the router for the two endpoint URIs which we mentioned before, ROUTER_ENDPOINT_URI is the endpoint for consuming the request of SOAP over HTTP, SERVICE_ENDPOINT_URI is the endpoint for providing the request for the SOAP over JMS service.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Now we setup the router for the two endpoint URIs which we mentioned before, ROUTER_ENDPOINT_URI is the endpoint for consuming the request of SOAP over HTTP, SERVICE_ENDPOINT_URI is the endpoint for providing the request for the SOAP over JMS service.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
context.addRoutes(new RouteBuilder() {
public void configure() {
@@ -127,24 +108,12 @@ context.addRoutes(new RouteBuilder() {
}
});
]]></script>
-</div></div>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
context.start();
Client client = new Client(address + "?wsdl");
]]></script>
-</div></div>
-
-<p>Then we start up the camel context and create the CXF client to kick off the request.</p>
-
-<h2 id="CXFExample-CXFexampleforusingCameltransport">CXF example for using Camel transport</h2>
-
-<p>Since Camel has lots of components and is a great mediation rule engine, we can leverage these Camel features in CXF by using the Camel transport. Here is an example to show how to use the Camel transport in CXF.</p>
-
-<p>In this example, we setup a load balance Camel context in the Camel destination. </p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Then we start up the camel context and create the CXF client to kick off the request.</p><h2 id="CXFExample-CXFexampleforusingCameltransport">CXF example for using Camel transport</h2><p>Since Camel has lots of components and is a great mediation rule engine, we can leverage these Camel features in CXF by using the Camel transport. Here is an example to show how to use the Camel transport in CXF.</p><p>In this example, we setup a load balancing Camel context in the Camel destination.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -180,22 +149,14 @@ Client client = new Client(address + &qu
</beans>
]]></script>
-</div></div>
-
-<p>When CXF loads this configuration, it will publish the CXF endpoint to the Camel endpoint that is found in the Camel context.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>When CXF loads this configuration, it will publish the CXF endpoint to the Camel endpoint that is found in the Camel context.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
SpringBusFactory bf = new SpringBusFactory();
BusFactory.setDefaultBus(null);
Bus bus = bf.createBus("/org/apache/camel/example/camel/transport/CamelDestination.xml");
BusFactory.setDefaultBus(bus);
]]></script>
-</div></div>
-
-<p>The code below shows how to publish the endpoint to different Camel context endpoints. You can specify the Camel endpoint URI as the endpoint address parameter.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>The code below shows how to publish the endpoint to different Camel context endpoints. You can specify the Camel endpoint URI as the endpoint address parameter.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
GreeterImpl implementor = new GreeterImpl();
implementor.setSuffix("EndpointA");
@@ -207,15 +168,7 @@ implementor.setSuffix("EndpointB&qu
address = "camel://direct:EndpointB";
endpointB = Endpoint.publish(address, implementor);
]]></script>
-</div></div>
-
-<h2 id="CXFExample-CXFexampleforusingtheWebServiceProviderAPI">CXF example for using the WebServiceProvider API</h2>
-
-<p>JAX-WS provides the WebServiceProvider API to meet the requirements of XML-level message handling. This example shows how to route a SOAP Message from a WebServiceProvider implementation to bean endpoint in the Camel context. Basically, we still pass the WebServiceProvider implementor as SEI, and the CxfConsumer will pass the SOAP Message in a list of parameters to the Camel router for further processing.</p>
-
-<p>First, let's have a look at the Camel context's configuration. Here we start a CxfConsumer to listen to the address and pass SOAP messages to the test bean.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h2 id="CXFExample-CXFexampleforusingtheWebServiceProviderAPI">CXF example for using the WebServiceProvider API</h2><p>JAX-WS provides the WebServiceProvider API to meet the requirements of XML-level message handling. This example shows how to route a SOAP Message from a WebServiceProvider implementation to bean endpoint in the Camel context. Basically, we still pass the WebServiceProvider implementor as SEI, and the CxfConsumer will pass the SOAP Message in a list of parameters to the Camel router for further processing.</p><p>First, let's have a look at the Camel context's configuration. Here we start a CxfConsumer to listen to the address and pass SOAP messages to the test bean.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
<!--
@@ -242,20 +195,12 @@ please replace the cxf-extension-http-je
</camelContext>
]]></script>
-</div></div>
-
-<p>Below is the WebServiceProvider implementor's annotation. In this code, we just want to handle SOAPMessages in the Message mode:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Below is the WebServiceProvider implementor's annotation. In this code, we just want to handle SOAPMessages in the Message mode:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
@WebServiceProvider()
@ServiceMode(Mode.MESSAGE)
]]></script>
-</div></div>
-
-<p>Since the CXF-Camel component will replace the CXF invoker to call the processor when starting a CXF endpoint, the CXF-Camel consumer will never call the provider implementor's invoke method here.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Since the CXF-Camel component will replace the CXF invoker to call the processor when starting a CXF endpoint, the CXF-Camel consumer will never call the provider implementor's invoke method here.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
public class GreeterProvider implements Provider<SOAPMessage> {
@@ -267,11 +212,7 @@ public class GreeterProvider implements
}
]]></script>
-</div></div>
-
-<p>Now we can implement the bean for handling the invocation of the SOAP message:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>Now we can implement the bean for handling the invocation of the SOAP message:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
public class TesterBean {