Modified: websites/production/camel/content/book-pattern-appendix.html ============================================================================== --- websites/production/camel/content/book-pattern-appendix.html (original) +++ websites/production/camel/content/book-pattern-appendix.html Thu Dec 19 02:22:12 2013 @@ -6318,54 +6318,23 @@ from("direct:start").choice() <h4 id="BookPatternAppendix-UsingThisPattern.46">Using This Pattern</h4> <p>If you would like to use this EIP Pattern then please read the <a shape="rect" href="getting-started.html">Getting Started</a>, you may also find the <a shape="rect" href="architecture.html">Architecture</a> useful particularly the description of <a shape="rect" href="endpoint.html">Endpoint</a> and <a shape="rect" href="uris.html">URIs</a>. Then you could try out some of the <a shape="rect" href="examples.html">Examples</a> first before trying this pattern out.</p> -<h3 id="BookPatternAppendix-WireTap">Wire Tap</h3> - -<p><a shape="rect" class="external-link" href="http://www.enterpriseintegrationpatterns.com/WireTap.html"; rel="nofollow">Wire Tap</a> (from the <a shape="rect" href="enterprise-integration-patterns.html">EIP patterns</a>) allows you to route messages to a separate location while they are being forwarded to the ultimate destination.</p> - -<p><img class="confluence-embedded-image confluence-external-resource" src="http://www.enterpriseintegrationpatterns.com/img/WireTap.gif"; data-image-src="http://www.enterpriseintegrationpatterns.com/img/WireTap.gif";></p> - - <div class="aui-message hint shadowed information-macro"> +<h3 id="BookPatternAppendix-WireTap">Wire Tap</h3><p><a shape="rect" class="external-link" href="http://www.enterpriseintegrationpatterns.com/WireTap.html"; rel="nofollow">Wire Tap</a> (from the <a shape="rect" href="enterprise-integration-patterns.html">EIP patterns</a>) allows you to route messages to a separate location while they are being forwarded to the ultimate destination.</p><p><img class="confluence-embedded-image confluence-external-resource" src="http://www.enterpriseintegrationpatterns.com/img/WireTap.gif"; data-image-src="http://www.enterpriseintegrationpatterns.com/img/WireTap.gif";></p> <div class="aui-message hint shadowed information-macro"> <p class="title">Streams</p> <span class="aui-icon icon-hint">Icon</span> <div class="message-content"> - -<p>If you <a shape="rect" href="wire-tap.html">Wire Tap</a> a stream message body then you should consider enabling <a shape="rect" href="stream-caching.html">Stream Caching</a> to ensure the message body can be read at each endpoint. See more details at <a shape="rect" href="stream-caching.html">Stream Caching</a>. </p> + <p>If you <a shape="rect" href="wire-tap.html">Wire Tap</a> a stream message body then you should consider enabling <a shape="rect" href="stream-caching.html">Stream caching</a> to ensure the message body can be read at each endpoint. See more details at <a shape="rect" href="stream-caching.html">Stream caching</a>.</p> </div> </div> - - -<h3 id="BookPatternAppendix-Options.11">Options</h3> - -<div class="confluenceTableSmall"> +<h3 id="BookPatternAppendix-Options.11">Options</h3><div class="confluenceTableSmall"> <table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>uri</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The URI of the endpoint to which the wire-tapped message will be sent. You should use either <code>uri</code> or <code>ref</code>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>ref</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Reference identifier of the endpoint to which the wire-tapped message will be sent. You should use either <code>uri</code> or <code>ref</code>. </p></td></tr><tr><td colspan="1" rows pan="1" class="confluenceTd"><p> <code>executorServiceRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Reference identifier of a custom <a shape="rect" href="threading-model.html" title="Threading Model">Thread Pool</a> to use when processing the wire-tapped messages. If not set, Camel will use a default thread pool. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>processorRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Reference identifier of a custom <a shape="rect" href="processor.html" title="Processor">Processor</a> to use for creating a new message (e.g., the "send a new message" mode). See below. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>copy</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>true</code> </p>< /td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.3</strong>: Whether to copy the <a shape="rect" href="exchange.html" title="Exchange">Exchange</a> before wire-tapping the message. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <code>onPrepareRef</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Camel 2.8:</strong> Reference identifier of a custom <a shape="rect" href="processor.html" title="Processor">Processor</a> to prepare the copy of the <a shape="rect" href="exchange.html" title="Exchange">Exchange</a> to be wire-tapped. This allows you to do any custom logic, such as deep-cloning the message payload. </p></td></tr></tbody></table> -</div> - - -<h3 id="BookPatternAppendix-WireTapthreadpool">WireTap thread pool</h3> - -<p>The <a shape="rect" href="wire-tap.html">Wire Tap</a> uses a thread pool to process the tapped messages. This thread pool will by default use the settings detailed at <a shape="rect" href="threading-model.html">Threading Model</a>. In particular, when the pool is exhausted (with all threads utilized), further wiretaps will be executed synchronously by the calling thread. To remedy this, you can configure an explicit thread pool on the <a shape="rect" href="wire-tap.html">Wire Tap</a> having either a different rejection policy, a larger worker queue, or more worker threads.</p> - -<h3 id="BookPatternAppendix-WireTapnode">WireTap node</h3> - -<p>Camel's Wire Tap node supports two flavors when tapping an <a shape="rect" href="exchange.html">Exchange</a>:</p> - -<p>-With the traditional Wire Tap, Camel will copy the original <a shape="rect" href="exchange.html">Exchange</a> and set its <a shape="rect" href="exchange-pattern.html">Exchange Pattern</a> to <strong>InOnly</strong>, as we want the tapped <a shape="rect" href="exchange.html">Exchange</a> to be sent in a <em>fire and forget</em> style. The tapped <a shape="rect" href="exchange.html">Exchange</a> is then sent in a separate thread so it can run in parallel with the original.</p> - -<p>-Camel also provides an option of sending a new <a shape="rect" href="exchange.html">Exchange</a> allowing you to populate it with new values.</p> - -<h4 id="BookPatternAppendix-Sendingacopy(traditionalwiretap)">Sending a copy (traditional wiretap)</h4> -<p><strong>Using the <a shape="rect" href="fluent-builders.html">Fluent Builders</a></strong></p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> +</div><h3 id="BookPatternAppendix-WireTapthreadpool">WireTap thread pool</h3><p>The <a shape="rect" href="wire-tap.html">Wire Tap</a> uses a thread pool to process the tapped messages. This thread pool will by default use the settings detailed at <a shape="rect" href="threading-model.html">Threading Model</a>. In particular, when the pool is exhausted (with all threads utilized), further wiretaps will be executed synchronously by the calling thread. To remedy this, you can configure an explicit thread pool on the <a shape="rect" href="wire-tap.html">Wire Tap</a> having either a different rejection policy, a larger worker queue, or more worker threads.</p><h3 id="BookPatternAppendix-WireTapnode">WireTap node</h3><p>Camel's Wire Tap node supports two flavors when tapping an <a shape="rect" href="exchange.html">Exchange</a>:</p><p>-With the traditional Wire Tap, Camel will copy the original <a shape="rect" href="exchange.html">Exchange</a> and set its <a shape="rect" href="exchange-pat tern.html">Exchange Pattern</a> to <strong>InOnly</strong>, as we want the tapped <a shape="rect" href="exchange.html">Exchange</a> to be sent in a <em>fire and forget</em> style. The tapped <a shape="rect" href="exchange.html">Exchange</a> is then sent in a separate thread so it can run in parallel with the original.</p><p>-Camel also provides an option of sending a new <a shape="rect" href="exchange.html">Exchange</a> allowing you to populate it with new values.</p><h4 id="BookPatternAppendix-Sendingacopy(traditionalwiretap)">Sending a copy (traditional wiretap)</h4><p><strong>Using the <a shape="rect" href="fluent-builders.html">Fluent Builders</a></strong></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ from("direct:start") .to("log:foo") .wireTap("direct:tap") .to("mock:result"); ]]></script> -</div></div> - -<p><strong>Using the <a shape="rect" href="spring-xml-extensions.html">Spring XML Extensions</a></strong></p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> +</div></div><p><strong>Using the <a shape="rect" href="spring-xml-extensions.html">Spring XML Extensions</a></strong></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[ <route> <from uri="direct:start"/> @@ -6374,16 +6343,7 @@ from("direct:start") <to uri="mock:result"/> </route> ]]></script> -</div></div> - -<h4 id="BookPatternAppendix-Sendinganew">Sending a new <a shape="rect" href="exchange.html">Exchange</a></h4> -<p><strong>Using the <a shape="rect" href="fluent-builders.html">Fluent Builders</a></strong><br clear="none"> -Camel supports either a processor or an <a shape="rect" href="expression.html">Expression</a> to populate the new <a shape="rect" href="exchange.html">Exchange</a>. Using a processor gives you full power over how the <a shape="rect" href="exchange.html">Exchange</a> is populated as you can set properties, headers, et cetera. An <a shape="rect" href="expression.html">Expression</a> can only be used to set the IN body. </p> - -<p>From <strong>Camel 2.3</strong> onwards the <a shape="rect" href="expression.html">Expression</a> or <a shape="rect" href="processor.html">Processor</a> is pre-populated with a copy of the original <a shape="rect" href="exchange.html">Exchange</a>, which allows you to access the original message when you prepare a new <a shape="rect" href="exchange.html">Exchange</a> to be sent. You can use the <code>copy</code> option (enabled by default) to indicate whether you want this. If you set <code>copy=false</code>, then it works as in Camel 2.2 or older where the <a shape="rect" href="exchange.html">Exchange</a> will be empty.</p> - -<p>Below is the processor variation. This example is from Camel 2.3, where we disable <code>copy</code> by passing in <code>false</code> to create a new, empty <a shape="rect" href="exchange.html">Exchange</a>. </p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> +</div></div><h4 id="BookPatternAppendix-Sendinganew">Sending a new <a shape="rect" href="exchange.html">Exchange</a></h4><p><strong>Using the <a shape="rect" href="fluent-builders.html">Fluent Builders</a></strong><br clear="none"> Camel supports either a processor or an <a shape="rect" href="expression.html">Expression</a> to populate the new <a shape="rect" href="exchange.html">Exchange</a>. Using a processor gives you full power over how the <a shape="rect" href="exchange.html">Exchange</a> is populated as you can set properties, headers, et cetera. An <a shape="rect" href="expression.html">Expression</a> can only be used to set the IN body.</p><p>From <strong>Camel 2.3</strong> onwards the <a shape="rect" href="expression.html">Expression</a> or <a shape="rect" href="processor.html">Processor</a> is pre-populated with a copy of the original <a shape="rect" href="exchange.html">Exchange</a>, which allows you to access the original message when you prepare a new <a shape="rect" hr ef="exchange.html">Exchange</a> to be sent. You can use the <code>copy</code> option (enabled by default) to indicate whether you want this. If you set <code>copy=false</code>, then it works as in Camel 2.2 or older where the <a shape="rect" href="exchange.html">Exchange</a> will be empty.</p><p>Below is the processor variation. This example is from Camel 2.3, where we disable <code>copy</code> by passing in <code>false</code> to create a new, empty <a shape="rect" href="exchange.html">Exchange</a>.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ from("direct:start") .wireTap("direct:foo", false, new Processor() { @@ -6396,10 +6356,7 @@ from("direct:start") from("direct:foo").to("mock:foo"); ]]></script> -</div></div> - -<p>Here is the <a shape="rect" href="expression.html">Expression</a> variation. This example is from Camel 2.3, where we disable <code>copy</code> by passing in <code>false</code> to create a new, empty <a shape="rect" href="exchange.html">Exchange</a>. </p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> +</div></div><p>Here is the <a shape="rect" href="expression.html">Expression</a> variation. This example is from Camel 2.3, where we disable <code>copy</code> by passing in <code>false</code> to create a new, empty <a shape="rect" href="exchange.html">Exchange</a>.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ from("direct:start") .wireTap("direct:foo", false, constant("Bye World")) @@ -6407,11 +6364,7 @@ from("direct:start") from("direct:foo").to("mock:foo"); ]]></script> -</div></div> - -<p><strong>Using the <a shape="rect" href="spring-xml-extensions.html">Spring XML Extensions</a></strong><br clear="none"> -The processor variation, which uses a <strong>processorRef</strong> attribute to refer to a Spring bean by ID: </p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> +</div></div><p><strong>Using the <a shape="rect" href="spring-xml-extensions.html">Spring XML Extensions</a></strong><br clear="none"> The processor variation, which uses a <strong>processorRef</strong> attribute to refer to a Spring bean by ID:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[ <route> <from uri="direct:start2"/> @@ -6419,10 +6372,7 @@ The processor variation, which uses a <s <to uri="mock:result"/> </route> ]]></script> -</div></div> - -<p>Here is the <a shape="rect" href="expression.html">Expression</a> variation, where the expression is defined in the <strong>body</strong> tag: </p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> +</div></div><p>Here is the <a shape="rect" href="expression.html">Expression</a> variation, where the expression is defined in the <strong>body</strong> tag:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[ <route> <from uri="direct:start"/> @@ -6432,10 +6382,7 @@ The processor variation, which uses a <s <to uri="mock:result"/> </route> ]]></script> -</div></div> - -<p>This variation accesses the body of the original message and creates a new <a shape="rect" href="exchange.html">Exchange</a> based on the <a shape="rect" href="expression.html">Expression</a>. It will create a new Exchange and have the body contain <code>"Bye ORIGINAL BODY MESSAGE HERE"</code></p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> +</div></div><p>This variation accesses the body of the original message and creates a new <a shape="rect" href="exchange.html">Exchange</a> based on the <a shape="rect" href="expression.html">Expression</a>. It will create a new Exchange and have the body contain <code>"Bye ORIGINAL BODY MESSAGE HERE"</code></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[ <route> <from uri="direct:start"/> @@ -6445,23 +6392,7 @@ The processor variation, which uses a <s <to uri="mock:result"/> </route> ]]></script> -</div></div> - -<h4 id="BookPatternAppendix-FurtherExample">Further Example</h4> - -<p>For another example of this pattern, refer to the <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/camel/trunk/camel-core/src/test/java/org/apache/camel/processor/WireTapTest.java";>wire tap test case</a>.</p> - -<h3 id="BookPatternAppendix-SendinganewandsetheadersinDSL">Sending a new <a shape="rect" href="exchange.html">Exchange</a> and set headers in DSL</h3> -<p><strong>Available as of Camel 2.8</strong></p> - -<p>If you send a new message using <a shape="rect" href="wire-tap.html">Wire Tap</a>, then you could only set the message body using an <a shape="rect" href="expression.html">Expression</a> from the DSL. If you also need to set headers, you would have to use a <a shape="rect" href="processor.html">Processor</a>. In Camel 2.8 onwards, you can now set headers as well in the DSL.</p> - -<p>The following example sends a new message which has</p> -<ul class="alternate"><li>"Bye World" as message body</li><li>a header with key "id" with the value 123</li><li>a header with key "date" which has current date as value</li></ul> - - -<h4 id="BookPatternAppendix-JavaDSL.1">Java DSL</h4> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> +</div></div><h4 id="BookPatternAppendix-FurtherExample">Further Example</h4><p>For another example of this pattern, refer to the <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/camel/trunk/camel-core/src/test/java/org/apache/camel/processor/WireTapTest.java";>wire tap test case</a>.</p><h3 id="BookPatternAppendix-SendinganewandsetheadersinDSL">Sending a new <a shape="rect" href="exchange.html">Exchange</a> and set headers in DSL</h3><p><strong>Available as of Camel 2.8</strong></p><p>If you send a new message using <a shape="rect" href="wire-tap.html">Wire Tap</a>, then you could only set the message body using an <a shape="rect" href="expression.html">Expression</a> from the DSL. If you also need to set headers, you would have to use a <a shape="rect" href="processor.html">Processor</a>. In Camel 2.8 onwards, you can now set headers as well in the DSL.</p><p>The following example sends a new message which has</p><ul class="alternate"><li>"Bye World" as me ssage body</li><li>a header with key "id" with the value 123</li><li>a header with key "date" which has current date as value</li></ul><h4 id="BookPatternAppendix-JavaDSL.1">Java DSL</h4><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ from("direct:start") // tap a new message and send it to direct:tap @@ -6479,11 +6410,7 @@ from("direct:start") from("direct:tap") .to("mock:tap"); ]]></script> -</div></div> - -<h4 id="BookPatternAppendix-XMLDSL">XML DSL</h4> -<p>The XML DSL is slightly different than Java DSL in how you configure the message body and headers using <body> and <setHeader>:</p> -<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> +</div></div><h4 id="BookPatternAppendix-XMLDSL">XML DSL</h4><p>The XML DSL is slightly different than Java DSL in how you configure the message body and headers using <body> and <setHeader>:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[ <route> <from uri="direct:start"/> @@ -6499,16 +6426,7 @@ from("direct:tap") <to uri="mock:result"/> </route> ]]></script> -</div></div> - - -<h3 id="BookPatternAppendix-UsingonPreparetoexecutecustomlogicwhenpreparingmessages.3">Using onPrepare to execute custom logic when preparing messages</h3> -<p><strong>Available as of Camel 2.8</strong></p> - -<p>See details at <a shape="rect" href="multicast.html">Multicast</a></p> - - -<h4 id="BookPatternAppendix-UsingThisPattern.47">Using This Pattern</h4> +</div></div><h3 id="BookPatternAppendix-UsingonPreparetoexecutecustomlogicwhenpreparingmessages.3">Using onPrepare to execute custom logic when preparing messages</h3><p><strong>Available as of Camel 2.8</strong></p><p>See details at <a shape="rect" href="multicast.html">Multicast</a></p><p></p><h4 id="BookPatternAppendix-UsingThisPattern.47">Using This Pattern</h4> <p>If you would like to use this EIP Pattern then please read the <a shape="rect" href="getting-started.html">Getting Started</a>, you may also find the <a shape="rect" href="architecture.html">Architecture</a> useful particularly the description of <a shape="rect" href="endpoint.html">Endpoint</a> and <a shape="rect" href="uris.html">URIs</a>. Then you could try out some of the <a shape="rect" href="examples.html">Examples</a> first before trying this pattern out.</p> <h2 id="BookPatternAppendix-Log">Log</h2>
Modified: websites/production/camel/content/book-tutorials.html ============================================================================== --- websites/production/camel/content/book-tutorials.html (original) +++ websites/production/camel/content/book-tutorials.html Thu Dec 19 02:22:12 2013 @@ -166,11 +166,11 @@ While not actual tutorials you might fin <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> <style type="text/css">/*<![CDATA[*/ -div.rbtoc1387228946717 {padding: 0px;} -div.rbtoc1387228946717 ul {list-style: disc;margin-left: 0px;} -div.rbtoc1387228946717 li {margin-left: 0px;padding-left: 0px;} +div.rbtoc1387419662105 {padding: 0px;} +div.rbtoc1387419662105 ul {list-style: disc;margin-left: 0px;} +div.rbtoc1387419662105 li {margin-left: 0px;padding-left: 0px;} -/*]]>*/</style><div class="toc-macro rbtoc1387228946717"> +/*]]>*/</style><div class="toc-macro rbtoc1387419662105"> <ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-JmsRemoting-TutorialonSpringRemotingwithJMS">Tutorial on Spring Remoting with JMS</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-Preface">Preface</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-Prerequisites">Prerequisites</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-Distribution">Distribution</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-About">About</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-CreatetheCamelProject">Create the Camel Project</a> <ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-JmsRemoting-UpdatethePOMwithDependencies">Update the POM with Dependencies</a></li></ul> </li><li><a shape="rect" href="#Tutorial-JmsRemoting-WritingtheServer">Writing the Server</a> @@ -2511,11 +2511,11 @@ So we completed the last piece in the pi <style type="text/css">/*<![CDATA[*/ -div.rbtoc1387228946913 {padding: 0px;} -div.rbtoc1387228946913 ul {list-style: disc;margin-left: 0px;} -div.rbtoc1387228946913 li {margin-left: 0px;padding-left: 0px;} +div.rbtoc1387419662314 {padding: 0px;} +div.rbtoc1387419662314 ul {list-style: disc;margin-left: 0px;} +div.rbtoc1387419662314 li {margin-left: 0px;padding-left: 0px;} -/*]]>*/</style><div class="toc-macro rbtoc1387228946913"> +/*]]>*/</style><div class="toc-macro rbtoc1387419662314"> <ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-AXIS-Camel-TutorialusingAxis1.4withApacheCamel">Tutorial using Axis 1.4 with Apache Camel</a> <ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-AXIS-Camel-Prerequisites">Prerequisites</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-Distribution">Distribution</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-Introduction">Introduction</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-SettinguptheprojecttorunAxis">Setting up the project to run Axis</a> <ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-AXIS-Camel-Maven2">Maven 2</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-wsdl">wsdl</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-ConfiguringAxis">Configuring Axis</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-RunningtheExample">Running the Example</a></li></ul> Added: websites/production/camel/content/cache/main.pageCache ============================================================================== Binary file - no diff available. Propchange: websites/production/camel/content/cache/main.pageCache ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Modified: websites/production/camel/content/camel-30-ideas.html ============================================================================== --- websites/production/camel/content/camel-30-ideas.html (original) +++ websites/production/camel/content/camel-30-ideas.html Thu Dec 19 02:22:12 2013 @@ -109,11 +109,11 @@ <div class="sectionMacroRow"><div class="columnMacro" style="width:20%;min-width:20%;max-width:20%;"> <div class="panel" style="border-width: 1px;"><div class="panelContent"> <style type="text/css">/*<![CDATA[*/ -div.rbtoc1387228844845 {padding: 0px;} -div.rbtoc1387228844845 ul {list-style: disc;margin-left: 0px;} -div.rbtoc1387228844845 li {margin-left: 0px;padding-left: 0px;} +div.rbtoc1387419629924 {padding: 0px;} +div.rbtoc1387419629924 ul {list-style: disc;margin-left: 0px;} +div.rbtoc1387419629924 li {margin-left: 0px;padding-left: 0px;} -/*]]>*/</style><div class="toc-macro rbtoc1387228844845"> +/*]]>*/</style><div class="toc-macro rbtoc1387419629924"> <ul class="toc-indentation"><li><a shape="rect" href="#Camel3.0-Ideas-Camel3.0Ideas">Camel 3.0 Ideas</a> <ul class="toc-indentation"><li><a shape="rect" href="#Camel3.0-Ideas-Tableofcontents">Table of contents</a></li><li><a shape="rect" href="#Camel3.0-Ideas-JDKsupport">JDK support</a></li><li><a shape="rect" href="#Camel3.0-Ideas-JDK8JavaDSL">JDK8 Java DSL</a></li><li><a shape="rect" href="#Camel3.0-Ideas-RoutingCoreRe-engineering(raulk)">Routing Core Re-engineering (raulk)</a> <ul class="toc-indentation"><li><a shape="rect" href="#Camel3.0-Ideas-ConvertingsomeEIPsfrom"performers"tomere"deciders"">Converting some EIPs from "performers" to mere "deciders"</a></li></ul> Modified: websites/production/camel/content/camel-jmx.html ============================================================================== --- websites/production/camel/content/camel-jmx.html (original) +++ websites/production/camel/content/camel-jmx.html Thu Dec 19 02:22:12 2013 @@ -93,11 +93,11 @@ Camel also provides a <a shape="rect" hr <h3 id="CamelJMX-ActivatingJMXinCamel">Activating JMX in Camel</h3> <style type="text/css">/*<![CDATA[*/ -div.rbtoc1387228830479 {padding: 0px;} -div.rbtoc1387228830479 ul {list-style: disc;margin-left: 0px;} -div.rbtoc1387228830479 li {margin-left: 0px;padding-left: 0px;} +div.rbtoc1387419625374 {padding: 0px;} +div.rbtoc1387419625374 ul {list-style: disc;margin-left: 0px;} +div.rbtoc1387419625374 li {margin-left: 0px;padding-left: 0px;} -/*]]>*/</style><div class="toc-macro rbtoc1387228830479"> +/*]]>*/</style><div class="toc-macro rbtoc1387419625374"> <ul class="toc-indentation"><li><a shape="rect" href="#CamelJMX-CamelJMX">Camel JMX</a> <ul class="toc-indentation"><li><a shape="rect" href="#CamelJMX-ActivatingJMXinCamel">Activating JMX in Camel</a> <ul class="toc-indentation"><li><a shape="rect" href="#CamelJMX-UsingJMXtomanageApacheCamel">Using JMX to manage Apache Camel</a></li><li><a shape="rect" href="#CamelJMX-DisablingJMXinstrumentationagentinCamel">Disabling JMX instrumentation agent in Camel</a></li><li><a shape="rect" href="#CamelJMX-LocatingaMBeanServerintheJavaVM">Locating a MBeanServer in the Java VM</a></li><li><a shape="rect" href="#CamelJMX-CreatingJMXRMIConnectorServer">Creating JMX RMI Connector Server</a></li><li><a shape="rect" href="#CamelJMX-JMXServiceURL">JMX Service URL</a></li><li><a shape="rect" href="#CamelJMX-TheSystemPropertiesforCamelJMXsupport">The System Properties for Camel JMX support</a></li><li><a shape="rect" href="#CamelJMX-HowtouseauthenticationwithJMX">How to use authentication with JMX</a></li><li><a shape="rect" href="#CamelJMX-JMXinsideanApplicationServer">JMX inside an Application Server</a> Modified: websites/production/camel/content/cxf.html ============================================================================== --- websites/production/camel/content/cxf.html (original) +++ websites/production/camel/content/cxf.html Thu Dec 19 02:22:12 2013 @@ -108,11 +108,11 @@ <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> <style type="text/css">/*<![CDATA[*/ -div.rbtoc1387228888321 {padding: 0px;} -div.rbtoc1387228888321 ul {list-style: disc;margin-left: 0px;} -div.rbtoc1387228888321 li {margin-left: 0px;padding-left: 0px;} +div.rbtoc1387419644309 {padding: 0px;} +div.rbtoc1387419644309 ul {list-style: disc;margin-left: 0px;} +div.rbtoc1387419644309 li {margin-left: 0px;padding-left: 0px;} -/*]]>*/</style><div class="toc-macro rbtoc1387228888321"> +/*]]>*/</style><div class="toc-macro rbtoc1387419644309"> <ul class="toc-indentation"><li><a shape="rect" href="#CXF-CXFComponent">CXF Component</a> <ul class="toc-indentation"><li><a shape="rect" href="#CXF-URIformat">URI format</a></li><li><a shape="rect" href="#CXF-Options">Options</a> <ul class="toc-indentation"><li><a shape="rect" href="#CXF-Thedescriptionsofthedataformats">The descriptions of the dataformats</a> Modified: websites/production/camel/content/disruptor.html ============================================================================== --- websites/production/camel/content/disruptor.html (original) +++ websites/production/camel/content/disruptor.html Thu Dec 19 02:22:12 2013 @@ -129,7 +129,7 @@ You can append query options to the URI in the following format:</p> <div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ - ?option=value&option=value&É + ?option=value&option=value&⦠]]></script> </div></div> Modified: websites/production/camel/content/http.html ============================================================================== --- websites/production/camel/content/http.html (original) +++ websites/production/camel/content/http.html Thu Dec 19 02:22:12 2013 @@ -435,9 +435,9 @@ ProtocolSocketFactory factory = Protocol.registerProtocol("https", new Protocol( -ÊÊÊÊÊÊÊ "https", -ÊÊÊÊÊÊÊ factory, -ÊÊÊÊÊÊÊ 443)); +       "https", +       factory, +       443)); from("direct:start") .to("https://mail.google.com/mail/").to("mock:results"); Modified: websites/production/camel/content/jt400.html ============================================================================== --- websites/production/camel/content/jt400.html (original) +++ websites/production/camel/content/jt400.html Thu Dec 19 02:22:12 2013 @@ -166,7 +166,7 @@ public class Jt400RouteBuilder extends R public class Jt400RouteBuilder extends RouteBuilder { @Override public void configure() throws Exception { - from("direct:work").to("jt400://GRUPO:ATWORK@server/QSYS.LIB/assets.LIB/compute.PGM?fieldsLength=10,10,512&ouputFieldsIdx=2,3").to(Òdirect:playÓ); + from("direct:work").to("jt400://GRUPO:ATWORK@server/QSYS.LIB/assets.LIB/compute.PGM?fieldsLength=10,10,512&ouputFieldsIdx=2,3").to(âdirect:playâ); } } ]]></script> Modified: websites/production/camel/content/scala-dsl-eip.html ============================================================================== --- websites/production/camel/content/scala-dsl-eip.html (original) +++ websites/production/camel/content/scala-dsl-eip.html Thu Dec 19 02:22:12 2013 @@ -98,11 +98,11 @@ You can check the <a shape="rect" class= <style type="text/css">/*<![CDATA[*/ -div.rbtoc1387228982447 {padding: 0px;} -div.rbtoc1387228982447 ul {list-style: none;margin-left: 0px;} -div.rbtoc1387228982447 li {margin-left: 0px;padding-left: 0px;} +div.rbtoc1387419674594 {padding: 0px;} +div.rbtoc1387419674594 ul {list-style: none;margin-left: 0px;} +div.rbtoc1387419674594 li {margin-left: 0px;padding-left: 0px;} -/*]]>*/</style><div class="toc-macro rbtoc1387228982447"> +/*]]>*/</style><div class="toc-macro rbtoc1387419674594"> <ul class="toc-indentation"><li><span class="TOCOutline">1</span> <a shape="rect" href="#ScalaDSL-EIP-Messagingsystems">Messaging systems</a> <ul class="toc-indentation"><li><span class="TOCOutline">1.1</span> <a shape="rect" href="#ScalaDSL-EIP-Pipelinepipeline">Pipeline</a></li><li><span class="TOCOutline">1.2</span> <a shape="rect" href="#ScalaDSL-EIP-Filterfilter">Filter</a></li></ul> </li><li><span class="TOCOutline">2</span> <a shape="rect" href="#ScalaDSL-EIP-Messagingchannels">Messaging channels</a> Modified: websites/production/camel/content/siteindex.html ============================================================================== --- websites/production/camel/content/siteindex.html (original) +++ websites/production/camel/content/siteindex.html Thu Dec 19 02:22:12 2013 @@ -2318,7 +2318,7 @@ <div class="smalltext" style="margin: 0 0 0 36px">Why use multiple CamelContext In general, you don't tend to want multiple camel contexts in your application, if you're running Camel as a standalone Java instance. However, if you're deploying Camel routes as OSGi bundles, or WARs in an application serve</div> <span class="icon icon-page" title="Page">Page:</span> <a shape="rect" href="wire-tap.html">Wire Tap</a> <br clear="none"> - <div class="smalltext" style="margin: 0 0 0 36px">Wire Tap Wire Tap (from the EIP patterns) allows you to route messages to a separate location while they are being forwarded to the ultimate destination. If you Wire Tap a stream message body then you should consider enabling Stream Caching to ensure the </div> + <div class="smalltext" style="margin: 0 0 0 36px">Wire Tap Wire Tap (from the EIP patterns) allows you to route messages to a separate location while they are being forwarded to the ultimate destination. If you Wire Tap a stream message body then you should consider enabling Stream caching to ensure the </div> <span class="icon icon-page" title="Page">Page:</span> <a shape="rect" href="writing-components.html">Writing Components</a> <br clear="none"> <div class="smalltext" style="margin: 0 0 0 36px">Writing Components Apache Camel is designed to make it very easy to drop in new components whether they be routing components, transformers, transports etc. The idea of a component is to be a factory and manager of Endpoints. Here are the main steps to wr</div> Modified: websites/production/camel/content/spring-testing.html ============================================================================== --- websites/production/camel/content/spring-testing.html (original) +++ websites/production/camel/content/spring-testing.html Thu Dec 19 02:22:12 2013 @@ -252,22 +252,22 @@ public class FilterTest extends Abstract @ContextConfiguration public class MyCamelTest { -Ê Ê @Autowired -Ê Ê protected CamelContext camelContext; +  @Autowired +  protected CamelContext camelContext; -Ê Ê @EndpointInject(uri = "mock:foo") -Ê Ê protected MockEndpoint foo; +  @EndpointInject(uri = "mock:foo") +  protected MockEndpoint foo; @Test @DirtiesContext -Ê Ê public void testMocksAreValid() throws Exception { - ...Ê Ê Ê Ê +  public void testMocksAreValid() throws Exception { + ...    -Ê Ê Ê Ê foo.message(0).header("bar").isEqualTo("ABC"); +    foo.message(0).header("bar").isEqualTo("ABC"); -Ê Ê Ê Ê MockEndpoint.assertIsSatisfied(camelContext); -Ê Ê } +    MockEndpoint.assertIsSatisfied(camelContext); +  } } ]]></script> </div></div> Modified: websites/production/camel/content/tutorial-axis-camel.html ============================================================================== --- websites/production/camel/content/tutorial-axis-camel.html (original) +++ websites/production/camel/content/tutorial-axis-camel.html Thu Dec 19 02:22:12 2013 @@ -98,11 +98,11 @@ <style type="text/css">/*<![CDATA[*/ -div.rbtoc1387228860347 {padding: 0px;} -div.rbtoc1387228860347 ul {list-style: disc;margin-left: 0px;} -div.rbtoc1387228860347 li {margin-left: 0px;padding-left: 0px;} +div.rbtoc1387419635197 {padding: 0px;} +div.rbtoc1387419635197 ul {list-style: disc;margin-left: 0px;} +div.rbtoc1387419635197 li {margin-left: 0px;padding-left: 0px;} -/*]]>*/</style><div class="toc-macro rbtoc1387228860347"> +/*]]>*/</style><div class="toc-macro rbtoc1387419635197"> <ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-AXIS-Camel-TutorialusingAxis1.4withApacheCamel">Tutorial using Axis 1.4 with Apache Camel</a> <ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-AXIS-Camel-Prerequisites">Prerequisites</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-Distribution">Distribution</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-Introduction">Introduction</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-SettinguptheprojecttorunAxis">Setting up the project to run Axis</a> <ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-AXIS-Camel-Maven2">Maven 2</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-wsdl">wsdl</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-ConfiguringAxis">Configuring Axis</a></li><li><a shape="rect" href="#Tutorial-AXIS-Camel-RunningtheExample">Running the Example</a></li></ul> Modified: websites/production/camel/content/tutorial-jmsremoting.html ============================================================================== --- websites/production/camel/content/tutorial-jmsremoting.html (original) +++ websites/production/camel/content/tutorial-jmsremoting.html Thu Dec 19 02:22:12 2013 @@ -101,11 +101,11 @@ <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> <style type="text/css">/*<![CDATA[*/ -div.rbtoc1387228750875 {padding: 0px;} -div.rbtoc1387228750875 ul {list-style: disc;margin-left: 0px;} -div.rbtoc1387228750875 li {margin-left: 0px;padding-left: 0px;} +div.rbtoc1387419598069 {padding: 0px;} +div.rbtoc1387419598069 ul {list-style: disc;margin-left: 0px;} +div.rbtoc1387419598069 li {margin-left: 0px;padding-left: 0px;} -/*]]>*/</style><div class="toc-macro rbtoc1387228750875"> +/*]]>*/</style><div class="toc-macro rbtoc1387419598069"> <ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-JmsRemoting-TutorialonSpringRemotingwithJMS">Tutorial on Spring Remoting with JMS</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-Preface">Preface</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-Prerequisites">Prerequisites</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-Distribution">Distribution</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-About">About</a></li><li><a shape="rect" href="#Tutorial-JmsRemoting-CreatetheCamelProject">Create the Camel Project</a> <ul class="toc-indentation"><li><a shape="rect" href="#Tutorial-JmsRemoting-UpdatethePOMwithDependencies">Update the POM with Dependencies</a></li></ul> </li><li><a shape="rect" href="#Tutorial-JmsRemoting-WritingtheServer">Writing the Server</a> Modified: websites/production/camel/content/tutorial-osgi-camel-part2c.html ============================================================================== --- websites/production/camel/content/tutorial-osgi-camel-part2c.html (original) +++ websites/production/camel/content/tutorial-osgi-camel-part2c.html Thu Dec 19 02:22:12 2013 @@ -1271,7 +1271,7 @@ State Version Name 005,24-04-2009,James,Anstey,incident smx-023,this is a report incident for smx-023,jans...@gmail.com,+555 10 20 300 007,01-04-2009,Willem,Jiang,incident smx-456,this is a report incident for smx-456,wji...@gmail.com,+666 10 20 300 008,27-04-2009,Matt,Raibble,incident appfuse-123,this is a report incident for appfuse-123,mraib...@gmail.com,+777 10 20 300 -009,12-04-2009,Jean-Baptiste,Onofr,incident smx3-088,this is a report incident for smx3-088,cjbono...@gmail.com,+888 10 20 300 +009,12-04-2009,Jean-Baptiste,Onofré,incident smx3-088,this is a report incident for smx3-088,cjbono...@gmail.com,+888 10 20 300 010,17-04-2009,Hadrian,Zbarcea,incident camel-005,this is a report incident for camel-005,hzbar...@gmail.com,+999 10 20 300 ]]></script> </div></div> Modified: websites/production/camel/content/user-guide.html ============================================================================== --- websites/production/camel/content/user-guide.html (original) +++ websites/production/camel/content/user-guide.html Thu Dec 19 02:22:12 2013 @@ -79,11 +79,11 @@ <p>If you want to get more familiar with what Apache Camel has to offer, please try the following resources:</p> <style type="text/css">/*<![CDATA[*/ -div.rbtoc1387228727764 {padding: 0px;} -div.rbtoc1387228727764 ul {list-style: disc;margin-left: 0px;} -div.rbtoc1387228727764 li {margin-left: 0px;padding-left: 0px;} +div.rbtoc1387419592665 {padding: 0px;} +div.rbtoc1387419592665 ul {list-style: disc;margin-left: 0px;} +div.rbtoc1387419592665 li {margin-left: 0px;padding-left: 0px;} -/*]]>*/</style><div class="toc-macro rbtoc1387228727764"> +/*]]>*/</style><div class="toc-macro rbtoc1387419592665"> <ul class="toc-indentation"><li><a shape="rect" href="#UserGuide-Wikipages">Wiki pages</a></li><li><a shape="rect" href="#UserGuide-PDF">PDF</a></li><li><a shape="rect" href="#UserGuide-OtherResources.">Other Resources.</a></li></ul> </div> Modified: websites/production/camel/content/zip-dataformat.html ============================================================================== --- websites/production/camel/content/zip-dataformat.html (original) +++ websites/production/camel/content/zip-dataformat.html Thu Dec 19 02:22:12 2013 @@ -127,7 +127,7 @@ from("direct:start").marshal() <p>In this example we unmarshal a zipped payload from an ActiveMQ queue called MY_QUEUE to its original format, and forward it for processing to the UnZippedMessageProcessor. Note that the compression Level employed during the marshalling should be identical to the one employed during unmarshalling to avoid errors.</p> <div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ -from("activemq:queue:MY_QUEUE").unmarshal().zip().process(new UnZippedMessageProcessor());Ê +from("activemq:queue:MY_QUEUE").unmarshal().zip().process(new UnZippedMessageProcessor()); ]]></script> </div></div> Modified: websites/production/camel/content/zip-file-dataformat.html ============================================================================== --- websites/production/camel/content/zip-file-dataformat.html (original) +++ websites/production/camel/content/zip-file-dataformat.html Thu Dec 19 02:22:12 2013 @@ -125,7 +125,7 @@ <p>In this example we unmarshal a Zip file payload from an ActiveMQ queue called MY_QUEUE to its original format, and forward it for processing to the <code>UnZippedMessageProcessor</code>.</p> <div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl"> <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[ -from("activemq:queue:MY_QUEUE").unmarshal().zipFile().process(new UnZippedMessageProcessor());Ê +from("activemq:queue:MY_QUEUE").unmarshal().zipFile().process(new UnZippedMessageProcessor()); ]]></script> </div></div>
![http://www.enterpriseintegrationpatterns.com/img/WireTap.gif"](http://www.enterpriseintegrationpatterns.com/img/WireTap.gif"){kind=link}