Author: buildbot
Date: Mon Sep 9 14:19:28 2013
New Revision: 877804
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/nmr.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 Mon Sep 9
14:19:28 2013
@@ -13071,7 +13071,7 @@ context.addRoutes(new RouteBuilder() {
<h2><a shape="rect" name="BookComponentAppendix-NMRComponent"></a>NMR
Component</h2>
-<p>The <b>nmr</b> component is an adapter to the Normalized Message Router
(NMR) in <a shape="rect" class="external-link"
href="http://servicemix.apache.org/home.html";>ServiceMix</a>, which is intended
for use by Camel applications deployed directly into the OSGi container. You
can exchange objects with NMR and not only XML like this is the case with the
JBI specification. The interest of this component is that you can interconnect
camel routes deployed in different OSGI bundles. </p>
+<p>The <b>nmr</b> component is an adapter to the Normalized Message Router
(NMR) in <a shape="rect" class="external-link"
href="http://servicemix.apache.org/home.html";>ServiceMix</a>, which is intended
for use by Camel applications deployed directly into the OSGi container. You
can exchange objects with NMR and not only XML like this is the case with the
JBI specification. The interest of this component is that you can interconnect
camel routes deployed in different OSGI bundles.</p>
<p>By contrast, the <a shape="rect" href="jbi.html" title="JBI">JBI</a>
component is intended for use by Camel applications deployed into the
ServiceMix JBI container.</p>
@@ -13139,6 +13139,7 @@ to("nmr:MyServiceEndpoint")
<p>The messages sent by this producer endpoint are sent to the already
deployed NMR endpoint.</p>
<p><a shape="rect" name="BookComponentAppendix-URIformat"></a></p>
+
<h3><a shape="rect" name="BookComponentAppendix-URIformat"></a>URI format</h3>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
@@ -13149,10 +13150,11 @@ nmr:endpointName
<h4><a shape="rect" name="BookComponentAppendix-URIOptions"></a>URI
Options</h4>
<div class="confluenceTableSmall"><div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Option </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>runAsSubject</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Apache ServiceMix 4.4:</b> When this is set to
<b><tt>true</tt></b> on a consumer endpoint, the endpoint will be invoked on
behalf of the <tt>Subject</tt> that is set on the <tt>Exchange</tt> (i.e. the
call to <tt>Subject.getSubject(AccessControlContext)</tt> will return the
<tt>Subject</tt> instance) </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>synchronous</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> When this is set to <b><tt>true</tt
></b> on a consumer endpoint, an incoming, synchronous NMR Exchange will be
>handled on the sender's thread instead of being handled on a new thread of
>the NMR endpoint's thread pool </td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"> <tt>timeout</tt> </td><td colspan="1" rowspan="1"
>class="confluenceTd"> <tt>0</tt> </td><td colspan="1" rowspan="1"
>class="confluenceTd"> <b>Apache ServiceMix 4.4:</b> When this is set to a
>value greater than 0, the producer endpoint will timeout if it doesn't
>receive a response from the NMR within the given timeout period (in
>milliseconds). Configuring a timeout value will switch to using synchronous
>interactions with the NMR instead of the usual asynchronous messaging.
></td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Option </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>runAsSubject</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Apache ServiceMix 4.4:</b> When this is set to
<tt><b>true</b></tt> on a consumer endpoint, the endpoint will be invoked on
behalf of the <tt>Subject</tt> that is set on the <tt>Exchange</tt> (i.e. the
call to <tt>Subject.getSubject(AccessControlContext)</tt> will return the
<tt>Subject</tt> instance) </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>synchronous</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> When this is set to <tt><b>true</b>
</tt> on a consumer endpoint, an incoming, synchronous NMR Exchange will be
handled on the sender's thread instead of being handled on a new thread of the
NMR endpoint's thread pool </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>timeout</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>0</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Apache ServiceMix 4.4:</b> When this is set to a value
greater than 0, the producer endpoint will timeout if it doesn't receive a
response from the NMR within the given timeout period (in milliseconds).
Configuring a timeout value will switch to using synchronous interactions with
the NMR instead of the usual asynchronous messaging. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>throwExceptionOnFailure</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> true </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>Apache ServiceMix 4.5.2:</b>
When this is set to <tt><b>fal
se</b></tt> then NMR's exceptions (like TimeoutException) will be consumed
silently. </td></tr></tbody></table>
</div>
</div>
+
<h4><a shape="rect" name="BookComponentAppendix-Examples"></a>Examples</h4>
<p>Consumer</p>
@@ -13172,6 +13174,7 @@ from()...to("nmr:MyServiceEndpoint?timeo
</div></div>
<h3><a shape="rect" name="BookComponentAppendix-UsingStreambodies"></a>Using
Stream bodies</h3>
+
<p>If you are using a stream type as the message body, you should be aware
that a stream is only capable of being read once. So if you enable
<tt>DEBUG</tt> logging, the body is usually logged and thus read. To deal with
this, Camel has a <tt>streamCaching</tt> option that can cache the stream,
enabling you to read it multiple times.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
@@ -13184,6 +13187,7 @@ from("nmr:MyEndpoint").streamCaching().t
We store big input streams (by default, over 64K) in a <tt>temp</tt> file
using <tt>CachedOutputStream</tt>. When you close the input stream, the temp
file will be deleted.</p>
<h4><a shape="rect" name="BookComponentAppendix-Testing"></a>Testing</h4>
+
<p>NMR camel routes can be tested using the camel unit test approach even if
they will be deployed next in different bundles on an OSGI runtime. With this
aim in view, you will extend the ServiceMixNMR Mock class
<tt>org.apache.servicemix.camel.nmr.AbstractComponentTest</tt> which will
create a NMR bus, register the Camel NMR Component and the endpoints defined
into the Camel routes.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
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 Mon Sep 9 14:19:28
2013
@@ -34472,7 +34472,7 @@ context.addRoutes(new RouteBuilder() {
<h2><a shape="rect" name="BookInOnePage-NMRComponent"></a>NMR Component</h2>
-<p>The <b>nmr</b> component is an adapter to the Normalized Message Router
(NMR) in <a shape="rect" class="external-link"
href="http://servicemix.apache.org/home.html";>ServiceMix</a>, which is intended
for use by Camel applications deployed directly into the OSGi container. You
can exchange objects with NMR and not only XML like this is the case with the
JBI specification. The interest of this component is that you can interconnect
camel routes deployed in different OSGI bundles. </p>
+<p>The <b>nmr</b> component is an adapter to the Normalized Message Router
(NMR) in <a shape="rect" class="external-link"
href="http://servicemix.apache.org/home.html";>ServiceMix</a>, which is intended
for use by Camel applications deployed directly into the OSGi container. You
can exchange objects with NMR and not only XML like this is the case with the
JBI specification. The interest of this component is that you can interconnect
camel routes deployed in different OSGI bundles.</p>
<p>By contrast, the <a shape="rect" href="jbi.html" title="JBI">JBI</a>
component is intended for use by Camel applications deployed into the
ServiceMix JBI container.</p>
@@ -34540,6 +34540,7 @@ to("nmr:MyServiceEndpoint")
<p>The messages sent by this producer endpoint are sent to the already
deployed NMR endpoint.</p>
<p><a shape="rect" name="BookInOnePage-URIformat"></a></p>
+
<h3><a shape="rect" name="BookInOnePage-URIformat"></a>URI format</h3>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
@@ -34550,10 +34551,11 @@ nmr:endpointName
<h4><a shape="rect" name="BookInOnePage-URIOptions"></a>URI Options</h4>
<div class="confluenceTableSmall"><div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Option </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>runAsSubject</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Apache ServiceMix 4.4:</b> When this is set to
<b><tt>true</tt></b> on a consumer endpoint, the endpoint will be invoked on
behalf of the <tt>Subject</tt> that is set on the <tt>Exchange</tt> (i.e. the
call to <tt>Subject.getSubject(AccessControlContext)</tt> will return the
<tt>Subject</tt> instance) </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>synchronous</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> When this is set to <b><tt>true</tt
></b> on a consumer endpoint, an incoming, synchronous NMR Exchange will be
>handled on the sender's thread instead of being handled on a new thread of
>the NMR endpoint's thread pool </td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"> <tt>timeout</tt> </td><td colspan="1" rowspan="1"
>class="confluenceTd"> <tt>0</tt> </td><td colspan="1" rowspan="1"
>class="confluenceTd"> <b>Apache ServiceMix 4.4:</b> When this is set to a
>value greater than 0, the producer endpoint will timeout if it doesn't
>receive a response from the NMR within the given timeout period (in
>milliseconds). Configuring a timeout value will switch to using synchronous
>interactions with the NMR instead of the usual asynchronous messaging.
></td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Option </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>runAsSubject</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Apache ServiceMix 4.4:</b> When this is set to
<tt><b>true</b></tt> on a consumer endpoint, the endpoint will be invoked on
behalf of the <tt>Subject</tt> that is set on the <tt>Exchange</tt> (i.e. the
call to <tt>Subject.getSubject(AccessControlContext)</tt> will return the
<tt>Subject</tt> instance) </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>synchronous</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> When this is set to <tt><b>true</b>
</tt> on a consumer endpoint, an incoming, synchronous NMR Exchange will be
handled on the sender's thread instead of being handled on a new thread of the
NMR endpoint's thread pool </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>timeout</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>0</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Apache ServiceMix 4.4:</b> When this is set to a value
greater than 0, the producer endpoint will timeout if it doesn't receive a
response from the NMR within the given timeout period (in milliseconds).
Configuring a timeout value will switch to using synchronous interactions with
the NMR instead of the usual asynchronous messaging. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>throwExceptionOnFailure</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> true </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>Apache ServiceMix 4.5.2:</b>
When this is set to <tt><b>fal
se</b></tt> then NMR's exceptions (like TimeoutException) will be consumed
silently. </td></tr></tbody></table>
</div>
</div>
+
<h4><a shape="rect" name="BookInOnePage-Examples"></a>Examples</h4>
<p>Consumer</p>
@@ -34573,6 +34575,7 @@ from()...to("nmr:MyServiceEndpoint?timeo
</div></div>
<h3><a shape="rect" name="BookInOnePage-UsingStreambodies"></a>Using Stream
bodies</h3>
+
<p>If you are using a stream type as the message body, you should be aware
that a stream is only capable of being read once. So if you enable
<tt>DEBUG</tt> logging, the body is usually logged and thus read. To deal with
this, Camel has a <tt>streamCaching</tt> option that can cache the stream,
enabling you to read it multiple times.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
@@ -34585,6 +34588,7 @@ from("nmr:MyEndpoint").streamCaching().t
We store big input streams (by default, over 64K) in a <tt>temp</tt> file
using <tt>CachedOutputStream</tt>. When you close the input stream, the temp
file will be deleted.</p>
<h4><a shape="rect" name="BookInOnePage-Testing"></a>Testing</h4>
+
<p>NMR camel routes can be tested using the camel unit test approach even if
they will be deployed next in different bundles on an OSGI runtime. With this
aim in view, you will extend the ServiceMixNMR Mock class
<tt>org.apache.servicemix.camel.nmr.AbstractComponentTest</tt> which will
create a NMR bus, register the Camel NMR Component and the endpoints defined
into the Camel routes.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/nmr.html
==============================================================================
--- websites/production/camel/content/nmr.html (original)
+++ websites/production/camel/content/nmr.html Mon Sep 9 14:19:28 2013
@@ -87,7 +87,7 @@
<td valign="top" width="100%">
<div class="wiki-content maincontent"><h2><a shape="rect"
name="NMR-NMRComponent"></a>NMR Component</h2>
-<p>The <b>nmr</b> component is an adapter to the Normalized Message Router
(NMR) in <a shape="rect" class="external-link"
href="http://servicemix.apache.org/home.html";>ServiceMix</a>, which is intended
for use by Camel applications deployed directly into the OSGi container. You
can exchange objects with NMR and not only XML like this is the case with the
JBI specification. The interest of this component is that you can interconnect
camel routes deployed in different OSGI bundles. </p>
+<p>The <b>nmr</b> component is an adapter to the Normalized Message Router
(NMR) in <a shape="rect" class="external-link"
href="http://servicemix.apache.org/home.html";>ServiceMix</a>, which is intended
for use by Camel applications deployed directly into the OSGi container. You
can exchange objects with NMR and not only XML like this is the case with the
JBI specification. The interest of this component is that you can interconnect
camel routes deployed in different OSGI bundles.</p>
<p>By contrast, the <a shape="rect" href="jbi.html" title="JBI">JBI</a>
component is intended for use by Camel applications deployed into the
ServiceMix JBI container.</p>
@@ -155,6 +155,7 @@ to("nmr:MyServiceEndpoint")
<p>The messages sent by this producer endpoint are sent to the already
deployed NMR endpoint.</p>
<p><a shape="rect" name="NMR-URIformat"></a></p>
+
<h3><a shape="rect" name="NMR-URIformat"></a>URI format</h3>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
@@ -165,10 +166,11 @@ nmr:endpointName
<h4><a shape="rect" name="NMR-URIOptions"></a>URI Options</h4>
<div class="confluenceTableSmall"><div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Option </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>runAsSubject</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Apache ServiceMix 4.4:</b> When this is set to
<b><tt>true</tt></b> on a consumer endpoint, the endpoint will be invoked on
behalf of the <tt>Subject</tt> that is set on the <tt>Exchange</tt> (i.e. the
call to <tt>Subject.getSubject(AccessControlContext)</tt> will return the
<tt>Subject</tt> instance) </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>synchronous</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> When this is set to <b><tt>true</tt
></b> on a consumer endpoint, an incoming, synchronous NMR Exchange will be
>handled on the sender's thread instead of being handled on a new thread of
>the NMR endpoint's thread pool </td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"> <tt>timeout</tt> </td><td colspan="1" rowspan="1"
>class="confluenceTd"> <tt>0</tt> </td><td colspan="1" rowspan="1"
>class="confluenceTd"> <b>Apache ServiceMix 4.4:</b> When this is set to a
>value greater than 0, the producer endpoint will timeout if it doesn't
>receive a response from the NMR within the given timeout period (in
>milliseconds). Configuring a timeout value will switch to using synchronous
>interactions with the NMR instead of the usual asynchronous messaging.
></td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Option </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>runAsSubject</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Apache ServiceMix 4.4:</b> When this is set to
<tt><b>true</b></tt> on a consumer endpoint, the endpoint will be invoked on
behalf of the <tt>Subject</tt> that is set on the <tt>Exchange</tt> (i.e. the
call to <tt>Subject.getSubject(AccessControlContext)</tt> will return the
<tt>Subject</tt> instance) </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>synchronous</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> When this is set to <tt><b>true</b>
</tt> on a consumer endpoint, an incoming, synchronous NMR Exchange will be
handled on the sender's thread instead of being handled on a new thread of the
NMR endpoint's thread pool </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>timeout</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>0</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Apache ServiceMix 4.4:</b> When this is set to a value
greater than 0, the producer endpoint will timeout if it doesn't receive a
response from the NMR within the given timeout period (in milliseconds).
Configuring a timeout value will switch to using synchronous interactions with
the NMR instead of the usual asynchronous messaging. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>throwExceptionOnFailure</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> true </td><td
colspan="1" rowspan="1" class="confluenceTd"> <b>Apache ServiceMix 4.5.2:</b>
When this is set to <tt><b>fal
se</b></tt> then NMR's exceptions (like TimeoutException) will be consumed
silently. </td></tr></tbody></table>
</div>
</div>
+
<h4><a shape="rect" name="NMR-Examples"></a>Examples</h4>
<p>Consumer</p>
@@ -188,6 +190,7 @@ from()...to("nmr:MyServiceEndpoint?timeo
</div></div>
<h3><a shape="rect" name="NMR-UsingStreambodies"></a>Using Stream bodies</h3>
+
<p>If you are using a stream type as the message body, you should be aware
that a stream is only capable of being read once. So if you enable
<tt>DEBUG</tt> logging, the body is usually logged and thus read. To deal with
this, Camel has a <tt>streamCaching</tt> option that can cache the stream,
enabling you to read it multiple times.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
@@ -200,6 +203,7 @@ from("nmr:MyEndpoint").streamCaching().t
We store big input streams (by default, over 64K) in a <tt>temp</tt> file
using <tt>CachedOutputStream</tt>. When you close the input stream, the temp
file will be deleted.</p>
<h4><a shape="rect" name="NMR-Testing"></a>Testing</h4>
+
<p>NMR camel routes can be tested using the camel unit test approach even if
they will be deployed next in different bundles on an OSGI runtime. With this
aim in view, you will extend the ServiceMixNMR Mock class
<tt>org.apache.servicemix.camel.nmr.AbstractComponentTest</tt> which will
create a NMR bus, register the Camel NMR Component and the endpoints defined
into the Camel routes.</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
