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/09/11 15:18:58 UTC
svn commit: r921867 - in /websites/production/camel/content:
book-in-one-page.html book-pattern-appendix.html cache/main.pageCache
messaging-gateway.html
Author: buildbot
Date: Thu Sep 11 13:18:57 2014
New Revision: 921867
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/book-in-one-page.html
websites/production/camel/content/book-pattern-appendix.html
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/messaging-gateway.html
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 Thu Sep 11 13:18:57 2014
@@ -4163,11 +4163,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.rbtoc1410430690103 {padding: 0px;}
-div.rbtoc1410430690103 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1410430690103 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1410441482732 {padding: 0px;}
+div.rbtoc1410441482732 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1410441482732 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1410430690103">
+/*]]>*/</style></p><div class="toc-macro rbtoc1410441482732">
<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>
@@ -6353,11 +6353,11 @@ So we completed the last piece in the pi
<style type="text/css">/*<![CDATA[*/
-div.rbtoc1410430690241 {padding: 0px;}
-div.rbtoc1410430690241 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1410430690241 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1410441483299 {padding: 0px;}
+div.rbtoc1410441483299 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1410441483299 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="toc-macro rbtoc1410430690241">
+/*]]>*/</style><div class="toc-macro rbtoc1410441483299">
<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>
@@ -18193,23 +18193,15 @@ from("direct:mixed2")
</div></div><p>Notice how we have configured the <code>onException</code> in the 2nd route to indicate in case of any exceptions we should handle it and just rollback this transaction. This is done using the <code>markRollbackOnlyLast</code> which tells Camel to only do it for the current transaction and not globally.</p><h4 id="BookInOnePage-SeeAlso.17">See Also</h4><ul><li><a shape="rect" href="error-handling-in-camel.html">Error handling in Camel</a></li><li><a shape="rect" href="transactionerrorhandler.html">TransactionErrorHandler</a></li><li><a shape="rect" href="error-handler.html">Error Handler</a></li><li><a shape="rect" href="jms.html">JMS</a></li></ul><p></p><h4 id="BookInOnePage-UsingThisPattern.43">Using This Pattern</h4>
<p>If you would like to use this EIP Pattern then please read the <a shape="rect" href="getting-started.html">Getting Started</a>, you may also find the <a shape="rect" href="architecture.html">Architecture</a> useful particularly the description of <a shape="rect" href="endpoint.html">Endpoint</a> and <a shape="rect" href="uris.html">URIs</a>. Then you could try out some of the <a shape="rect" href="examples.html">Examples</a> first before trying this pattern out.</p>
-<h3 id="BookInOnePage-MessagingGateway">Messaging Gateway</h3>
-
-<p>Camel has several endpoint components that support the <a shape="rect" class="external-link" href="http://www.enterpriseintegrationpatterns.com/MessagingGateway.html" rel="nofollow">Messaging Gateway</a> from the <a shape="rect" href="enterprise-integration-patterns.html">EIP patterns</a>.</p>
-
-<p><img class="confluence-embedded-image confluence-external-resource" src="http://www.enterpriseintegrationpatterns.com/img/MessagingGatewaySolution.gif" data-image-src="http://www.enterpriseintegrationpatterns.com/img/MessagingGatewaySolution.gif"></p>
-
-<p>Components like <a shape="rect" href="bean.html">Bean</a> and <a shape="rect" href="cxf.html">CXF</a> provide a a way to bind a Java interface to the message exchange.</p>
-
-<p>However you may want to read the <a shape="rect" href="using-camelproxy.html">Using CamelProxy</a> documentation as a true <a shape="rect" href="messaging-gateway.html">Messaging Gateway</a> EIP solution.<br clear="none">
-Another approach is to use <code>@Produce</code> which you can read about in <a shape="rect" href="pojo-producing.html">POJO Producing</a> which also can be used as a <a shape="rect" href="messaging-gateway.html">Messaging Gateway</a> EIP solution.</p>
-
-<h4 id="BookInOnePage-SeeAlso.18">See Also</h4>
-
-<ul><li><a shape="rect" href="bean.html">Bean</a></li><li><a shape="rect" href="cxf.html">CXF</a></li><li><a shape="rect" href="using-camelproxy.html">Using CamelProxy</a></li><li><a shape="rect" href="pojo-producing.html">POJO Producing</a></li><li><a shape="rect" href="spring-remoting.html">Spring Remoting</a></li></ul>
-
-
-<h4 id="BookInOnePage-UsingThisPattern.44">Using This Pattern</h4>
+<h3 id="BookInOnePage-MessagingGateway">Messaging Gateway</h3><p>Camel has several endpoint components that support the <a shape="rect" class="external-link" href="http://www.enterpriseintegrationpatterns.com/MessagingGateway.html" rel="nofollow">Messaging Gateway</a> from the <a shape="rect" href="enterprise-integration-patterns.html">EIP patterns</a>.</p><p><img class="confluence-embedded-image confluence-external-resource" src="http://www.enterpriseintegrationpatterns.com/img/MessagingGatewaySolution.gif" data-image-src="http://www.enterpriseintegrationpatterns.com/img/MessagingGatewaySolution.gif"></p><p>Components like <a shape="rect" href="bean.html">Bean</a> and <a shape="rect" href="cxf.html">CXF</a> provide a a way to bind a Java interface to the message exchange.</p><p>However you may want to read the <a shape="rect" href="using-camelproxy.html">Using CamelProxy</a> documentation as a true <a shape="rect" href="messaging-gateway.html">Messaging Gateway</a> EIP solution.<br
clear="none"> Another approach is to use <code>@Produce</code> which you can read about in <a shape="rect" href="pojo-producing.html">POJO Producing</a> which also can be used as a <a shape="rect" href="messaging-gateway.html">Messaging Gateway</a> EIP solution.</p><p> </p><h4 id="BookInOnePage-Example.16">Example</h4><p>The following example how the <a shape="rect" href="cxf.html">CXF</a> and <a shape="rect" href="bean.html">Bean</a> components can be used to abstract the developer from the underlying messaging system API</p><p><strong><br clear="none"></strong></p><p><strong>Using the <a shape="rect" href="fluent-builders.html">Fluent Builders</a></strong></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[from("cxf:bean:soapMessageEndpoint")
+ .to("bean:testBean?method=processSOAP");]]></script>
+</div></div><p> </p><p><strong><strong>Using the <a shape="rect" href="spring-xml-extensions.html">Spring XML Extensions</a></strong></strong></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[<route>
+ <from uri="cxf:bean:soapMessageEndpoint"/>
+ <to uri="bean:testBean?method=processSOAP"/>
+</route>]]></script>
+</div></div><h4 id="BookInOnePage-SeeAlso.18">See Also</h4><ul><li><a shape="rect" href="bean.html">Bean</a></li><li><a shape="rect" href="cxf.html">CXF</a></li><li><a shape="rect" href="using-camelproxy.html">Using CamelProxy</a></li><li><a shape="rect" href="pojo-producing.html">POJO Producing</a></li><li><a shape="rect" href="spring-remoting.html">Spring Remoting</a></li></ul><p></p><h4 id="BookInOnePage-UsingThisPattern.44">Using This Pattern</h4>
<p>If you would like to use this EIP Pattern then please read the <a shape="rect" href="getting-started.html">Getting Started</a>, you may also find the <a shape="rect" href="architecture.html">Architecture</a> useful particularly the description of <a shape="rect" href="endpoint.html">Endpoint</a> and <a shape="rect" href="uris.html">URIs</a>. Then you could try out some of the <a shape="rect" href="examples.html">Examples</a> first before trying this pattern out.</p>
<h3 id="BookInOnePage-ServiceActivator">Service Activator</h3>
@@ -18258,7 +18250,7 @@ from("direct:invokeMyService")
<p><img class="confluence-embedded-image confluence-external-resource" src="http://www.enterpriseintegrationpatterns.com/img/Detour.gif" data-image-src="http://www.enterpriseintegrationpatterns.com/img/Detour.gif"></p>
-<h4 id="BookInOnePage-Example.16">Example</h4>
+<h4 id="BookInOnePage-Example.17">Example</h4>
<p>In this example we essentially have a route like <code>from("direct:start").to("mock:result")</code> with a conditional detour to the <code>mock:detour</code> endpoint in the middle of the route..</p>
@@ -19569,7 +19561,7 @@ camelContextId:localEndpointName[?option
<p>You can append query options to the URI in the following format, <code>?option=value&option=value&...</code></p>
-<h3 id="BookInOnePage-Example.17">Example</h3>
+<h3 id="BookInOnePage-Example.18">Example</h3>
<p>In this example we'll create a black box context, then we'll use it from another CamelContext.</p>
@@ -19916,11 +19908,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.rbtoc1410430692670 {padding: 0px;}
-div.rbtoc1410430692670 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1410430692670 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1410441487293 {padding: 0px;}
+div.rbtoc1410441487293 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1410441487293 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1410430692670">
+/*]]>*/</style></p><div class="toc-macro rbtoc1410441487293">
<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>
@@ -20858,7 +20850,7 @@ dataset:name[?options]
]]></script>
</div></div>
-<h3 id="BookInOnePage-Example.18">Example</h3>
+<h3 id="BookInOnePage-Example.19">Example</h3>
<p>For example, to test that a set of messages are sent to a queue and then consumed from the queue without losing any messages:</p>
@@ -24525,7 +24517,7 @@ We store big input streams (by default,
</div>
<p> </p><h4 id="BookInOnePage-Consumer.1">Consumer</h4><p>The consumer will connect to JCR periodically and return a List<<a shape="rect" class="external-link" href="http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/javax/jcr/observation/Event.html" rel="nofollow">javax.jcr.observation.Event</a>> in the message body.</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> Default Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>eventTypes</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>0</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> A combination of one or more event types encoded as a bit mask value such as javax.jcr.observation.Event.NODE_ADDED, javax.jcr.observation.Event.NODE_REMOVED, etc. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>deep</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> When it is true, events whose associated parent node is at current path or within its subgrap
h are received. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>uuids</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Only events whose associated parent node has one of the identifiers in the comma separated uuid list will be received.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>nodeTypeNames</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Only events whose associated parent node has one of the node types (or a subtype of one of the node types) in this list will be received. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>noLocal</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> If <code>noLocal</
code> is <code>true</code>, then events generated by the session through which the listener was registered are ignored. Otherwise, they are not ignored. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>sessionLiveCheckInterval</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>60000</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Interval in milliseconds to wait before each session live checking. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>sessionLiveCheckIntervalOnStart</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>3000</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Interval in milliseconds to wait before the first session live checking. </p></td></tr></tbody></table></div>
-</div><h3 id="BookInOnePage-Example.19">Example</h3><p>The snippet below creates a node named <code>node</code> under the <code>/home/test</code> node in the content repository. One additional property is added to the node as well: <code>my.contents.property</code> which will contain the body of the message being sent.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div><h3 id="BookInOnePage-Example.20">Example</h3><p>The snippet below creates a node named <code>node</code> under the <code>/home/test</code> node in the content repository. One additional property is added to the node as well: <code>my.contents.property</code> which will contain the body of the message being sent.</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[from("direct:a").setHeader(JcrConstants.JCR_NODE_NAME, constant("node"))
.setHeader("my.contents.property", body())
.to("jcr://user:pass@repository/home/test");]]></script>
@@ -25019,7 +25011,7 @@ rnc:someLocalOrRemoteResource
<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Option </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>useDom</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies whether DOMSource/DOMResult or SaxSource/SaxResult should be used by the validator. </p></td></tr></tbody></table></div>
-<h3 id="BookInOnePage-Example.20">Example</h3>
+<h3 id="BookInOnePage-Example.21">Example</h3>
<p>The following <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/camel/trunk/components/camel-jing/src/test/resources/org/apache/camel/component/validator/jing/rnc-context.xml">example</a> shows how to configure a route from the endpoint <strong>direct:start</strong> which then goes to one of two endpoints, either <strong>mock:valid</strong> or <strong>mock:invalid</strong> based on whether or not the XML matches the given <a shape="rect" class="external-link" href="http://relaxng.org/compact-tutorial-20030326.html" rel="nofollow">RelaxNG Compact Syntax</a> schema (which is supplied on the classpath).</p>
@@ -25395,7 +25387,7 @@ ObjectName(String domain, Hashtable<S
<p>The Hashtable is constructed by extracting properties that start with "key." The properties will have the "key." prefixed stripped prior to building the Hashtable. This allows the URI to contain a variable number of properties to identify the mbean.</p>
-<h4 id="BookInOnePage-Example.21">Example</h4>
+<h4 id="BookInOnePage-Example.22">Example</h4>
<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[
from("jmx:platform?objectDomain=jmxExample&key.name=simpleBean").
@@ -25424,7 +25416,7 @@ monitor.start();
<p>The 2.8 version introduces a new type of consumer that automatically creates and registers a monitor bean for the specified objectName and attribute. Additional endpoint attributes allow the user to specify the attribute to monitor, type of monitor to create, and any other required properties. The code snippet above is condensed into a set of endpoint properties. The consumer uses these properties to create the CounterMonitor, register it, and then subscribe to its changes. All of the JMX monitor types are supported.</p>
-<h4 id="BookInOnePage-Example.22">Example</h4>
+<h4 id="BookInOnePage-Example.23">Example</h4>
<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[
from("jmx:platform?objectDomain=myDomain&objectName=simpleBean&" +
@@ -25488,7 +25480,7 @@ public class MultiSteps {
<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[from("jpa://org.apache.camel.examples.MultiSteps?consumer.nativeQuery=select * from MultiSteps where step = 1")
.to("bean:myBusinessLogic");
]]></script>
-</div></div><p>If you use the native query option, you will receive an object array in the message body.</p><h3 id="BookInOnePage-Example.23">Example</h3><p>See <a shape="rect" href="tracer-example.html">Tracer Example</a> for an example using <a shape="rect" href="jpa.html">JPA</a> to store traced messages into a database.</p><h3 id="BookInOnePage-UsingtheJPAbasedidempotentrepository">Using the JPA based idempotent repository</h3><p>In this section we will use the JPA based idempotent repository.</p><p>First we need to setup a <code>persistence-unit</code> in the persistence.xml file:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>If you use the native query option, you will receive an object array in the message body.</p><h3 id="BookInOnePage-Example.24">Example</h3><p>See <a shape="rect" href="tracer-example.html">Tracer Example</a> for an example using <a shape="rect" href="jpa.html">JPA</a> to store traced messages into a database.</p><h3 id="BookInOnePage-UsingtheJPAbasedidempotentrepository">Using the JPA based idempotent repository</h3><p>In this section we will use the JPA based idempotent repository.</p><p>First we need to setup a <code>persistence-unit</code> in the persistence.xml file:</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[
<persistence-unit name="idempotentDb" transaction-type="RESOURCE_LOCAL">
<class>org.apache.camel.processor.idempotent.jpa.MessageProcessed</class>
@@ -25618,7 +25610,7 @@ jt400://user:password@system/QSYS.LIB/LI
<p>This endpoint expects the input to be either a String array or byte[] array (depending on format) and handles all the CCSID handling through the native jt400 library mechanisms. A parameter can be <em>omitted</em> by passing null as the value in its position (the remote program has to support it). After the program execution the endpoint returns either a String array or byte[] array with the values as they were returned by the program (the input only parameters will contain the same data as the beginning of the invocation)<br clear="none">
This endpoint does not implement a provider endpoint!</p>
-<h3 id="BookInOnePage-Example.24">Example</h3>
+<h3 id="BookInOnePage-Example.25">Example</h3>
<p>In the snippet below, the data for an exchange sent to the <code>direct:george</code> endpoint will be put in the data queue <code>PENNYLANE</code> in library <code>BEATLES</code> on a system named <code>LIVERPOOL</code>. <br clear="none" class="atl-forced-newline">
Another user connects to the same data queue to receive the information from the data queue and forward it to the <code>mock:ringo</code> endpoint.</p>
<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
@@ -27259,7 +27251,7 @@ msv:http://acme.com/cheese.rng
<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Option </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>useDom</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Whether DOMSource/DOMResult or SaxSource/SaxResult should be used by the validator. <strong>Note:</strong> DOM must be used by the <a shape="rect" href="msv.html">MSV</a> component. </p></td></tr></tbody></table></div>
</div>
-<h3 id="BookInOnePage-Example.25">Example</h3>
+<h3 id="BookInOnePage-Example.26">Example</h3>
<p>The following <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/camel/trunk/components/camel-msv/src/test/resources/org/apache/camel/component/validator/msv/camelContext.xml">example</a> shows how to configure a route from endpoint <strong>direct:start</strong> which then goes to one of two endpoints, either <strong>mock:valid</strong> or <strong>mock:invalid</strong> based on whether or not the XML matches the given <a shape="rect" class="external-link" href="http://relaxng.org/" rel="nofollow">RelaxNG XML Schema</a> (which is supplied on the classpath).</p>
@@ -28382,7 +28374,7 @@ TargetCompID=YOUR_TARGET
.withField(ExecTransType.FIELD, Integer.toString(ExecTransType.STATUS))
.withField(OrderID.FIELD, request.getString(OrderID.FIELD)));
]]></script>
-</div></div><h4 id="BookInOnePage-Example.26">Example</h4><p>The source code contains an example called <code>RequestReplyExample</code> that demonstrates the InOut exchanges<br clear="none"> for a consumer and producer. This example creates a simple HTTP server endpoint that accepts order<br clear="none"> status requests. The HTTP request is converted to a FIX OrderStatusRequestMessage, is augmented with a<br clear="none"> correlation criteria, and is then routed to a quickfix endpoint. The response is then converted to a<br clear="none"> JSON-formatted string and sent back to the HTTP server endpoint to be provided as the web response.</p><p>The Spring configuration have changed from Camel 2.9 onwards. See further below for example.</p><h3 id="BookInOnePage-SpringConfiguration">Spring Configuration</h3><p><strong>Camel 2.6 - 2.8.x</strong></p><p>The QuickFIX/J component includes a Spring <code>FactoryBean</code> for configuring the session settings within a Spring context. A type
converter for QuickFIX/J session ID strings is also included. The following example shows a simple configuration of an acceptor and initiator session with default settings for both sessions.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h4 id="BookInOnePage-Example.27">Example</h4><p>The source code contains an example called <code>RequestReplyExample</code> that demonstrates the InOut exchanges<br clear="none"> for a consumer and producer. This example creates a simple HTTP server endpoint that accepts order<br clear="none"> status requests. The HTTP request is converted to a FIX OrderStatusRequestMessage, is augmented with a<br clear="none"> correlation criteria, and is then routed to a quickfix endpoint. The response is then converted to a<br clear="none"> JSON-formatted string and sent back to the HTTP server endpoint to be provided as the web response.</p><p>The Spring configuration have changed from Camel 2.9 onwards. See further below for example.</p><h3 id="BookInOnePage-SpringConfiguration">Spring Configuration</h3><p><strong>Camel 2.6 - 2.8.x</strong></p><p>The QuickFIX/J component includes a Spring <code>FactoryBean</code> for configuring the session settings within a Spring context. A type
converter for QuickFIX/J session ID strings is also included. The following example shows a simple configuration of an acceptor and initiator session with default settings for both sessions.</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[
<!-- camel route -->
<camelContext id="quickfixjContext" xmlns="http://camel.apache.org/schema/spring">
@@ -31498,7 +31490,7 @@ test:expectedMessagesEndpointUri
</div>
-<h3 id="BookInOnePage-Example.27">Example</h3>
+<h3 id="BookInOnePage-Example.28">Example</h3>
<p>For example, you could write a test case as follows:</p>
@@ -31662,7 +31654,7 @@ validator:someLocalOrRemoteResource
<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Option </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>resourceResolver</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.9:</strong> Reference to a <code>org.w3c.dom.ls.LSResourceResolver</code> in the <a shape="rect" href="registry.html">Registry</a>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>useDom</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>false</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Whether <code>DOMSource</code>/<code>DOMResult</code> or <code>SaxSource</code>/<code>SaxResult</code>
should be used by the validator. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>useSharedSchema</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.3:</strong> Whether the <code>Schema</code> instance should be shared or not. This option is introduced to work around a <a shape="rect" class="external-link" href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6773084" rel="nofollow">JDK 1.6.x bug</a>. Xerces should not have this issue. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>failOnNullBody</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.9.5/2.10.3:</strong> Whether to fail if no body exists. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>headerName</code> </p
></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>null</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> To validate against a header instead of the message body. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>failOnNullHeader</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.11:</strong> Whether to fail if no header exists when validating against a header. </p></td></tr></tbody></table></div>
</div>
-<h3 id="BookInOnePage-Example.28">Example</h3>
+<h3 id="BookInOnePage-Example.29">Example</h3>
<p>The following <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/camel/trunk/components/camel-spring/src/test/resources/org/apache/camel/component/validator/camelContext.xml">example</a> shows how to configure a route from endpoint <strong>direct:start</strong> which then goes to one of two endpoints, either <strong>mock:valid</strong> or <strong>mock:invalid</strong> based on whether or not the XML matches the given schema (which is supplied on the classpath).</p>
Modified: websites/production/camel/content/book-pattern-appendix.html
==============================================================================
--- websites/production/camel/content/book-pattern-appendix.html (original)
+++ websites/production/camel/content/book-pattern-appendix.html Thu Sep 11 13:18:57 2014
@@ -4854,23 +4854,15 @@ from("direct:mixed2")
</div></div><p>Notice how we have configured the <code>onException</code> in the 2nd route to indicate in case of any exceptions we should handle it and just rollback this transaction. This is done using the <code>markRollbackOnlyLast</code> which tells Camel to only do it for the current transaction and not globally.</p><h4 id="BookPatternAppendix-SeeAlso.7">See Also</h4><ul><li><a shape="rect" href="error-handling-in-camel.html">Error handling in Camel</a></li><li><a shape="rect" href="transactionerrorhandler.html">TransactionErrorHandler</a></li><li><a shape="rect" href="error-handler.html">Error Handler</a></li><li><a shape="rect" href="jms.html">JMS</a></li></ul><p></p><h4 id="BookPatternAppendix-UsingThisPattern.43">Using This Pattern</h4>
<p>If you would like to use this EIP Pattern then please read the <a shape="rect" href="getting-started.html">Getting Started</a>, you may also find the <a shape="rect" href="architecture.html">Architecture</a> useful particularly the description of <a shape="rect" href="endpoint.html">Endpoint</a> and <a shape="rect" href="uris.html">URIs</a>. Then you could try out some of the <a shape="rect" href="examples.html">Examples</a> first before trying this pattern out.</p>
-<h3 id="BookPatternAppendix-MessagingGateway">Messaging Gateway</h3>
-
-<p>Camel has several endpoint components that support the <a shape="rect" class="external-link" href="http://www.enterpriseintegrationpatterns.com/MessagingGateway.html" rel="nofollow">Messaging Gateway</a> from the <a shape="rect" href="enterprise-integration-patterns.html">EIP patterns</a>.</p>
-
-<p><img class="confluence-embedded-image confluence-external-resource" src="http://www.enterpriseintegrationpatterns.com/img/MessagingGatewaySolution.gif" data-image-src="http://www.enterpriseintegrationpatterns.com/img/MessagingGatewaySolution.gif"></p>
-
-<p>Components like <a shape="rect" href="bean.html">Bean</a> and <a shape="rect" href="cxf.html">CXF</a> provide a a way to bind a Java interface to the message exchange.</p>
-
-<p>However you may want to read the <a shape="rect" href="using-camelproxy.html">Using CamelProxy</a> documentation as a true <a shape="rect" href="messaging-gateway.html">Messaging Gateway</a> EIP solution.<br clear="none">
-Another approach is to use <code>@Produce</code> which you can read about in <a shape="rect" href="pojo-producing.html">POJO Producing</a> which also can be used as a <a shape="rect" href="messaging-gateway.html">Messaging Gateway</a> EIP solution.</p>
-
-<h4 id="BookPatternAppendix-SeeAlso.8">See Also</h4>
-
-<ul><li><a shape="rect" href="bean.html">Bean</a></li><li><a shape="rect" href="cxf.html">CXF</a></li><li><a shape="rect" href="using-camelproxy.html">Using CamelProxy</a></li><li><a shape="rect" href="pojo-producing.html">POJO Producing</a></li><li><a shape="rect" href="spring-remoting.html">Spring Remoting</a></li></ul>
-
-
-<h4 id="BookPatternAppendix-UsingThisPattern.44">Using This Pattern</h4>
+<h3 id="BookPatternAppendix-MessagingGateway">Messaging Gateway</h3><p>Camel has several endpoint components that support the <a shape="rect" class="external-link" href="http://www.enterpriseintegrationpatterns.com/MessagingGateway.html" rel="nofollow">Messaging Gateway</a> from the <a shape="rect" href="enterprise-integration-patterns.html">EIP patterns</a>.</p><p><img class="confluence-embedded-image confluence-external-resource" src="http://www.enterpriseintegrationpatterns.com/img/MessagingGatewaySolution.gif" data-image-src="http://www.enterpriseintegrationpatterns.com/img/MessagingGatewaySolution.gif"></p><p>Components like <a shape="rect" href="bean.html">Bean</a> and <a shape="rect" href="cxf.html">CXF</a> provide a a way to bind a Java interface to the message exchange.</p><p>However you may want to read the <a shape="rect" href="using-camelproxy.html">Using CamelProxy</a> documentation as a true <a shape="rect" href="messaging-gateway.html">Messaging Gateway</a> EIP soluti
on.<br clear="none"> Another approach is to use <code>@Produce</code> which you can read about in <a shape="rect" href="pojo-producing.html">POJO Producing</a> which also can be used as a <a shape="rect" href="messaging-gateway.html">Messaging Gateway</a> EIP solution.</p><p> </p><h4 id="BookPatternAppendix-Example.10">Example</h4><p>The following example how the <a shape="rect" href="cxf.html">CXF</a> and <a shape="rect" href="bean.html">Bean</a> components can be used to abstract the developer from the underlying messaging system API</p><p><strong><br clear="none"></strong></p><p><strong>Using the <a shape="rect" href="fluent-builders.html">Fluent Builders</a></strong></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[from("cxf:bean:soapMessageEndpoint")
+ .to("bean:testBean?method=processSOAP");]]></script>
+</div></div><p> </p><p><strong><strong>Using the <a shape="rect" href="spring-xml-extensions.html">Spring XML Extensions</a></strong></strong></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[<route>
+ <from uri="cxf:bean:soapMessageEndpoint"/>
+ <to uri="bean:testBean?method=processSOAP"/>
+</route>]]></script>
+</div></div><h4 id="BookPatternAppendix-SeeAlso.8">See Also</h4><ul><li><a shape="rect" href="bean.html">Bean</a></li><li><a shape="rect" href="cxf.html">CXF</a></li><li><a shape="rect" href="using-camelproxy.html">Using CamelProxy</a></li><li><a shape="rect" href="pojo-producing.html">POJO Producing</a></li><li><a shape="rect" href="spring-remoting.html">Spring Remoting</a></li></ul><p></p><h4 id="BookPatternAppendix-UsingThisPattern.44">Using This Pattern</h4>
<p>If you would like to use this EIP Pattern then please read the <a shape="rect" href="getting-started.html">Getting Started</a>, you may also find the <a shape="rect" href="architecture.html">Architecture</a> useful particularly the description of <a shape="rect" href="endpoint.html">Endpoint</a> and <a shape="rect" href="uris.html">URIs</a>. Then you could try out some of the <a shape="rect" href="examples.html">Examples</a> first before trying this pattern out.</p>
<h3 id="BookPatternAppendix-ServiceActivator">Service Activator</h3>
@@ -4919,7 +4911,7 @@ from("direct:invokeMyService")
<p><img class="confluence-embedded-image confluence-external-resource" src="http://www.enterpriseintegrationpatterns.com/img/Detour.gif" data-image-src="http://www.enterpriseintegrationpatterns.com/img/Detour.gif"></p>
-<h4 id="BookPatternAppendix-Example.10">Example</h4>
+<h4 id="BookPatternAppendix-Example.11">Example</h4>
<p>In this example we essentially have a route like <code>from("direct:start").to("mock:result")</code> with a conditional detour to the <code>mock:detour</code> endpoint in the middle of the route..</p>
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/messaging-gateway.html
==============================================================================
--- websites/production/camel/content/messaging-gateway.html (original)
+++ websites/production/camel/content/messaging-gateway.html Thu Sep 11 13:18:57 2014
@@ -36,6 +36,16 @@
<![endif]-->
+ <link href='//camel.apache.org/styles/highlighter/styles/shCoreCamel.css' rel='stylesheet' type='text/css' />
+ <link href='//camel.apache.org/styles/highlighter/styles/shThemeCamel.css' rel='stylesheet' type='text/css' />
+ <script src='//camel.apache.org/styles/highlighter/scripts/shCore.js' type='text/javascript'></script>
+ <script src='//camel.apache.org/styles/highlighter/scripts/shBrushJava.js' type='text/javascript'></script>
+ <script src='//camel.apache.org/styles/highlighter/scripts/shBrushXml.js' type='text/javascript'></script>
+
+ <script type="text/javascript">
+ SyntaxHighlighter.defaults['toolbar'] = false;
+ SyntaxHighlighter.all();
+ </script>
<title>
Apache Camel: Messaging Gateway
@@ -75,23 +85,15 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h3 id="MessagingGateway-MessagingGateway">Messaging Gateway</h3>
-
-<p>Camel has several endpoint components that support the <a shape="rect" class="external-link" href="http://www.enterpriseintegrationpatterns.com/MessagingGateway.html" rel="nofollow">Messaging Gateway</a> from the <a shape="rect" href="enterprise-integration-patterns.html">EIP patterns</a>.</p>
-
-<p><img class="confluence-embedded-image confluence-external-resource" src="http://www.enterpriseintegrationpatterns.com/img/MessagingGatewaySolution.gif" data-image-src="http://www.enterpriseintegrationpatterns.com/img/MessagingGatewaySolution.gif"></p>
-
-<p>Components like <a shape="rect" href="bean.html">Bean</a> and <a shape="rect" href="cxf.html">CXF</a> provide a a way to bind a Java interface to the message exchange.</p>
-
-<p>However you may want to read the <a shape="rect" href="using-camelproxy.html">Using CamelProxy</a> documentation as a true <a shape="rect" href="messaging-gateway.html">Messaging Gateway</a> EIP solution.<br clear="none">
-Another approach is to use <code>@Produce</code> which you can read about in <a shape="rect" href="pojo-producing.html">POJO Producing</a> which also can be used as a <a shape="rect" href="messaging-gateway.html">Messaging Gateway</a> EIP solution.</p>
-
-<h4 id="MessagingGateway-SeeAlso">See Also</h4>
-
-<ul><li><a shape="rect" href="bean.html">Bean</a></li><li><a shape="rect" href="cxf.html">CXF</a></li><li><a shape="rect" href="using-camelproxy.html">Using CamelProxy</a></li><li><a shape="rect" href="pojo-producing.html">POJO Producing</a></li><li><a shape="rect" href="spring-remoting.html">Spring Remoting</a></li></ul>
-
-
-<h4 id="MessagingGateway-UsingThisPattern">Using This Pattern</h4>
+<div class="wiki-content maincontent"><h3 id="MessagingGateway-MessagingGateway">Messaging Gateway</h3><p>Camel has several endpoint components that support the <a shape="rect" class="external-link" href="http://www.enterpriseintegrationpatterns.com/MessagingGateway.html" rel="nofollow">Messaging Gateway</a> from the <a shape="rect" href="enterprise-integration-patterns.html">EIP patterns</a>.</p><p><img class="confluence-embedded-image confluence-external-resource" src="http://www.enterpriseintegrationpatterns.com/img/MessagingGatewaySolution.gif" data-image-src="http://www.enterpriseintegrationpatterns.com/img/MessagingGatewaySolution.gif"></p><p>Components like <a shape="rect" href="bean.html">Bean</a> and <a shape="rect" href="cxf.html">CXF</a> provide a a way to bind a Java interface to the message exchange.</p><p>However you may want to read the <a shape="rect" href="using-camelproxy.html">Using CamelProxy</a> documentation as a true <a shape="rect" href="messaging-gateway.htm
l">Messaging Gateway</a> EIP solution.<br clear="none"> Another approach is to use <code>@Produce</code> which you can read about in <a shape="rect" href="pojo-producing.html">POJO Producing</a> which also can be used as a <a shape="rect" href="messaging-gateway.html">Messaging Gateway</a> EIP solution.</p><p> </p><h4 id="MessagingGateway-Example">Example</h4><p>The following example how the <a shape="rect" href="cxf.html">CXF</a> and <a shape="rect" href="bean.html">Bean</a> components can be used to abstract the developer from the underlying messaging system API</p><p><strong><br clear="none"></strong></p><p><strong>Using the <a shape="rect" href="fluent-builders.html">Fluent Builders</a></strong></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[from("cxf:bean:soapMessageEndpoint")
+ .to("bean:testBean?method=processSOAP");]]></script>
+</div></div><p> </p><p><strong><strong>Using the <a shape="rect" href="spring-xml-extensions.html">Spring XML Extensions</a></strong></strong></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[<route>
+ <from uri="cxf:bean:soapMessageEndpoint"/>
+ <to uri="bean:testBean?method=processSOAP"/>
+</route>]]></script>
+</div></div><h4 id="MessagingGateway-SeeAlso">See Also</h4><ul><li><a shape="rect" href="bean.html">Bean</a></li><li><a shape="rect" href="cxf.html">CXF</a></li><li><a shape="rect" href="using-camelproxy.html">Using CamelProxy</a></li><li><a shape="rect" href="pojo-producing.html">POJO Producing</a></li><li><a shape="rect" href="spring-remoting.html">Spring Remoting</a></li></ul><p></p><h4 id="MessagingGateway-UsingThisPattern">Using This Pattern</h4>
<p>If you would like to use this EIP Pattern then please read the <a shape="rect" href="getting-started.html">Getting Started</a>, you may also find the <a shape="rect" href="architecture.html">Architecture</a> useful particularly the description of <a shape="rect" href="endpoint.html">Endpoint</a> and <a shape="rect" href="uris.html">URIs</a>. Then you could try out some of the <a shape="rect" href="examples.html">Examples</a> first before trying this pattern out.</p></div>
</td>