You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by bu...@apache.org on 2019/03/31 15:23:09 UTC
svn commit: r1042911 [28/48] - in /websites/production/camel/content: ./
2007/08/17/ 2008/04/08/ 2008/04/28/ 2009/01/19/ 2009/10/26/ 2012/01/17/
2012/03/01/ 2019/03/ 2019/03/31/
Modified: websites/production/camel/content/hiding-middleware.html
==============================================================================
--- websites/production/camel/content/hiding-middleware.html (original)
+++ websites/production/camel/content/hiding-middleware.html Sun Mar 31 15:23:07 2019
@@ -94,7 +94,7 @@
<p>The best approach when using remoting is to use <a shape="rect" href="spring-remoting.html">Spring Remoting</a> which can then use any messaging or remoting technology under the covers. When using Camel's implementation you can then use any of the Camel <a shape="rect" href="components.html">Components</a> along with any of the <a shape="rect" href="enterprise-integration-patterns.html">Enterprise Integration Patterns</a>.</p>
-<p>Another approach is to bind Java beans to Camel endpoints via the <a shape="rect" href="bean-integration.html">Bean Integration</a>. For example using <a shape="rect" href="pojo-consuming.html">POJO Consuming</a> and <a shape="rect" href="pojo-producing.html">POJO Producing</a> you can avoid using any Camel APIs to decouple your code both from middleware APIs <em>and</em> Camel APIs! <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/7701/d7b403a44466e5e8970db7530201039d865e79e1/_/images/icons/emoticons/smile.svg" data-emoticon-name="smile" alt="(smile)"></p></div>
+<p>Another approach is to bind Java beans to Camel endpoints via the <a shape="rect" href="bean-integration.html">Bean Integration</a>. For example using <a shape="rect" href="pojo-consuming.html">POJO Consuming</a> and <a shape="rect" href="pojo-producing.html">POJO Producing</a> you can avoid using any Camel APIs to decouple your code both from middleware APIs <em>and</em> Camel APIs! <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/7901/17fbf59dc6f69bee0caf86e0cbbd7fb3bd9d8b4a/_/images/icons/emoticons/smile.svg" data-emoticon-name="smile" alt="(smile)"></p></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/how-can-i-create-a-custom-component-or-endpoint.html
==============================================================================
--- websites/production/camel/content/how-can-i-create-a-custom-component-or-endpoint.html (original)
+++ websites/production/camel/content/how-can-i-create-a-custom-component-or-endpoint.html Sun Mar 31 15:23:07 2019
@@ -80,7 +80,7 @@
<td valign="top" width="100%">
<div class="wiki-content maincontent"><h2 id="HowcanIcreateacustomcomponentorendpoint-HowcanIcreateacustomcomponentorendpoint?">How can I create a custom component or endpoint?</h2>
-<p>Please read <a shape="rect" href="writing-components.html">Writing Components</a> for a background in how to implement a new component or endpoint. Its really easy to do! <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/7701/d7b403a44466e5e8970db7530201039d865e79e1/_/images/icons/emoticons/smile.svg" data-emoticon-name="smile" alt="(smile)"></p>
+<p>Please read <a shape="rect" href="writing-components.html">Writing Components</a> for a background in how to implement a new component or endpoint. Its really easy to do! <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/7901/17fbf59dc6f69bee0caf86e0cbbd7fb3bd9d8b4a/_/images/icons/emoticons/smile.svg" data-emoticon-name="smile" alt="(smile)"></p>
<h3 id="HowcanIcreateacustomcomponentorendpoint-SeeAlso">See Also</h3>
Modified: websites/production/camel/content/how-can-i-get-help.html
==============================================================================
--- websites/production/camel/content/how-can-i-get-help.html (original)
+++ websites/production/camel/content/how-can-i-get-help.html Sun Mar 31 15:23:07 2019
@@ -78,7 +78,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h2 id="HowcanIgethelp-GettingHelp">Getting Help</h2><p>If you are experiencing problems using Camel then please report your problem to our mailing list. This allows the entire community to help with your problem. If indeed a bug has been identified in the Camel software, then document the problem in our <a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/CAMEL">Issue Tracker</a>. Please refrain from immediately opening a ticket in the issue tracker unless you are certain it's a problem in the Camel software. If you are in doubt, we appreciate asking the <a shape="rect" class="external-link" href="http://camel.apache.org/mailing-lists.html">mailing list</a>, <a shape="rect" class="external-link" href="http://camel.apache.org/irc-room.html">IRC chat</a>, or <a shape="rect" class="external-link" href="https://gitter.im/apache/apache-cam
el" rel="nofollow">Gitter chat</a> first.</p><div class="confluence-information-macro confluence-information-macro-tip conf-macro output-block" data-hasbody="true" data-macro-name="tip"><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p>Please read the section below (<em>How to get help</em>), and follow the bullets advised there first.</p></div></div><div class="confluence-information-macro confluence-information-macro-information conf-macro output-block" data-hasbody="true" data-macro-name="info"><p class="title">Reporting bugs - Please read this first</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p>We prefer people to get in touch first using the <a shape="rect" class="external-link" href="http://camel.apache.org/mailing-lists.html">mailing list</a>, <a shape="rect" class="externa
l-link" href="http://camel.apache.org/irc-room.html">IRC chat</a> or <a shape="rect" class="external-link" href="https://gitter.im/apache/apache-camel" rel="nofollow">Gitter chat</a>. Or take time to read FAQs, or search in the mailing list archives to find answers.<br clear="none"> Unfortunately some people create a JIRA ticket as first thing. Please don't do that! Only if you are sure it really is a bug etc. JIRA tickets create noise<br clear="none"> for the Camel team to react on issues that are not bugs. But already covered in FAQs, in the mailing lists etc. Or in the existing documentation.<br clear="none"> Also on the mailing lists there is more people active to help you better.</p></div></div><ul><li><a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/CAMEL">Issue Tracker</a></li><li><a shape="rect" href="faq.html">FAQ</a></li></ul><h3 id="HowcanIgethelp-Alternativediscussionforums">Alternative discussion forums</h3><p>There's a number of sites ou
tside Apache that offer discussion forums on Camel. For example, <a shape="rect" class="external-link" href="http://stackoverflow.com/" rel="nofollow">Stack Overflow</a> is a popular Q & A site with a <a shape="rect" class="external-link" href="http://stackoverflow.com/questions/tagged/apache-camel" rel="nofollow">dedicated Apache Camel forum</a>. You are also likely to find helpful discussions on technical blogs, on <a shape="rect" class="external-link" href="https://www.google.com/search?q=apache+camel" rel="nofollow">Google</a>, or even on <a shape="rect" class="external-link" href="https://twitter.com/#!/search/apache%20camel" rel="nofollow">Twitter</a>.</p><h3 id="HowcanIgethelp-Usingdeprecatedcomponents">Using deprecated components</h3><p>Deprecated components are <strong>not</strong> supported and issues such as bugs may not be fixed. We encourage users to migrate away from using any deprecated component. A list of deprecated components is listed on the git
hub page at: <a shape="rect" class="external-link" href="https://github.com/apache/camel/tree/master/components#components" rel="nofollow">https://github.com/apache/camel/tree/master/components#components</a></p><h3 id="HowcanIgethelp-Howtogethelp">How to get help</h3><p>Before you report a problem, you may wish to read the <a shape="rect" href="faq.html">FAQ</a>. <br clear="none"> When you report an issue, please be sure to include as much information as possible. The more we know, the easier it is to reach an effective solution quickly.</p><div class="confluence-information-macro confluence-information-macro-note conf-macro output-block" data-hasbody="true" data-macro-name="note"><p class="title">What version do you use</p><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p>What version of Camel do you use! Remember to include this information.</p></div></div><ul><li><strong>wha
t are the version numbers of involved software components?</strong> (this is very important to detail)</li><li>what platform and JDK?</li><li>any particular container being used? and if so, what version?</li><li>stack traces generally really help! (<strong>Remember to post which version of Camel you use, this is important to know when posting stacktraces</strong>) If in doubt, include the whole thing; often exceptions get wrapped in other exceptions and the exception right near the bottom explains the actual error, not the first few lines at the top. It's very easy for us to skim-read past unnecessary parts of a stack trace.</li><li>log output can be useful too; sometimes <a shape="rect" href="how-do-i-change-the-logging.html">enabling DEBUG logging</a> can help</li><li>your code & configuration files are often useful</li><li>did it work before? what have you changed to break it?</li><li>try upgrading to the latest release and see if it's fixed there</li><li>try the latest SNAPS
HOT to see if it's fixed in the pre-release</li><li>search the user forum to see if has been discussed before</li><li>see the "known issues" section in the release notes</li><li>and check the <a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/CAMEL">issue tracker</a> to see if the issue has already been reported</li><li>do <strong>not</strong> send private emails to Camel <a shape="rect" href="team.html">Team</a> members to ask them to help you faster, or in the private only. Help on Apache Camel is volunteer based and <strong>must</strong> happen in the <strong>open</strong> on the public <a shape="rect" href="mailing-lists.html">Mailing Lists</a>. If you want to get help faster or in private, then see further below.</li></ul><h3 id="HowcanIgethelp-Howtogethelpfaster">How to get help faster</h3><p>We can help you much quicker if you try the following</p><ul><li>provide us with a JUnit test case that demonstrates your issue. e.g. if you think you'v
e found a bug, can you create a test case to demonstrate the bug?</li><li><a shape="rect" class="external-link" href="http://camel.apache.org/contributing.html">submit a patch</a> fixing the bug! (We also buy you beer when we meet you if you submit bug fixes <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/7701/d7b403a44466e5e8970db7530201039d865e79e1/_/images/icons/emoticons/smile.svg" data-emoticon-name="smile" alt="(smile)"> )</li><li>for memory leak or performance related issues, if you can run a profiler on your test case and attach the output as a file (or zipped file if it's huge) to the JIRA we can normally fix things much faster. e.g. you could run <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jmap.html" rel="nofollow">jmap</a>/<a shape="rect" class="external-link" href="http://java.sun.com/javase/6/docs/technotes/tools/share/jhat.html" rel="nofollow">jhat</a>, JProfiler or YourKit on your
code and send us the output. To find memory leaks it's quicker to resolve if you can tell us what classes are taking up all of the RAM; we can normally figure out what's wrong from that.</li></ul><h2 id="HowcanIgethelp-CommercialSupport">Commercial Support</h2><p>This is an open source project, so the amount of time we have available to help resolve your issue is often limited as all help is provided on a volunteer basis. If you want to get priority help, need to get up to speed quickly, require some training or mentoring, or need full 24 x 7 production support you could contact one of the following companies with <a shape="rect" href="commercial-camel-offerings.html">Commercial Camel Offerings</a>.</p></div></div>
+<div class="wiki-content maincontent"><div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h2 id="HowcanIgethelp-GettingHelp">Getting Help</h2><p>If you are experiencing problems using Camel then please report your problem to our mailing list. This allows the entire community to help with your problem. If indeed a bug has been identified in the Camel software, then document the problem in our <a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/CAMEL">Issue Tracker</a>. Please refrain from immediately opening a ticket in the issue tracker unless you are certain it's a problem in the Camel software. If you are in doubt, we appreciate asking the <a shape="rect" class="external-link" href="http://camel.apache.org/mailing-lists.html">mailing list</a>, <a shape="rect" class="external-link" href="http://camel.apache.org/irc-room.html">IRC chat</a>, or <a shape="rect" class="external-link" href="https://gitter.im/apache/apache-cam
el" rel="nofollow">Gitter chat</a> first.</p><div class="confluence-information-macro confluence-information-macro-tip conf-macro output-block" data-hasbody="true" data-macro-name="tip"><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p>Please read the section below (<em>How to get help</em>), and follow the bullets advised there first.</p></div></div><div class="confluence-information-macro confluence-information-macro-information conf-macro output-block" data-hasbody="true" data-macro-name="info"><p class="title">Reporting bugs - Please read this first</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p>We prefer people to get in touch first using the <a shape="rect" class="external-link" href="http://camel.apache.org/mailing-lists.html">mailing list</a>, <a shape="rect" class="externa
l-link" href="http://camel.apache.org/irc-room.html">IRC chat</a> or <a shape="rect" class="external-link" href="https://gitter.im/apache/apache-camel" rel="nofollow">Gitter chat</a>. Or take time to read FAQs, or search in the mailing list archives to find answers.<br clear="none"> Unfortunately some people create a JIRA ticket as first thing. Please don't do that! Only if you are sure it really is a bug etc. JIRA tickets create noise<br clear="none"> for the Camel team to react on issues that are not bugs. But already covered in FAQs, in the mailing lists etc. Or in the existing documentation.<br clear="none"> Also on the mailing lists there is more people active to help you better.</p></div></div><ul><li><a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/CAMEL">Issue Tracker</a></li><li><a shape="rect" href="faq.html">FAQ</a></li></ul><h3 id="HowcanIgethelp-Alternativediscussionforums">Alternative discussion forums</h3><p>There's a number of sites ou
tside Apache that offer discussion forums on Camel. For example, <a shape="rect" class="external-link" href="http://stackoverflow.com/" rel="nofollow">Stack Overflow</a> is a popular Q & A site with a <a shape="rect" class="external-link" href="http://stackoverflow.com/questions/tagged/apache-camel" rel="nofollow">dedicated Apache Camel forum</a>. You are also likely to find helpful discussions on technical blogs, on <a shape="rect" class="external-link" href="https://www.google.com/search?q=apache+camel" rel="nofollow">Google</a>, or even on <a shape="rect" class="external-link" href="https://twitter.com/#!/search/apache%20camel" rel="nofollow">Twitter</a>.</p><h3 id="HowcanIgethelp-Usingdeprecatedcomponents">Using deprecated components</h3><p>Deprecated components are <strong>not</strong> supported and issues such as bugs may not be fixed. We encourage users to migrate away from using any deprecated component. A list of deprecated components is listed on the git
hub page at: <a shape="rect" class="external-link" href="https://github.com/apache/camel/tree/master/components#components" rel="nofollow">https://github.com/apache/camel/tree/master/components#components</a></p><h3 id="HowcanIgethelp-Howtogethelp">How to get help</h3><p>Before you report a problem, you may wish to read the <a shape="rect" href="faq.html">FAQ</a>. <br clear="none"> When you report an issue, please be sure to include as much information as possible. The more we know, the easier it is to reach an effective solution quickly.</p><div class="confluence-information-macro confluence-information-macro-note conf-macro output-block" data-hasbody="true" data-macro-name="note"><p class="title">What version do you use</p><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p>What version of Camel do you use! Remember to include this information.</p></div></div><ul><li><strong>wha
t are the version numbers of involved software components?</strong> (this is very important to detail)</li><li>what platform and JDK?</li><li>any particular container being used? and if so, what version?</li><li>stack traces generally really help! (<strong>Remember to post which version of Camel you use, this is important to know when posting stacktraces</strong>) If in doubt, include the whole thing; often exceptions get wrapped in other exceptions and the exception right near the bottom explains the actual error, not the first few lines at the top. It's very easy for us to skim-read past unnecessary parts of a stack trace.</li><li>log output can be useful too; sometimes <a shape="rect" href="how-do-i-change-the-logging.html">enabling DEBUG logging</a> can help</li><li>your code & configuration files are often useful</li><li>did it work before? what have you changed to break it?</li><li>try upgrading to the latest release and see if it's fixed there</li><li>try the latest SNAPS
HOT to see if it's fixed in the pre-release</li><li>search the user forum to see if has been discussed before</li><li>see the "known issues" section in the release notes</li><li>and check the <a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/CAMEL">issue tracker</a> to see if the issue has already been reported</li><li>do <strong>not</strong> send private emails to Camel <a shape="rect" href="team.html">Team</a> members to ask them to help you faster, or in the private only. Help on Apache Camel is volunteer based and <strong>must</strong> happen in the <strong>open</strong> on the public <a shape="rect" href="mailing-lists.html">Mailing Lists</a>. If you want to get help faster or in private, then see further below.</li></ul><h3 id="HowcanIgethelp-Howtogethelpfaster">How to get help faster</h3><p>We can help you much quicker if you try the following</p><ul><li>provide us with a JUnit test case that demonstrates your issue. e.g. if you think you'v
e found a bug, can you create a test case to demonstrate the bug?</li><li><a shape="rect" class="external-link" href="http://camel.apache.org/contributing.html">submit a patch</a> fixing the bug! (We also buy you beer when we meet you if you submit bug fixes <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/7901/17fbf59dc6f69bee0caf86e0cbbd7fb3bd9d8b4a/_/images/icons/emoticons/smile.svg" data-emoticon-name="smile" alt="(smile)"> )</li><li>for memory leak or performance related issues, if you can run a profiler on your test case and attach the output as a file (or zipped file if it's huge) to the JIRA we can normally fix things much faster. e.g. you could run <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jmap.html" rel="nofollow">jmap</a>/<a shape="rect" class="external-link" href="http://java.sun.com/javase/6/docs/technotes/tools/share/jhat.html" rel="nofollow">jhat</a>, JProfiler or YourKit on your
code and send us the output. To find memory leaks it's quicker to resolve if you can tell us what classes are taking up all of the RAM; we can normally figure out what's wrong from that.</li></ul><h2 id="HowcanIgethelp-CommercialSupport">Commercial Support</h2><p>This is an open source project, so the amount of time we have available to help resolve your issue is often limited as all help is provided on a volunteer basis. If you want to get priority help, need to get up to speed quickly, require some training or mentoring, or need full 24 x 7 production support you could contact one of the following companies with <a shape="rect" href="commercial-camel-offerings.html">Commercial Camel Offerings</a>.</p></div></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/how-can-i-get-the-source-code.html
==============================================================================
--- websites/production/camel/content/how-can-i-get-the-source-code.html (original)
+++ websites/production/camel/content/how-can-i-get-the-source-code.html Sun Mar 31 15:23:07 2019
@@ -89,11 +89,11 @@
<tr>
<td valign="top" width="100%">
<div class="wiki-content maincontent">
-<div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><div class="confluence-information-macro confluence-information-macro-warning conf-macro output-block" data-hasbody="true" data-macro-name="warning"><p class="title">Warning</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p>Apache Camel code repository was moved to git, The old svn repo will not be updated.</p></div></div><h2 id="HowcanIgetthesourcecode-WebBrowsingofgit">Web Browsing of git</h2><p>To browse via the web:</p><div class="panel conf-macro output-block" data-hasbody="true" data-macro-name="panel" style="border-width: 1px;"><div class="panelContent">
+<div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><div class="confluence-information-macro confluence-information-macro-warning conf-macro output-block" data-hasbody="true" data-macro-name="warning"><p class="title">Warning</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p>Apache Camel code repository was moved to git, The old svn repo will not be updated.</p></div></div><h2 id="HowcanIgetthesourcecode-WebBrowsingofgit">Web Browsing of git</h2><p>To browse via the web:</p><div class="panel conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="panel"><div class="panelContent">
<p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=camel.git">https://git-wip-us.apache.org/repos/asf?p=camel.git</a></p>
-</div></div><h3 id="HowcanIgetthesourcecode-WebBrowingUsingFishEye">Web Browing Using FishEye</h3><p>A hearty thanks to <a shape="rect" class="external-link" href="http://atlassian.com/" rel="nofollow">Atlassian</a> for providing <a shape="rect" class="external-link" href="http://cenqua.com/fisheye/" rel="nofollow">FishEye</a> hosting for Camel. Below is the URL to browse the Subversion repo via FishEye:</p><div class="panel conf-macro output-block" data-hasbody="true" data-macro-name="panel" style="border-width: 1px;"><div class="panelContent">
+</div></div><h3 id="HowcanIgetthesourcecode-WebBrowingUsingFishEye">Web Browing Using FishEye</h3><p>A hearty thanks to <a shape="rect" class="external-link" href="http://atlassian.com/" rel="nofollow">Atlassian</a> for providing <a shape="rect" class="external-link" href="http://cenqua.com/fisheye/" rel="nofollow">FishEye</a> hosting for Camel. Below is the URL to browse the Subversion repo via FishEye:</p><div class="panel conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="panel"><div class="panelContent">
<p><a shape="rect" class="external-link" href="https://fisheye6.atlassian.com/browse/camel-git" rel="nofollow">https://fisheye6.atlassian.com/browse/camel-git</a></p>
-</div></div><h2 id="HowcanIgetthesourcecode-Checkingoutfromgit">Checking out from git</h2><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h2 id="HowcanIgetthesourcecode-Checkingoutfromgit">Checking out from git</h2><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">git clone https://git-wip-us.apache.org/repos/asf/camel.git
</pre>
</div></div><p>Only project developers can commit to the git via this method. SSH must be installed on your client machine. Enter your site password when prompted.</p><h2 id="HowcanIgetthesourcecode-Usinggithub">Using github</h2><p>The source code is <a shape="rect" class="external-link" href="https://github.com/apache/camel/" rel="nofollow">mirrored to github</a>, so you can also checkout the source code from github, if you are familiar with using github. By using github you can submit pull requests to the project using the standard github way.</p><ul><li><a shape="rect" class="external-link" href="https://github.com/apache/camel/" rel="nofollow">https://github.com/apache/camel/</a></li></ul><h2 id="HowcanIgetthesourcecode-Buildingthecode">Building the code</h2><p>To then build the code see <a shape="rect" href="building.html">Building</a>.</p></div></div>
Modified: websites/production/camel/content/how-do-i-disable-jmx.html
==============================================================================
--- websites/production/camel/content/how-do-i-disable-jmx.html (original)
+++ websites/production/camel/content/how-do-i-disable-jmx.html Sun Mar 31 15:23:07 2019
@@ -90,13 +90,13 @@
<div class="wiki-content maincontent"><h2 id="HowdoIdisableJMX-HowdoIdisableJMX?">How do I disable JMX?</h2>
<p>You can disable JMX instrumentation agent by setting Java VM system property as follow. The property value is treated as boolean.</p>
-<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
-Dorg.apache.camel.jmx.disabled=true
</pre>
</div></div>
<p>Or, by adding a jmxAgent element inside the camelContext element in Spring configuration:</p>
-<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
<camelContext id="camel" xmlns="http://camel.apache.org/schema/spring">
<jmxAgent id="agent" disabled="true"/>
@@ -105,7 +105,7 @@
</pre>
</div></div>
<p>Or in Camel 2.1 its a bit easier (not having to use JVM system property) if using pure Java as you can disable it as follows:</p>
-<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
CamelContext camel = new DefaultCamelContext();
camel.disableJMX();
Modified: websites/production/camel/content/how-do-i-handle-failures-when-consuming-for-example-from-a-ftp-server.html
==============================================================================
--- websites/production/camel/content/how-do-i-handle-failures-when-consuming-for-example-from-a-ftp-server.html (original)
+++ websites/production/camel/content/how-do-i-handle-failures-when-consuming-for-example-from-a-ftp-server.html Sun Mar 31 15:23:07 2019
@@ -90,7 +90,7 @@
<div class="wiki-content maincontent"><h2 id="HowdoIhandlefailureswhenconsumingforexamplefromaFTPserver-HowdoIhandlefailureswhenconsumingforexamplefromaFTPserver">How do I handle failures when consuming for example from a FTP server</h2>
<p>When you do a route such as</p>
-<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
from("ftp://foo@somesever.com?password=secret").to("bean:logic?method=doSomething");
</pre>
Modified: websites/production/camel/content/how-do-i-invoke-camel-routes-from-jbi.html
==============================================================================
--- websites/production/camel/content/how-do-i-invoke-camel-routes-from-jbi.html (original)
+++ websites/production/camel/content/how-do-i-invoke-camel-routes-from-jbi.html Sun Mar 31 15:23:07 2019
@@ -91,7 +91,7 @@
<p>When you use the <a shape="rect" href="jbi.html">JBI</a> endpoint as follows</p>
-<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
from("jbi:endpoint:http://foo.bar.org/MyService/MyEndpoint")
</pre>
@@ -99,7 +99,7 @@ from("jbi:endpoint:http://foo.bar.org/My
<p>you automatically expose the endpoint to the NMR bus where service qname is </p>
-<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
{http://foo.bar.org}MyService
</pre>
@@ -111,7 +111,7 @@ from("jbi:endpoint:http://foo.bar.org/My
<p>Sending works in the same way: you use </p>
-<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
to("jbi:endpoint:http://foo.bar.org/MyService/MyEndpoint")
Modified: websites/production/camel/content/how-do-i-reuse-the-contexttestsupport-class-in-my-unit-tests.html
==============================================================================
--- websites/production/camel/content/how-do-i-reuse-the-contexttestsupport-class-in-my-unit-tests.html (original)
+++ websites/production/camel/content/how-do-i-reuse-the-contexttestsupport-class-in-my-unit-tests.html Sun Mar 31 15:23:07 2019
@@ -97,7 +97,7 @@
<p>ContextTestSupport :</p>
-<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
<dependency>
<groupId>org.apache.camel</groupId>
@@ -111,7 +111,7 @@
<p>SpringTestSupport:</p>
-<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
<dependency>
<groupId>org.apache.camel</groupId>
Modified: websites/production/camel/content/how-do-i-run-camel-using-java-webstart.html
==============================================================================
--- websites/production/camel/content/how-do-i-run-camel-using-java-webstart.html (original)
+++ websites/production/camel/content/how-do-i-run-camel-using-java-webstart.html Sun Mar 31 15:23:07 2019
@@ -101,7 +101,7 @@
<a shape="rect" class="external-link" href="http://mojo.codehaus.org/webstart/webstart-maven-plugin/" rel="nofollow">http://mojo.codehaus.org/webstart/webstart-maven-plugin/</a></p>
<p>You need to configure your maven to not output the jar version attribute (<code>outputJarVersion=false</code>) as started in this snippet</p>
-<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
<plugin>
<groupId>org.codehaus.mojo.webstart</groupId>
@@ -138,7 +138,7 @@
</div></div>
<p>And a sample of the generated <strong>appl.jnlp</strong> file:</p>
-<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
<jnlp .....>
.......
Modified: websites/production/camel/content/how-do-i-use-java-14-logging.html
==============================================================================
--- websites/production/camel/content/how-do-i-use-java-14-logging.html (original)
+++ websites/production/camel/content/how-do-i-use-java-14-logging.html Sun Mar 31 15:23:07 2019
@@ -94,14 +94,14 @@
<p>The quick way to enable Java 1.4 logging is to create a <strong>commons-logging.properties</strong> file on the classpath with this entry...</p>
-<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
org.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger
#org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger
</pre>
</div></div>
-<p>Many thanks to Glen Mazza for figuring this out <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/7701/d7b403a44466e5e8970db7530201039d865e79e1/_/images/icons/emoticons/smile.svg" data-emoticon-name="smile" alt="(smile)"></p></div>
+<p>Many thanks to Glen Mazza for figuring this out <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/7901/17fbf59dc6f69bee0caf86e0cbbd7fb3bd9d8b4a/_/images/icons/emoticons/smile.svg" data-emoticon-name="smile" alt="(smile)"></p></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/camel/content/how-do-i-use-log4j.html
==============================================================================
--- websites/production/camel/content/how-do-i-use-log4j.html (original)
+++ websites/production/camel/content/how-do-i-use-log4j.html Sun Mar 31 15:23:07 2019
@@ -94,7 +94,7 @@
<p>The quick way to enable Log4j is to add log4j to your classpath or maven pom.xml. For example the following in your pom.xml should do the trick</p>
-<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
<dependencies>
<dependency>
@@ -113,7 +113,7 @@
<p>Here's an example log4j.properties file</p>
-<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
log4j.rootLogger=INFO, out
Modified: websites/production/camel/content/how-to-avoid-importing-bunch-of-cxf-packages-when-start-up-the-camel-cxf-endpoint-from-osgi-platform-.html
==============================================================================
--- websites/production/camel/content/how-to-avoid-importing-bunch-of-cxf-packages-when-start-up-the-camel-cxf-endpoint-from-osgi-platform-.html (original)
+++ websites/production/camel/content/how-to-avoid-importing-bunch-of-cxf-packages-when-start-up-the-camel-cxf-endpoint-from-osgi-platform-.html Sun Mar 31 15:23:07 2019
@@ -94,7 +94,7 @@ This is the code snippet to show to crea
<p><strong>NOTE</strong>, if you have other CXF configuration which want to be load, you need to make sure the thread context class loader can load it. </p>
-<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
ClassLoader oldCL = Thread.currentThread().getContextClassLoader();
try {
@@ -115,7 +115,7 @@ try {
<p>From Camel 2.2.0, we introduced a SpringBusFactoryBean which leverage the BusApplicationContext will use the BusApplicationContext.class classloader as a fall back classloader, so you can configure the SpringBusFactoryBean and set the bus directly into the camel-cxf endpoint without using any java code. The Spring configuration snippet is below:<br clear="none">
<strong>NOTE</strong><br clear="none">
If you are using URI to specify the camel-cxf endpoint , you can set the URI with bus option like this "cxf://ADDRESS?bus=myBus&...".</p>
-<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
Modified: websites/production/camel/content/how-to-send-the-same-message-to-multiple-endpoints.html
==============================================================================
--- websites/production/camel/content/how-to-send-the-same-message-to-multiple-endpoints.html (original)
+++ websites/production/camel/content/how-to-send-the-same-message-to-multiple-endpoints.html Sun Mar 31 15:23:07 2019
@@ -92,7 +92,7 @@
<p>When you need to send the <strong>same</strong> message to multiple endpoints then you should use <a shape="rect" href="multicast.html">Multicast</a>.</p>
<p>In the sample below we consume messages from the activemq queue <code>foo</code> and want to send the <strong>same message</strong> to both <code>seda:foo</code> and <code>seda:bar</code>. Sending the same message requires that we use <a shape="rect" href="multicast.html">Multicast</a>. This is done by adding the <code>multicast()</code> before the to type:</p>
-<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
from("activemq:queue:foo").multicast().to("seda:foo", "seda:bar");
</pre>
@@ -100,7 +100,7 @@ from("activemq:queue:foo").multicast().t
<div class="confluence-information-macro confluence-information-macro-tip conf-macro output-block" data-hasbody="true" data-macro-name="tip"><p class="title">Pipeline is default in Camel</p><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"> </span><div class="confluence-information-macro-body">
<p>If you have a route such as:</p>
-<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
from("activemq:queue:foo").to("seda:foo", "seda:bar");
</pre>
Modified: websites/production/camel/content/how-to-validate-the-camel-1x-context-xml-from-apache-camel-web-site.html
==============================================================================
--- websites/production/camel/content/how-to-validate-the-camel-1x-context-xml-from-apache-camel-web-site.html (original)
+++ websites/production/camel/content/how-to-validate-the-camel-1x-context-xml-from-apache-camel-web-site.html Sun Mar 31 15:23:07 2019
@@ -93,7 +93,7 @@
<p>To walk around this issue, you just need to specify the schema version in your Spring configuration's schemaLocation attribute.</p>
-<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
Modified: websites/production/camel/content/http-session-handling.html
==============================================================================
--- websites/production/camel/content/http-session-handling.html (original)
+++ websites/production/camel/content/http-session-handling.html Sun Mar 31 15:23:07 2019
@@ -87,7 +87,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><p><strong>Available as of Camel 2.19</strong></p><p>Several Camel components can use HTTP as the underlying transport protocol. In general HTTP calls are stateless in nature, however some servers allow to maintain state via cookies. Cookies are often used to maintain a server session (e.g. via a session cookie called "JSESSIONID" with servers implementing the JEE Servlet specification).</p><h1 id="HTTP-SessionHandling-SessionScope">Session Scope</h1><p>If a Camel route intends to implement some kind of HTTP session handling the scope of this session should be considered.</p><p>Independently from the session scope the implementation must honor the domain of<br clear="none">the handled cookies.</p><h2 id="HTTP-SessionHandling-Route/ContextScope">Route/Context Scope</h2><p>It might be desirable to have a single session for a route or a <a shape="rect" href="camelcontext.html">CamelContext</a>. This essentially means that all calls to a server issu
ed from a route or CamelContext share a single HTTP session.</p><h2 id="HTTP-SessionHandling-EndpointScope">Endpoint Scope</h2><p>It is also possible to have a session on an <a shape="rect" href="endpoint.html">Endpoint</a> entity. This would mean that all invocations of an HTTP call issued by a single Endpoint share a session, whereas different Endpoints never share sessions, even if the call is sent to the same server.<br clear="none"><br clear="none">Some components like camel-http, and camel-http4 support endpoint scoped sessions even prior to version 2.19.</p><h2 id="HTTP-SessionHandling-ExchangeScope">Exchange Scope</h2><p>The third option to define a session scope is on <a shape="rect" href="exchange.html">Exchange </a>level. This is particularly useful for scenarios where the server session is really maintaining state.</p><p>In this case the route could e.g. first do a login call, then some update calls and finally a logout call. If the session handling would be defined on r
oute or CamelContext scopes this would seem to run, however under load parallel invocations of the route would share a <strong>single</strong> session, which could cause issues. If the session is defined on exchange scope, each invocation of the route will get a separate session and the server can maintain a separate state for the different parallel invocations.</p><h1 id="HTTP-SessionHandling-Usage">Usage</h1><p>If you are a Camel user, you see that several Camel components support the cookieHandler parameter on endpoint level. All you need to do is to instantiate a cookie handler  appropriate for your use case and reference it in the cookieHandler parameter for all endpoints that are supposed to participate in the HTTP session.</p><p>There are two pre-implemented cookie handlers: <code>org.apache.camel.http.common.cookie.InstanceCookieHandler</code> and <code>org.apache.camel.http.common.cookie.ExchangeCookieHandler.</code></p><p>The <code>InstanceCookieHandler</code> stores&
#160; cookies in an instance of itself. You can compare that with a browser instance that is shared between all the endpoints that use it (and will be used for all invocations of these endpoints). If you want to maintain separate sessions for different endpoints or groups of endpoints you may have multiple instances of the <code>InstanceCookieHandler</code>.</p><p>The <code>ExchangeCookieHandler</code> stores the session in the exchange. With the browser analogy this means that each Exchange will get its own browser instance (so sessions are separated). As the <code>ExchangeCookieHandler</code> does not store any state it is generally not useful to have multiple <code>ExchangeCookieHandler</code> instances (as they would access the same data, anyway).</p><h2 id="HTTP-SessionHandling-Example">Example</h2><p>The following three routes will each do two invocations of an echo REST service. In the first route (without a cookie handler) each invocation will get a new session. For the seco
nd route all invocations will share a session. For the third route the first and the second invocation within the route share a session, but different (even parallel) invocations of the route will not share a session.</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="wiki-content maincontent"><p><strong>Available as of Camel 2.19</strong></p><p>Several Camel components can use HTTP as the underlying transport protocol. In general HTTP calls are stateless in nature, however some servers allow to maintain state via cookies. Cookies are often used to maintain a server session (e.g. via a session cookie called "JSESSIONID" with servers implementing the JEE Servlet specification).</p><h1 id="HTTP-SessionHandling-SessionScope">Session Scope</h1><p>If a Camel route intends to implement some kind of HTTP session handling the scope of this session should be considered.</p><p>Independently from the session scope the implementation must honor the domain of<br clear="none">the handled cookies.</p><h2 id="HTTP-SessionHandling-Route/ContextScope">Route/Context Scope</h2><p>It might be desirable to have a single session for a route or a <a shape="rect" href="camelcontext.html">CamelContext</a>. This essentially means that all calls to a server issu
ed from a route or CamelContext share a single HTTP session.</p><h2 id="HTTP-SessionHandling-EndpointScope">Endpoint Scope</h2><p>It is also possible to have a session on an <a shape="rect" href="endpoint.html">Endpoint</a> entity. This would mean that all invocations of an HTTP call issued by a single Endpoint share a session, whereas different Endpoints never share sessions, even if the call is sent to the same server.<br clear="none"><br clear="none">Some components like camel-http, and camel-http4 support endpoint scoped sessions even prior to version 2.19.</p><h2 id="HTTP-SessionHandling-ExchangeScope">Exchange Scope</h2><p>The third option to define a session scope is on <a shape="rect" href="exchange.html">Exchange </a>level. This is particularly useful for scenarios where the server session is really maintaining state.</p><p>In this case the route could e.g. first do a login call, then some update calls and finally a logout call. If the session handling would be defined on r
oute or CamelContext scopes this would seem to run, however under load parallel invocations of the route would share a <strong>single</strong> session, which could cause issues. If the session is defined on exchange scope, each invocation of the route will get a separate session and the server can maintain a separate state for the different parallel invocations.</p><h1 id="HTTP-SessionHandling-Usage">Usage</h1><p>If you are a Camel user, you see that several Camel components support the cookieHandler parameter on endpoint level. All you need to do is to instantiate a cookie handler  appropriate for your use case and reference it in the cookieHandler parameter for all endpoints that are supposed to participate in the HTTP session.</p><p>There are two pre-implemented cookie handlers: <code>org.apache.camel.http.common.cookie.InstanceCookieHandler</code> and <code>org.apache.camel.http.common.cookie.ExchangeCookieHandler.</code></p><p>The <code>InstanceCookieHandler</code> stores&
#160; cookies in an instance of itself. You can compare that with a browser instance that is shared between all the endpoints that use it (and will be used for all invocations of these endpoints). If you want to maintain separate sessions for different endpoints or groups of endpoints you may have multiple instances of the <code>InstanceCookieHandler</code>.</p><p>The <code>ExchangeCookieHandler</code> stores the session in the exchange. With the browser analogy this means that each Exchange will get its own browser instance (so sessions are separated). As the <code>ExchangeCookieHandler</code> does not store any state it is generally not useful to have multiple <code>ExchangeCookieHandler</code> instances (as they would access the same data, anyway).</p><h2 id="HTTP-SessionHandling-Example">Example</h2><p>The following three routes will each do two invocations of an echo REST service. In the first route (without a cookie handler) each invocation will get a new session. For the seco
nd route all invocations will share a session. For the third route the first and the second invocation within the route share a session, but different (even parallel) invocations of the route will not share a session.</p><div class="code panel pdl conf-macro output-block" style="border-width: 1px;" data-hasbody="true" data-macro-name="code"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: xml; gutter: false; theme: Default" data-theme="Default"> <cxf:rsClient id="rsClientProxy" address="http://127.0.0.1:8080/CxfRsProducerSessionTest/"
serviceClass="org.apache.camel.component.cxf.jaxrs.testbean.EchoService"
loggingFeatureEnabled="true" />