camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1000860 - in /websites/production/camel/content: book-component-appendix.html book-in-one-page.html cache/main.pageCache test.html
Date Thu, 10 Nov 2016 15:21:03 GMT
Author: buildbot
Date: Thu Nov 10 15:21:03 2016
New Revision: 1000860

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/book-component-appendix.html
    websites/production/camel/content/book-in-one-page.html
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/test.html

Modified: websites/production/camel/content/book-component-appendix.html
==============================================================================
--- websites/production/camel/content/book-component-appendix.html (original)
+++ websites/production/camel/content/book-component-appendix.html Thu Nov 10 15:21:03 2016
@@ -621,8 +621,8 @@ cometds://localhost:8443/service/mychann
  <div class="confluence-information-macro-body">
   <p>When using CXF in streaming modes (see DataFormat option), then also read about
<a shape="rect" href="stream-caching.html">Stream caching</a>.</p>
  </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">/**/ div.rbtoc1478513883374
{padding: 0px;} div.rbtoc1478513883374 ul {list-style: disc;margin-left: 0px;} div.rbtoc1478513883374
li {margin-left: 0px;padding-left: 0px;} /**/</style>
- </p><div class="toc-macro rbtoc1478513883374"> 
+</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">/**/ div.rbtoc1478791089577
{padding: 0px;} div.rbtoc1478791089577 ul {list-style: disc;margin-left: 0px;} div.rbtoc1478791089577
li {margin-left: 0px;padding-left: 0px;} /**/</style>
+ </p><div class="toc-macro rbtoc1478791089577"> 
   <ul class="toc-indentation"><li><a shape="rect" href="#BookComponentAppendix-CXFComponent">CXF
Component</a> 
     <ul class="toc-indentation"><li><a shape="rect" href="#BookComponentAppendix-URIformat">URI
format</a></li><li><a shape="rect" href="#BookComponentAppendix-Options">Options</a>

       <ul class="toc-indentation"><li><a shape="rect" href="#BookComponentAppendix-Thedescriptionsofthedataformats">The
descriptions of the dataformats</a> 
@@ -5961,21 +5961,21 @@ test.endpoint = result2</pre>
    </div>
   </div>
  </div>
-</div><h2 id="BookComponentAppendix-TestComponent">Test Component</h2><p><a
shape="rect" href="testing.html">Testing</a> of distributed and asynchronous processing
is notoriously difficult. The <a shape="rect" href="mock.html">Mock</a>, <a
shape="rect" href="test.html">Test</a> and <a shape="rect" href="dataset.html">DataSet</a>
endpoints work great with the <a shape="rect" href="testing.html">Camel Testing Framework</a>
to simplify your unit and integration testing using <a shape="rect" href="enterprise-integration-patterns.html">Enterprise
Integration Patterns</a> and Camel's large range of <a shape="rect" href="components.html">Components</a>
together with the powerful <a shape="rect" href="bean-integration.html">Bean Integration</a>.</p><p>The
<strong>test</strong> component extends the <a shape="rect" href="mock.html">Mock</a>
component to support pulling messages from another endpoint on startup to set the expected
message bodies on the underlying <a shape="rect" href="mock.ht
 ml">Mock</a> endpoint. That is, you use the test endpoint in a route and messages
