svn commit: r859443 - in /websites/production/activemq/content: cache/main.pageCache jms-to-jms-bridge.html

[bu...@apache.org]

Author: buildbot
Date: Mon Apr 22 13:21:36 2013
New Revision: 859443

Log:
Production update by buildbot for activemq

Modified:
    websites/production/activemq/content/cache/main.pageCache
    websites/production/activemq/content/jms-to-jms-bridge.html

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

Modified: websites/production/activemq/content/jms-to-jms-bridge.html
==============================================================================
--- websites/production/activemq/content/jms-to-jms-bridge.html (original)
+++ websites/production/activemq/content/jms-to-jms-bridge.html Mon Apr 22 13:21:36 2013
@@ -74,6 +74,22 @@
           <div class="wiki-content maincontent">
 <h3><a shape="rect" name="JMStoJMSBridge-Introduction"></a>Introduction</h3>
 
+<div class="panelMacro"><table class="warningMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/forbidden.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Warning, try Camel first!</b><br clear="none">Note that we recommend you look at using <a shape="rect" class="external-link" href="http://camel.apache.org/">Apache Camel</a> for bridging ActiveMQ to or from any message broker (or indeed <a shape="rect" class="external-link" href="http://camel.apache.org/components.html">any other technology, protocol or middleware</a>) as its much easier to:
+<ul><li>keep things flexible; its very easy to map different queue/topic to one or more queues or topics on the other provider</li><li>perform content based routing, filtering and other <a shape="rect" class="external-link" href="http://camel.apache.org/enterprise-integration-patterns.html">Enterprise Integration Patterns</a></li><li>allows you to work with <a shape="rect" class="external-link" href="http://camel.apache.org/components.html">any technology, protocol or middleware</a>, not just JMS providers</li></ul>
+
+
+<p>e.g. in your Spring XML file just add:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<pre class="code-xml">
+<span class="code-tag">&lt;camelContext xmlns=<span class="code-quote">"http://camel.apache.org/schema/spring"</span>&gt;</span>
+  <span class="code-tag">&lt;route&gt;</span>
+   <span class="code-tag">&lt;from uri=<span class="code-quote">"mqseries:Foo.Bar"</span>/&gt;</span>
+   <span class="code-tag">&lt;to uri=<span class="code-quote">"activemq:Cheese"</span>/&gt;</span>
+  <span class="code-tag">&lt;/route&gt;</span>
+<span class="code-tag">&lt;/camelContext&gt;</span>
+</pre>
+</div></div></td></tr></table></div>
+
 <p>ActiveMQ provides bridging functionality to other JMS providers that implement the JMS 1.0.2 and above specification.<br clear="none">
 A JMS bridge can be co-located with an ActiveMQ broker or run remotely.<br clear="none">
 In order to support JMS 1.0.2 there is seperation between Queues and Topics.</p>