Author: buildbot
Date: Thu Mar 10 12:20:31 2016
New Revision: 982386
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-2170-release.html
websites/production/camel/content/testing.html
Modified: websites/production/camel/content/book-cookbook.html
==============================================================================
--- websites/production/camel/content/book-cookbook.html (original)
+++ websites/production/camel/content/book-cookbook.html Thu Mar 10 12:20:31
2016
@@ -1351,7 +1351,7 @@ public class IsMockEndpointsAndSkipJUnit
]]></script>
</div></div><div class="confluence-information-macro
confluence-information-macro-tip"><p class="title">time units</p><span
class="aui-icon aui-icon-small aui-iconfont-approve
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>In the example above we use
<code>seconds</code> as the time unit, but Camel offers
<code>milliseconds</code>, and <code>minutes</code> as
well.</p></div></div><p></p><h3 id="Bookcookbook-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><li><a
shape="rect" href="testing.html">Testing</a></li></ul>
-<h2 id="Bookcookbook-Testing">Testing</h2><p>Testing is a crucial activity in
any piece of software development or integration. Typically Camel Riders use
various different <a shape="rect" href="components.html">technologies</a> wired
together in a variety of <a shape="rect"
href="enterprise-integration-patterns.html">patterns</a> with different <a
shape="rect" href="languages.html">expression languages</a> together with
different forms of <a shape="rect" href="bean-integration.html">Bean
Integration</a> and <a shape="rect" href="dependency-injection.html">Dependency
Injection</a> so its very easy for things to go wrong! <img class="emoticon
emoticon-smile"
src="https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/smile.png";
data-emoticon-name="smile" alt="(smile)"> . Testing is the crucial weapon to
ensure that things work as you would expect.</p><p>Camel is a Java library so
you can easily wire up tests in whatever un
it testing framework you use (JUnit 3.x (deprecated), 4.x, or TestNG). However
the Camel project has tried to make the testing of Camel as easy and powerful
as possible so we have introduced the following features.</p><h3
id="Bookcookbook-Testingmechanisms">Testing mechanisms</h3><p>The following
mechanisms are supported</p><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>Component</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><a shape="rect"
href="camel-test.html">Camel Test</a></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>camel-test</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Is a standalone Java library letting you
easily create Camel test cases using a single Java class for all your
configuration and routing wi
thout using <a shape="rect" href="spring.html">Spring</a> or <a shape="rect"
href="guice.html">Guice</a> for <a shape="rect"
href="dependency-injection.html">Dependency Injection</a> which does not
require an in-depth knowledge of Spring + Spring Test or Guice.  Supports
JUnit 3.x (deprecated) and JUnit 4.x based tests.</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><a shape="rect"
href="cdi-testing.html">CDI Testing</a></td><td colspan="1" rowspan="1"
class="confluenceTd"><code>camel-test-cdi</code></td><td colspan="1"
rowspan="1" class="confluenceTd"><span style="color: rgb(0,0,0);">Provides a
JUnit 4 runner that bootstraps a test environment using CDI so that you don't
have to be familiar with any CDI testing frameworks and can concentrate on the
testing logic of your Camel CDI applications. Testing frameworks like <a
shape="rect" class="external-link" href="http://arquillian.org";
rel="nofollow">Arquillian</a> or <a shape="rect" class="external-link"
href="https://ops4j1.jira.com/wiki/display/PAXEXAM4"; rel="nofollow">PAX
Exam</a>, can be used for more advanced test cases, where you need to configure
your system under test in a very fine-grained way or target specific CDI
containers.</span></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><a shape="rect" href="spring-testing.html">Spring
Testing</a></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>camel-test-spring</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Supports JUnit 3.x (deprecated) or JUnit
4.x based tests that bootstrap a test environment using Spring without needing
to be familiar with Spring Test. The plain JUnit 3.x/4.x based tests work very
similar to the test support classes in <code>camel-test</code>.  Also
supports Spring Test based tests that use the declarative style of test
configuration and injection common in Spring Test.  The Spring Test based
tests provide feature parity with the plain JUnit
3.x/4.x based testing approach.  Notice <code>camel-test-spring</code> is
a new component in <strong>Camel 2.10</strong> onwards. For older Camel release
use <code>camel-test</code> which has built-in <a shape="rect"
href="spring-testing.html">Spring Testing</a>.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><a shape="rect"
href="blueprint-testing.html">Blueprint Testing</a></p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>camel-test-blueprint</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.10:</strong>
Provides the ability to do unit testing on blueprint
configurations</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><a shape="rect" href="guice.html">Guice</a></p></td><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>camel-guice</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Uses <a shape="rect"
href="guice.html">Guice</a> to dependency inject your test cl
asses</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>Camel TestNG</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>camel-testng</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Supports plain TestNG based tests with
or without <a shape="rect" href="spring.html">Spring</a> or <a
shape="rect" href="guice.html">Guice</a> for <a shape="rect"
href="dependency-injection.html">Dependency Injection</a> which does not
require an in-depth knowledge of Spring + Spring Test or Guice.  Also from
<strong>Camel 2.10</strong> onwards, this component supports Spring
Test based tests that use the declarative style of test configuration and
injection common in Spring Test and described in more detail under <a
shape="rect" href="spring-testing.html">Spring
Testing</a>.</p></td></tr></tbody></table></div><p>In all approaches the test
classes look pretty much the same in that they all reuse the <a shape=
"rect" href="bean-integration.html">Camel binding and injection
annotations</a>.</p><h4 id="Bookcookbook-CamelTestExample">Camel Test
Example</h4><p>Here is the <a shape="rect" href="camel-test.html">Camel
Test</a> <a shape="rect" class="external-link"
href="http://svn.apache.org/repos/asf/camel/trunk/components/camel-test/src/test/java/org/apache/camel/test/patterns/FilterTest.java";>example</a>.</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+<h2 id="Bookcookbook-Testing">Testing</h2><p>Testing is a crucial activity in
any piece of software development or integration. Typically Camel Riders use
various different <a shape="rect" href="components.html">technologies</a> wired
together in a variety of <a shape="rect"
href="enterprise-integration-patterns.html">patterns</a> with different <a
shape="rect" href="languages.html">expression languages</a> together with
different forms of <a shape="rect" href="bean-integration.html">Bean
Integration</a> and <a shape="rect" href="dependency-injection.html">Dependency
Injection</a> so its very easy for things to go wrong! <img class="emoticon
emoticon-smile"
src="https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/smile.png";
data-emoticon-name="smile" alt="(smile)"> . Testing is the crucial weapon to
ensure that things work as you would expect.</p><p>Camel is a Java library so
you can easily wire up tests in whatever un
it testing framework you use (JUnit 3.x (deprecated), 4.x, or TestNG). However
the Camel project has tried to make the testing of Camel as easy and powerful
as possible so we have introduced the following features.</p><h3
id="Bookcookbook-Testingmechanisms">Testing mechanisms</h3><p>The following
mechanisms are supported</p><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>Component</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><a shape="rect"
href="camel-test.html">Camel Test</a></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>camel-test</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Is a standalone Java library letting you
easily create Camel test cases using a single Java class for all your
configuration and routing wi
thout using <a shape="rect" href="spring.html">Spring</a> or <a shape="rect"
href="guice.html">Guice</a> for <a shape="rect"
href="dependency-injection.html">Dependency Injection</a> which does not
require an in-depth knowledge of Spring + Spring Test or Guice.  Supports
JUnit 3.x (deprecated) and JUnit 4.x based tests.</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><a shape="rect"
href="cdi-testing.html">CDI Testing</a></td><td colspan="1" rowspan="1"
class="confluenceTd"><code>camel-test-cdi</code></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Provides a JUnit 4 runner that bootstraps a
test environment using CDI so that you don't have to be familiar with any CDI
testing frameworks and can concentrate on the testing logic of your Camel CDI
applications. Testing frameworks like <a shape="rect"
class="external-link" href="http://arquillian.org/";
rel="nofollow">Arquillian</a> or <a shape="rect"
class="external-link" href="https://
ops4j1.jira.com/wiki/display/PAXEXAM4" rel="nofollow">PAX Exam</a>, can be
used for more advanced test cases, where you need to configure your system
under test in a very fine-grained way or target specific CDI
containers.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><a shape="rect" href="spring-testing.html">Spring
Testing</a></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>camel-test-spring</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Supports JUnit 3.x (deprecated) or JUnit
4.x based tests that bootstrap a test environment using Spring without needing
to be familiar with Spring Test. The plain JUnit 3.x/4.x based tests work very
similar to the test support classes in <code>camel-test</code>.  Also
supports Spring Test based tests that use the declarative style of test
configuration and injection common in Spring Test.  The Spring Test based
tests provide feature parity with the plain JUnit 3.x/4.x based tes
ting approach.  Notice <code>camel-test-spring</code> is a new component
in <strong>Camel 2.10</strong> onwards. For older Camel release use
<code>camel-test</code> which has built-in <a shape="rect"
href="spring-testing.html">Spring Testing</a>.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><a shape="rect"
href="blueprint-testing.html">Blueprint Testing</a></p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>camel-test-blueprint</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.10:</strong>
Provides the ability to do unit testing on blueprint
configurations</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><a shape="rect" href="guice.html">Guice</a></p></td><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>camel-guice</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Uses <a shape="rect"
href="guice.html">Guice</a> to dependency inject your test classes</p></td></t
r><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Camel
TestNG</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>camel-testng</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Supports plain TestNG based tests with
or without <a shape="rect" href="spring.html">Spring</a> or <a
shape="rect" href="guice.html">Guice</a> for <a shape="rect"
href="dependency-injection.html">Dependency Injection</a> which does not
require an in-depth knowledge of Spring + Spring Test or Guice.  Also from
<strong>Camel 2.10</strong> onwards, this component supports Spring
Test based tests that use the declarative style of test configuration and
injection common in Spring Test and described in more detail under <a
shape="rect" href="spring-testing.html">Spring
Testing</a>.</p></td></tr></tbody></table></div><p>In all approaches the test
classes look pretty much the same in that they all reuse the <a shape="rect"
href="bean
-integration.html">Camel binding and injection annotations</a>.</p><h4
id="Bookcookbook-CamelTestExample">Camel Test Example</h4><p>Here is the <a
shape="rect" href="camel-test.html">Camel Test</a> <a shape="rect"
class="external-link"
href="http://svn.apache.org/repos/asf/camel/trunk/components/camel-test/src/test/java/org/apache/camel/test/patterns/FilterTest.java";>example</a>.</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[
public class FilterTest extends CamelTestSupport {
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 Mar 10 12:20:31
2016
@@ -2414,7 +2414,7 @@ public class IsMockEndpointsAndSkipJUnit
]]></script>
</div></div><div class="confluence-information-macro
confluence-information-macro-tip"><p class="title">time units</p><span
class="aui-icon aui-icon-small aui-iconfont-approve
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>In the example above we use
<code>seconds</code> as the time unit, but Camel offers
<code>milliseconds</code>, and <code>minutes</code> as
well.</p></div></div><p></p><h3 id="BookInOnePage-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><li><a
shape="rect" href="testing.html">Testing</a></li></ul>
-<h2 id="BookInOnePage-Testing">Testing</h2><p>Testing is a crucial activity in
any piece of software development or integration. Typically Camel Riders use
various different <a shape="rect" href="components.html">technologies</a> wired
together in a variety of <a shape="rect"
href="enterprise-integration-patterns.html">patterns</a> with different <a
shape="rect" href="languages.html">expression languages</a> together with
different forms of <a shape="rect" href="bean-integration.html">Bean
Integration</a> and <a shape="rect" href="dependency-injection.html">Dependency
Injection</a> so its very easy for things to go wrong! <img class="emoticon
emoticon-smile"
src="https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/smile.png";
data-emoticon-name="smile" alt="(smile)"> . Testing is the crucial weapon to
ensure that things work as you would expect.</p><p>Camel is a Java library so
you can easily wire up tests in whatever u
nit testing framework you use (JUnit 3.x (deprecated), 4.x, or TestNG).
However the Camel project has tried to make the testing of Camel as easy and
powerful as possible so we have introduced the following features.</p><h3
id="BookInOnePage-Testingmechanisms">Testing mechanisms</h3><p>The following
mechanisms are supported</p><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>Component</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><a shape="rect"
href="camel-test.html">Camel Test</a></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>camel-test</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Is a standalone Java library letting you
easily create Camel test cases using a single Java class for all your
configuration and routing
without using <a shape="rect" href="spring.html">Spring</a> or <a shape="rect"
href="guice.html">Guice</a> for <a shape="rect"
href="dependency-injection.html">Dependency Injection</a> which does not
require an in-depth knowledge of Spring + Spring Test or Guice.  Supports
JUnit 3.x (deprecated) and JUnit 4.x based tests.</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><a shape="rect"
href="cdi-testing.html">CDI Testing</a></td><td colspan="1" rowspan="1"
class="confluenceTd"><code>camel-test-cdi</code></td><td colspan="1"
rowspan="1" class="confluenceTd"><span style="color: rgb(0,0,0);">Provides a
JUnit 4 runner that bootstraps a test environment using CDI so that you don't
have to be familiar with any CDI testing frameworks and can concentrate on the
testing logic of your Camel CDI applications. Testing frameworks like <a
shape="rect" class="external-link" href="http://arquillian.org";
rel="nofollow">Arquillian</a> or <a shape="rect" class="external-link
" href="https://ops4j1.jira.com/wiki/display/PAXEXAM4"; rel="nofollow">PAX
Exam</a>, can be used for more advanced test cases, where you need to configure
your system under test in a very fine-grained way or target specific CDI
containers.</span></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><a shape="rect" href="spring-testing.html">Spring
Testing</a></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>camel-test-spring</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Supports JUnit 3.x (deprecated) or JUnit
4.x based tests that bootstrap a test environment using Spring without needing
to be familiar with Spring Test. The plain JUnit 3.x/4.x based tests work very
similar to the test support classes in <code>camel-test</code>.  Also
supports Spring Test based tests that use the declarative style of test
configuration and injection common in Spring Test.  The Spring Test based
tests provide feature parity with the plain JUni
t 3.x/4.x based testing approach.  Notice <code>camel-test-spring</code>
is a new component in <strong>Camel 2.10</strong> onwards. For older Camel
release use <code>camel-test</code> which has built-in <a shape="rect"
href="spring-testing.html">Spring Testing</a>.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><a shape="rect"
href="blueprint-testing.html">Blueprint Testing</a></p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>camel-test-blueprint</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.10:</strong>
Provides the ability to do unit testing on blueprint
configurations</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><a shape="rect" href="guice.html">Guice</a></p></td><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>camel-guice</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Uses <a shape="rect"
href="guice.html">Guice</a> to dependency inject your test
classes</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>Camel TestNG</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>camel-testng</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Supports plain TestNG based tests with
or without <a shape="rect" href="spring.html">Spring</a> or <a
shape="rect" href="guice.html">Guice</a> for <a shape="rect"
href="dependency-injection.html">Dependency Injection</a> which does not
require an in-depth knowledge of Spring + Spring Test or Guice.  Also from
<strong>Camel 2.10</strong> onwards, this component supports Spring
Test based tests that use the declarative style of test configuration and
injection common in Spring Test and described in more detail under <a
shape="rect" href="spring-testing.html">Spring
Testing</a>.</p></td></tr></tbody></table></div><p>In all approaches the test
classes look pretty much the same in that they all reuse the <a shap
e="rect" href="bean-integration.html">Camel binding and injection
annotations</a>.</p><h4 id="BookInOnePage-CamelTestExample">Camel Test
Example</h4><p>Here is the <a shape="rect" href="camel-test.html">Camel
Test</a> <a shape="rect" class="external-link"
href="http://svn.apache.org/repos/asf/camel/trunk/components/camel-test/src/test/java/org/apache/camel/test/patterns/FilterTest.java";>example</a>.</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+<h2 id="BookInOnePage-Testing">Testing</h2><p>Testing is a crucial activity in
any piece of software development or integration. Typically Camel Riders use
various different <a shape="rect" href="components.html">technologies</a> wired
together in a variety of <a shape="rect"
href="enterprise-integration-patterns.html">patterns</a> with different <a
shape="rect" href="languages.html">expression languages</a> together with
different forms of <a shape="rect" href="bean-integration.html">Bean
Integration</a> and <a shape="rect" href="dependency-injection.html">Dependency
Injection</a> so its very easy for things to go wrong! <img class="emoticon
emoticon-smile"
src="https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/smile.png";
data-emoticon-name="smile" alt="(smile)"> . Testing is the crucial weapon to
ensure that things work as you would expect.</p><p>Camel is a Java library so
you can easily wire up tests in whatever u
nit testing framework you use (JUnit 3.x (deprecated), 4.x, or TestNG).
However the Camel project has tried to make the testing of Camel as easy and
powerful as possible so we have introduced the following features.</p><h3
id="BookInOnePage-Testingmechanisms">Testing mechanisms</h3><p>The following
mechanisms are supported</p><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>Component</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><a shape="rect"
href="camel-test.html">Camel Test</a></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>camel-test</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Is a standalone Java library letting you
easily create Camel test cases using a single Java class for all your
configuration and routing
without using <a shape="rect" href="spring.html">Spring</a> or <a shape="rect"
href="guice.html">Guice</a> for <a shape="rect"
href="dependency-injection.html">Dependency Injection</a> which does not
require an in-depth knowledge of Spring + Spring Test or Guice.  Supports
JUnit 3.x (deprecated) and JUnit 4.x based tests.</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><a shape="rect"
href="cdi-testing.html">CDI Testing</a></td><td colspan="1" rowspan="1"
class="confluenceTd"><code>camel-test-cdi</code></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Provides a JUnit 4 runner that bootstraps a
test environment using CDI so that you don't have to be familiar with any CDI
testing frameworks and can concentrate on the testing logic of your Camel CDI
applications. Testing frameworks like <a shape="rect"
class="external-link" href="http://arquillian.org/";
rel="nofollow">Arquillian</a> or <a shape="rect"
class="external-link" href="https:
//ops4j1.jira.com/wiki/display/PAXEXAM4" rel="nofollow">PAX Exam</a>, can be
used for more advanced test cases, where you need to configure your system
under test in a very fine-grained way or target specific CDI
containers.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><a shape="rect" href="spring-testing.html">Spring
Testing</a></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>camel-test-spring</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Supports JUnit 3.x (deprecated) or JUnit
4.x based tests that bootstrap a test environment using Spring without needing
to be familiar with Spring Test. The plain JUnit 3.x/4.x based tests work very
similar to the test support classes in <code>camel-test</code>.  Also
supports Spring Test based tests that use the declarative style of test
configuration and injection common in Spring Test.  The Spring Test based
tests provide feature parity with the plain JUnit 3.x/4.x based t
esting approach.  Notice <code>camel-test-spring</code> is a new
component in <strong>Camel 2.10</strong> onwards. For older Camel release use
<code>camel-test</code> which has built-in <a shape="rect"
href="spring-testing.html">Spring Testing</a>.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><a shape="rect"
href="blueprint-testing.html">Blueprint Testing</a></p></td><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>camel-test-blueprint</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.10:</strong>
Provides the ability to do unit testing on blueprint
configurations</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><a shape="rect" href="guice.html">Guice</a></p></td><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>camel-guice</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Uses <a shape="rect"
href="guice.html">Guice</a> to dependency inject your test classes</p></td><
/tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Camel
TestNG</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>camel-testng</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Supports plain TestNG based tests with
or without <a shape="rect" href="spring.html">Spring</a> or <a
shape="rect" href="guice.html">Guice</a> for <a shape="rect"
href="dependency-injection.html">Dependency Injection</a> which does not
require an in-depth knowledge of Spring + Spring Test or Guice.  Also from
<strong>Camel 2.10</strong> onwards, this component supports Spring
Test based tests that use the declarative style of test configuration and
injection common in Spring Test and described in more detail under <a
shape="rect" href="spring-testing.html">Spring
Testing</a>.</p></td></tr></tbody></table></div><p>In all approaches the test
classes look pretty much the same in that they all reuse the <a shape="rect"
href="be
an-integration.html">Camel binding and injection annotations</a>.</p><h4
id="BookInOnePage-CamelTestExample">Camel Test Example</h4><p>Here is the <a
shape="rect" href="camel-test.html">Camel Test</a> <a shape="rect"
class="external-link"
href="http://svn.apache.org/repos/asf/camel/trunk/components/camel-test/src/test/java/org/apache/camel/test/patterns/FilterTest.java";>example</a>.</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[
public class FilterTest extends CamelTestSupport {
@@ -3670,11 +3670,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> </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.rbtoc1457608664766 {padding: 0px;}
-div.rbtoc1457608664766 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1457608664766 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1457612333109 {padding: 0px;}
+div.rbtoc1457612333109 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1457612333109 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1457608664766">
+/*]]>*/</style></p><div class="toc-macro rbtoc1457612333109">
<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>
@@ -5789,11 +5789,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.rbtoc1457608665361 {padding: 0px;}
-div.rbtoc1457608665361 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1457608665361 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1457612333576 {padding: 0px;}
+div.rbtoc1457612333576 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1457612333576 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="toc-macro rbtoc1457608665361">
+/*]]>*/</style><div class="toc-macro rbtoc1457612333576">
<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>
@@ -17248,11 +17248,11 @@ template.send("direct:alias-verify&
]]></script>
</div></div><p></p><h3 id="BookInOnePage-SeeAlso.28">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="crypto.html">Crypto</a> Crypto is also available as a <a
shape="rect" href="data-format.html">Data Format</a></li></ul> <h2
id="BookInOnePage-CXFComponent">CXF Component</h2><div
class="confluence-information-macro confluence-information-macro-note"><span
class="aui-icon aui-icon-small aui-iconfont-warning
confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>When using CXF as a consumer, the
<a shape="rect" href="cxf-bean-component.html">CXF Bean Component</a> allows
you to factor out how message payloads are received from their processing as a
RESTful or SOAP web service. This has the potential of using a multitude of
transports to consume web
services. The bean component's configuration is also simpler and provides the
fastest method to implement web services using Camel and
CXF.</p></div></div><div class="confluence-information-macro
confluence-information-macro-tip"><span class="aui-icon aui-icon-small
aui-iconfont-approve confluence-information-macro-icon"></span><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">/*<![CDATA[*/
-div.rbtoc1457608680688 {padding: 0px;}
-div.rbtoc1457608680688 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1457608680688 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1457612339164 {padding: 0px;}
+div.rbtoc1457612339164 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1457612339164 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1457608680688">
+/*]]>*/</style></p><div class="toc-macro rbtoc1457612339164">
<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>
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
![https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/smile.png"](https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/smile.png"){kind=link}