arriving on it will be implicitly compared to some expected messages extracted from some other
location.</p><p>So you can use, for example, an expected set of message bodies
as files. This will then set up a properly configured <a shape="rect" href="mock.html">Mock</a>
endpoint, which is only valid if the received messages match the number of expected messages
and their message payloads are equal.</p><p>Maven users will need to add the following
dependency to their <code>pom.xml</code> for this component when using <strong>Camel
2.8</strong> or older:</p><div class="code panel pdl" style="border-width:
1px;">
+</div><h2 id="BookComponentAppendix-TestComponent">Test Component</h2><p><a
shape="rect" href="testing.html">Testing</a> of distributed and asynchronous processing
is notoriously difficult. The <a shape="rect" href="mock.html">Mock</a>, <a
shape="rect" href="test.html">Test</a> and <a shape="rect" href="dataset.html">DataSet</a>
endpoints work great with the <a shape="rect" href="testing.html">Camel Testing Framework</a>
to simplify your unit and integration testing using <a shape="rect" href="enterprise-integration-patterns.html">Enterprise
Integration Patterns</a> and Camel's large range of <a shape="rect" href="components.html">Components</a>
together with the powerful <a shape="rect" href="bean-integration.html">Bean Integration</a>.</p><p>The
<strong><code>test</code></strong> component extends the <a shape="rect"
href="mock.html">Mock</a> component to support pulling messages from another endpoint
on startup to set the expected message bodies on the underlying <a shape="rect" 
 href="mock.html">Mock</a> endpoint. That is, you use the test endpoint in a route
and messages arriving on it will be implicitly compared to some expected messages extracted
from some other location.</p><p>So you can use, for example, an expected set of
message bodies as files. This will then set up a properly configured <a shape="rect" href="mock.html">Mock</a>
endpoint, which is only valid if the received messages match the number of expected messages
and their message payloads are equal.</p><p>Maven users will need to add the following
dependency to their <strong><code>pom.xml</code></strong> for this
component when using <strong>Camel 2.8</strong> or older:</p><div class="code
panel pdl" style="border-width: 1px;">
  <div class="codeContent panelContent pdl"> 
   <script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter">&amp;lt;dependency&amp;gt;
&amp;lt;groupId&amp;gt;org.apache.camel&amp;lt;/groupId&amp;gt; &amp;lt;artifactId&amp;gt;camel-spring&amp;lt;/artifactId&amp;gt;
&amp;lt;version&amp;gt;x.x.x&amp;lt;/version&amp;gt; &amp;lt;!-- use the
same version as your Camel core version --&amp;gt; &amp;lt;/dependency&amp;gt;
</script> 
  </div>
-</div><p>From Camel 2.9 onwards the <a shape="rect" href="test.html">Test</a>
component is provided directly in the camel-core.</p><h3 id="BookComponentAppendix-URIformat.68">URI
format</h3><div class="code panel pdl" style="border-width: 1px;">
+</div><p>From <strong>Camel 2.9</strong>: the <a shape="rect"
href="test.html">Test</a> component is provided directly in <strong><code>camel-core</code></strong>.</p><h3
id="BookComponentAppendix-URIformat.68">URI format</h3><div class="code panel
pdl" style="border-width: 1px;">
  <div class="codeContent panelContent pdl"> 
   <script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter">test:expectedMessagesEndpointUri
</script> 
  </div>
-</div><p>Where <strong>expectedMessagesEndpointUri</strong> refers
to some other <a shape="rect" href="component.html">Component</a> URI that the
expected message bodies are pulled from before starting the test.</p><h3 id="BookComponentAppendix-URIOptions.10">URI
Options</h3><div class="confluenceTableSmall">
+</div><p>Where&#160;<strong><code>expectedMessagesEndpointUri</code></strong>
refers to some other <a shape="rect" href="component.html">Component</a> URI that
the expected message bodies are pulled from before starting the test.</p><h3 id="BookComponentAppendix-URIOptions.10">URI
Options</h3><div class="confluenceTableSmall">
  <div class="table-wrap"> 
-  <table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>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>timeout</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>2000</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.12:</strong>
The timeout to use when polling for message bodies from the URI.</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">anyOrder</td><td colspan="1" rowspan="1"
class="confluenceTd">false</td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel
2.17:</strong> Whether the expected messages should arrive in the same order or can
be in any order.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">split</td><td
colspan="1" rowspan="1" class="confluenceTd">false
 </td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.17:</strong>
If enabled the the messages loaded from the test endpoint will be split using \n\r delimiters
(new lines) so each line is an expected message.<br clear="none">For example to use
a file endpoint to load a file where each line is an expected message.&#160;</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">delimiter</td><td colspan="1" rowspan="1"
class="confluenceTd">\n|\r</td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel
2.17:</strong> The split delimiter to use when split is enabled. By default the delimiter
is new line based. The delimiter can be a regular expression.</td></tr></tbody></table>

+  <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"><code>anyOrder</code></td><td
colspan="1" rowspan="1" class="confluenceTd"><code>false</code></td><td
colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.17:</strong> Whether
the expected messages should arrive in the same order, or in any order.</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><code>delimiter</code></td><td
colspan="1" rowspan="1" class="confluenceTd"><code>\n|\r</code></td><td
colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.17:</strong> The
delimiter to use when&#160;<strong><code>split=true</code></strong>.
The delimiter can be a regular expression.</td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><code>split
 </code></td><td colspan="1" rowspan="1" class="confluenceTd"><code>false</code></td><td
colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.17:</strong> If&#160;<strong><code>true</code></strong>
messages loaded from the test endpoint will be split using the defined <strong><code>delimiter</code></strong>.<br
clear="none">For example to use a&#160;<strong><code>file</code></strong>
endpoint to load a file where each line is an expected message.&#160;</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>timeout</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>2000</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.12:</strong>
The timeout to use when polling for message bodies from the URI.</p></td></tr></tbody></table>

  </div>
 </div><h3 id="BookComponentAppendix-Example.10">Example</h3><p>For
example, you could write a test case as follows:</p><div class="code panel pdl" style="border-width:
1px;">
  <div class="codeContent panelContent pdl"> 
-  <script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter">from(&amp;quot;seda:someEndpoint&amp;quot;).
to(&amp;quot;test:file://data/expectedOutput?noop=true&amp;quot;); </script>

+  <script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter">from(&amp;quot;seda:someEndpoint&amp;quot;)
.to(&amp;quot;test:file://data/expectedOutput?noop=true&amp;quot;); </script>

  </div>
 </div><p>If your test then invokes the <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/component/mock/MockEndpoint.html#assertIsSatisfied(org.apache.camel.CamelContext)">MockEndpoint.assertIsSatisfied(camelContext)
method</a>, your test case will perform the necessary assertions.</p><p>To
see how you can set other expectations on the test endpoint, see the <a shape="rect" href="mock.html">Mock</a>
component.</p><p></p><h3 id="BookComponentAppendix-SeeAlso.64">See
Also</h3> 
  <ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a
shape="rect" href="component.html">Component</a></li><li><a shape="rect"
href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting
Started</a></li></ul><ul><li><a shape="rect" href="spring-testing.html">Spring
Testing</a></li></ul><h2 id="BookComponentAppendix-TimerComponent">Timer
Component</h2><p>The <strong>timer:</strong> component is used to
generate message exchanges when a timer fires You can only consume events from this endpoint.</p><h3
id="BookComponentAppendix-URIformat.69">URI format</h3><div class="code panel
pdl" style="border-width: 1px;">

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 Nov 10 15:21:03 2016
@@ -3966,11 +3966,11 @@ The tutorial has been designed in two pa
 While not actual tutorials you might find working through the source of the various <a
shape="rect" href="examples.html">Examples</a> useful.</li></ul>
 
 <h2 id="BookInOnePage-TutorialonSpringRemotingwithJMS">Tutorial on Spring Remoting
with JMS</h2><p>&#160;</p><div class="confluence-information-macro
confluence-information-macro-information"><p class="title">Thanks</p><span
class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>This tutorial was kindly donated to
Apache Camel by Martin Gilday.</p></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.rbtoc1478513926754 {padding: 0px;}
-div.rbtoc1478513926754 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1478513926754 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1478791134056 {padding: 0px;}
+div.rbtoc1478791134056 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1478791134056 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style></p><div class="toc-macro rbtoc1478513926754">
+/*]]>*/</style></p><div class="toc-macro rbtoc1478791134056">
 <ul class="toc-indentation"><li><a shape="rect" href="#BookInOnePage-TutorialonSpringRemotingwithJMS">Tutorial
on Spring Remoting with JMS</a></li><li><a shape="rect" href="#BookInOnePage-Preface">Preface</a></li><li><a
shape="rect" href="#BookInOnePage-Prerequisites">Prerequisites</a></li><li><a
shape="rect" href="#BookInOnePage-Distribution">Distribution</a></li><li><a
shape="rect" href="#BookInOnePage-About">About</a></li><li><a shape="rect"
href="#BookInOnePage-CreatetheCamelProject">Create the Camel Project</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#BookInOnePage-UpdatethePOMwithDependencies">Update
the POM with Dependencies</a></li></ul>
 </li><li><a shape="rect" href="#BookInOnePage-WritingtheServer">Writing
the Server</a>
@@ -6085,11 +6085,11 @@ So we completed the last piece in the pi
 <p>This example has been removed from <strong>Camel 2.9</strong> onwards.
Apache Axis 1.4 is a very old and unsupported framework. We encourage users to use <a shape="rect"
href="cxf.html">CXF</a> instead of Axis.</p></div></div>
 
 <style type="text/css">/*<![CDATA[*/
-div.rbtoc1478513927596 {padding: 0px;}
-div.rbtoc1478513927596 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1478513927596 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1478791134602 {padding: 0px;}
+div.rbtoc1478791134602 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1478791134602 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style><div class="toc-macro rbtoc1478513927596">
+/*]]>*/</style><div class="toc-macro rbtoc1478791134602">
 <ul class="toc-indentation"><li><a shape="rect" href="#BookInOnePage-TutorialusingAxis1.4withApacheCamel">Tutorial
using Axis 1.4 with Apache Camel</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#BookInOnePage-Prerequisites">Prerequisites</a></li><li><a
shape="rect" href="#BookInOnePage-Distribution">Distribution</a></li><li><a
shape="rect" href="#BookInOnePage-Introduction">Introduction</a></li><li><a
shape="rect" href="#BookInOnePage-SettinguptheprojecttorunAxis">Setting up the project
to run Axis</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#BookInOnePage-Maven2">Maven
2</a></li><li><a shape="rect" href="#BookInOnePage-wsdl">wsdl</a></li><li><a
shape="rect" href="#BookInOnePage-ConfiguringAxis">Configuring Axis</a></li><li><a
shape="rect" href="#BookInOnePage-RunningtheExample">Running the Example</a></li></ul>
@@ -14323,8 +14323,8 @@ cometds://localhost:8443/service/mychann
  <div class="confluence-information-macro-body">
   <p>When using CXF in streaming modes (see DataFormat option), then also read about
<a shape="rect" href="stream-caching.html">Stream caching</a>.</p>
  </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">/**/ div.rbtoc1478513964037
{padding: 0px;} div.rbtoc1478513964037 ul {list-style: disc;margin-left: 0px;} div.rbtoc1478513964037
li {margin-left: 0px;padding-left: 0px;} /**/</style>
- </p><div class="toc-macro rbtoc1478513964037"> 
+</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">/**/ div.rbtoc1478791175245
{padding: 0px;} div.rbtoc1478791175245 ul {list-style: disc;margin-left: 0px;} div.rbtoc1478791175245
li {margin-left: 0px;padding-left: 0px;} /**/</style>
+ </p><div class="toc-macro rbtoc1478791175245"> 
   <ul class="toc-indentation"><li><a shape="rect" href="#BookInOnePage-CXFComponent">CXF
Component</a> 
     <ul class="toc-indentation"><li><a shape="rect" href="#BookInOnePage-URIformat">URI
format</a></li><li><a shape="rect" href="#BookInOnePage-Options">Options</a>

       <ul class="toc-indentation"><li><a shape="rect" href="#BookInOnePage-Thedescriptionsofthedataformats">The
descriptions of the dataformats</a> 
@@ -19663,21 +19663,21 @@ test.endpoint = result2</pre>
    </div>
   </div>
  </div>
-</div><h2 id="BookInOnePage-TestComponent">Test Component</h2><p><a
shape="rect" href="testing.html">Testing</a> of distributed and asynchronous processing
is notoriously difficult. The <a shape="rect" href="mock.html">Mock</a>, <a
shape="rect" href="test.html">Test</a> and <a shape="rect" href="dataset.html">DataSet</a>
endpoints work great with the <a shape="rect" href="testing.html">Camel Testing Framework</a>
to simplify your unit and integration testing using <a shape="rect" href="enterprise-integration-patterns.html">Enterprise
Integration Patterns</a> and Camel's large range of <a shape="rect" href="components.html">Components</a>
together with the powerful <a shape="rect" href="bean-integration.html">Bean Integration</a>.</p><p>The
<strong>test</strong> component extends the <a shape="rect" href="mock.html">Mock</a>
component to support pulling messages from another endpoint on startup to set the expected
message bodies on the underlying <a shape="rect" href="mock.html">Mock
 </a> endpoint. That is, you use the test endpoint in a route and messages arriving
on it will be implicitly compared to some expected messages extracted from some other location.</p><p>So
you can use, for example, an expected set of message bodies as files. This will then set up
a properly configured <a shape="rect" href="mock.html">Mock</a> endpoint, which
is only valid if the received messages match the number of expected messages and their message
payloads are equal.</p><p>Maven users will need to add the following dependency
to their <code>pom.xml</code> for this component when using <strong>Camel
2.8</strong> or older:</p><div class="code panel pdl" style="border-width:
1px;">
+</div><h2 id="BookInOnePage-TestComponent">Test Component</h2><p><a
shape="rect" href="testing.html">Testing</a> of distributed and asynchronous processing
is notoriously difficult. The <a shape="rect" href="mock.html">Mock</a>, <a
shape="rect" href="test.html">Test</a> and <a shape="rect" href="dataset.html">DataSet</a>
endpoints work great with the <a shape="rect" href="testing.html">Camel Testing Framework</a>
to simplify your unit and integration testing using <a shape="rect" href="enterprise-integration-patterns.html">Enterprise
Integration Patterns</a> and Camel's large range of <a shape="rect" href="components.html">Components</a>
together with the powerful <a shape="rect" href="bean-integration.html">Bean Integration</a>.</p><p>The
<strong><code>test</code></strong> component extends the <a shape="rect"
href="mock.html">Mock</a> component to support pulling messages from another endpoint
on startup to set the expected message bodies on the underlying <a shape="rect" href="mo
 ck.html">Mock</a> endpoint. That is, you use the test endpoint in a route and messages
arriving on it will be implicitly compared to some expected messages extracted from some other
location.</p><p>So you can use, for example, an expected set of message bodies
as files. This will then set up a properly configured <a shape="rect" href="mock.html">Mock</a>
endpoint, which is only valid if the received messages match the number of expected messages
and their message payloads are equal.</p><p>Maven users will need to add the following
dependency to their <strong><code>pom.xml</code></strong> for this
component when using <strong>Camel 2.8</strong> or older:</p><div class="code
panel pdl" style="border-width: 1px;">
  <div class="codeContent panelContent pdl"> 
   <script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter">&amp;lt;dependency&amp;gt;
&amp;lt;groupId&amp;gt;org.apache.camel&amp;lt;/groupId&amp;gt; &amp;lt;artifactId&amp;gt;camel-spring&amp;lt;/artifactId&amp;gt;
&amp;lt;version&amp;gt;x.x.x&amp;lt;/version&amp;gt; &amp;lt;!-- use the
same version as your Camel core version --&amp;gt; &amp;lt;/dependency&amp;gt;
</script> 
  </div>
-</div><p>From Camel 2.9 onwards the <a shape="rect" href="test.html">Test</a>
component is provided directly in the camel-core.</p><h3 id="BookInOnePage-URIformat.69">URI
format</h3><div class="code panel pdl" style="border-width: 1px;">
+</div><p>From <strong>Camel 2.9</strong>: the <a shape="rect"
href="test.html">Test</a> component is provided directly in <strong><code>camel-core</code></strong>.</p><h3
id="BookInOnePage-URIformat.69">URI format</h3><div class="code panel pdl" style="border-width:
1px;">
  <div class="codeContent panelContent pdl"> 
   <script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter">test:expectedMessagesEndpointUri
</script> 
  </div>
-</div><p>Where <strong>expectedMessagesEndpointUri</strong> refers
to some other <a shape="rect" href="component.html">Component</a> URI that the
expected message bodies are pulled from before starting the test.</p><h3 id="BookInOnePage-URIOptions.10">URI
Options</h3><div class="confluenceTableSmall">
+</div><p>Where&#160;<strong><code>expectedMessagesEndpointUri</code></strong>
refers to some other <a shape="rect" href="component.html">Component</a> URI that
the expected message bodies are pulled from before starting the test.</p><h3 id="BookInOnePage-URIOptions.10">URI
Options</h3><div class="confluenceTableSmall">
  <div class="table-wrap"> 
-  <table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>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>timeout</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>2000</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.12:</strong>
The timeout to use when polling for message bodies from the URI.</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">anyOrder</td><td colspan="1" rowspan="1"
class="confluenceTd">false</td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel
2.17:</strong> Whether the expected messages should arrive in the same order or can
be in any order.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">split</td><td
colspan="1" rowspan="1" class="confluenceTd">false
 </td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.17:</strong>
If enabled the the messages loaded from the test endpoint will be split using \n\r delimiters
(new lines) so each line is an expected message.<br clear="none">For example to use
a file endpoint to load a file where each line is an expected message.&#160;</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">delimiter</td><td colspan="1" rowspan="1"
class="confluenceTd">\n|\r</td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel
2.17:</strong> The split delimiter to use when split is enabled. By default the delimiter
is new line based. The delimiter can be a regular expression.</td></tr></tbody></table>

+  <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"><code>anyOrder</code></td><td
colspan="1" rowspan="1" class="confluenceTd"><code>false</code></td><td
colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.17:</strong> Whether
the expected messages should arrive in the same order, or in any order.</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><code>delimiter</code></td><td
colspan="1" rowspan="1" class="confluenceTd"><code>\n|\r</code></td><td
colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.17:</strong> The
delimiter to use when&#160;<strong><code>split=true</code></strong>.
The delimiter can be a regular expression.</td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><code>split
 </code></td><td colspan="1" rowspan="1" class="confluenceTd"><code>false</code></td><td
colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.17:</strong> If&#160;<strong><code>true</code></strong>
messages loaded from the test endpoint will be split using the defined <strong><code>delimiter</code></strong>.<br
clear="none">For example to use a&#160;<strong><code>file</code></strong>
endpoint to load a file where each line is an expected message.&#160;</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>timeout</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>2000</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.12:</strong>
The timeout to use when polling for message bodies from the URI.</p></td></tr></tbody></table>

  </div>
 </div><h3 id="BookInOnePage-Example.29">Example</h3><p>For example,
you could write a test case as follows:</p><div class="code panel pdl" style="border-width:
1px;">
  <div class="codeContent panelContent pdl"> 
-  <script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter">from(&amp;quot;seda:someEndpoint&amp;quot;).
to(&amp;quot;test:file://data/expectedOutput?noop=true&amp;quot;); </script>

+  <script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter">from(&amp;quot;seda:someEndpoint&amp;quot;)
.to(&amp;quot;test:file://data/expectedOutput?noop=true&amp;quot;); </script>

  </div>
 </div><p>If your test then invokes the <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/component/mock/MockEndpoint.html#assertIsSatisfied(org.apache.camel.CamelContext)">MockEndpoint.assertIsSatisfied(camelContext)
method</a>, your test case will perform the necessary assertions.</p><p>To
see how you can set other expectations on the test endpoint, see the <a shape="rect" href="mock.html">Mock</a>
component.</p><p></p><h3 id="BookInOnePage-SeeAlso.84">See Also</h3>

  <ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a
shape="rect" href="component.html">Component</a></li><li><a shape="rect"
href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting
Started</a></li></ul><ul><li><a shape="rect" href="spring-testing.html">Spring
Testing</a></li></ul><h2 id="BookInOnePage-TimerComponent">Timer Component</h2><p>The
<strong>timer:</strong> component is used to generate message exchanges when a
timer fires You can only consume events from this endpoint.</p><h3 id="BookInOnePage-URIformat.70">URI
format</h3><div class="code panel pdl" style="border-width: 1px;">

Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/camel/content/test.html
==============================================================================
--- websites/production/camel/content/test.html (original)
+++ websites/production/camel/content/test.html Thu Nov 10 15:21:03 2016
@@ -85,7 +85,7 @@
 	<tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="Test-TestComponent">Test Component</h2><p><a
shape="rect" href="testing.html">Testing</a> of distributed and asynchronous processing
is notoriously difficult. The <a shape="rect" href="mock.html">Mock</a>, <a
shape="rect" href="test.html">Test</a> and <a shape="rect" href="dataset.html">DataSet</a>
endpoints work great with the <a shape="rect" href="testing.html">Camel Testing Framework</a>
to simplify your unit and integration testing using <a shape="rect" href="enterprise-integration-patterns.html">Enterprise
Integration Patterns</a> and Camel's large range of <a shape="rect" href="components.html">Components</a>
together with the powerful <a shape="rect" href="bean-integration.html">Bean Integration</a>.</p><p>The
<strong>test</strong> component extends the <a shape="rect" href="mock.html">Mock</a>
component to support pulling messages from another endpoint on startup to set the expected
message bodies on the underlying <a shape="rect
 " href="mock.html">Mock</a> endpoint. That is, you use the test endpoint in a route
and messages arriving on it will be implicitly compared to some expected messages extracted
from some other location.</p><p>So you can use, for example, an expected set of
message bodies as files. This will then set up a properly configured <a shape="rect" href="mock.html">Mock</a>
endpoint, which is only valid if the received messages match the number of expected messages
and their message payloads are equal.</p><p>Maven users will need to add the following
dependency to their <code>pom.xml</code> for this component when using <strong>Camel
2.8</strong> or older:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<div class="wiki-content maincontent"><h2 id="Test-TestComponent">Test Component</h2><p><a
shape="rect" href="testing.html">Testing</a> of distributed and asynchronous processing
is notoriously difficult. The <a shape="rect" href="mock.html">Mock</a>, <a
shape="rect" href="test.html">Test</a> and <a shape="rect" href="dataset.html">DataSet</a>
endpoints work great with the <a shape="rect" href="testing.html">Camel Testing Framework</a>
to simplify your unit and integration testing using <a shape="rect" href="enterprise-integration-patterns.html">Enterprise
Integration Patterns</a> and Camel's large range of <a shape="rect" href="components.html">Components</a>
together with the powerful <a shape="rect" href="bean-integration.html">Bean Integration</a>.</p><p>The
<strong><code>test</code></strong> component extends the <a shape="rect"
href="mock.html">Mock</a> component to support pulling messages from another endpoint
on startup to set the expected message bodies on the underlying <
 a shape="rect" href="mock.html">Mock</a> endpoint. That is, you use the test endpoint
in a route and messages arriving on it will be implicitly compared to some expected messages
extracted from some other location.</p><p>So you can use, for example, an expected
set of message bodies as files. This will then set up a properly configured <a shape="rect"
href="mock.html">Mock</a> endpoint, which is only valid if the received messages
match the number of expected messages and their message payloads are equal.</p><p>Maven
users will need to add the following dependency to their <strong><code>pom.xml</code></strong>
for this component when using <strong>Camel 2.8</strong> or older:</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
 <script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[&lt;dependency&gt;
     &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
     &lt;artifactId&gt;camel-spring&lt;/artifactId&gt;
@@ -93,14 +93,14 @@
     &lt;!-- use the same version as your Camel core version --&gt;
 &lt;/dependency&gt;
 ]]></script>
-</div></div><p>From Camel 2.9 onwards the <a shape="rect" href="test.html">Test</a>
component is provided directly in the camel-core.</p><h3 id="Test-URIformat">URI
format</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><p>From <strong>Camel 2.9</strong>: the <a shape="rect"
href="test.html">Test</a> component is provided directly in <strong><code>camel-core</code></strong>.</p><h3
id="Test-URIformat">URI format</h3><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
 <script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[test:expectedMessagesEndpointUri
 ]]></script>
-</div></div><p>Where <strong>expectedMessagesEndpointUri</strong>
refers to some other <a shape="rect" href="component.html">Component</a> URI that
the expected message bodies are pulled from before starting the test.</p><h3 id="Test-URIOptions">URI
Options</h3><div class="confluenceTableSmall"><div class="table-wrap">
- <table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>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>timeout</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>2000</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.12:</strong>
The timeout to use when polling for message bodies from the URI.</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">anyOrder</td><td colspan="1" rowspan="1"
class="confluenceTd">false</td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel
2.17:</strong> Whether the expected messages should arrive in the same order or can
be in any order.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">split</td><td
colspan="1" rowspan="1" class="confluenceTd">false<
 /td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.17:</strong>
If enabled the the messages loaded from the test endpoint will be split using \n\r delimiters
(new lines) so each line is an expected message.<br clear="none">For example to use
a file endpoint to load a file where each line is an expected message.&#160;</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">delimiter</td><td colspan="1" rowspan="1"
class="confluenceTd">\n|\r</td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel
2.17:</strong> The split delimiter to use when split is enabled. By default the delimiter
is new line based. The delimiter can be a regular expression.</td></tr></tbody></table>
+</div></div><p>Where&#160;<strong><code>expectedMessagesEndpointUri</code></strong>
refers to some other <a shape="rect" href="component.html">Component</a> URI that
the expected message bodies are pulled from before starting the test.</p><h3 id="Test-URIOptions">URI
Options</h3><div class="confluenceTableSmall"><div class="table-wrap">
+ <table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default
Value</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><code>anyOrder</code></td><td
colspan="1" rowspan="1" class="confluenceTd"><code>false</code></td><td
colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.17:</strong> Whether
the expected messages should arrive in the same order, or in any order.</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><code>delimiter</code></td><td
colspan="1" rowspan="1" class="confluenceTd"><code>\n|\r</code></td><td
colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.17:</strong> The
delimiter to use when&#160;<strong><code>split=true</code></strong>.
The delimiter can be a regular expression.</td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><code>split<
 /code></td><td colspan="1" rowspan="1" class="confluenceTd"><code>false</code></td><td
colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.17:</strong> If&#160;<strong><code>true</code></strong>
messages loaded from the test endpoint will be split using the defined <strong><code>delimiter</code></strong>.<br
clear="none">For example to use a&#160;<strong><code>file</code></strong>
endpoint to load a file where each line is an expected message.&#160;</td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>timeout</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>2000</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.12:</strong>
The timeout to use when polling for message bodies from the URI.</p></td></tr></tbody></table>
 </div></div><h3 id="Test-Example">Example</h3><p>For example,
you could write a test case as follows:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[from(&quot;seda:someEndpoint&quot;).
-  to(&quot;test:file://data/expectedOutput?noop=true&quot;);
+<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[from(&quot;seda:someEndpoint&quot;)
+  .to(&quot;test:file://data/expectedOutput?noop=true&quot;);
 ]]></script>
 </div></div><p>If your test then invokes the <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/component/mock/MockEndpoint.html#assertIsSatisfied(org.apache.camel.CamelContext)">MockEndpoint.assertIsSatisfied(camelContext)
method</a>, your test case will perform the necessary assertions.</p><p>To
see how you can set other expectations on the test endpoint, see the <a shape="rect" href="mock.html">Mock</a>
component.</p><p></p><h3 id="Test-SeeAlso">See Also</h3>
 <ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a
shape="rect" href="component.html">Component</a></li><li><a shape="rect"
href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting
Started</a></li></ul><ul><li><a shape="rect" href="spring-testing.html">Spring
Testing</a></li></ul></div>




Mime
View raw message