camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r825951 [1/2] - in /websites/production/camel/content: articles.html book-component-appendix.html book-in-one-page.html cache/main.pageCache jms.html
Date Mon, 16 Jul 2012 07:19:58 GMT
Author: buildbot
Date: Mon Jul 16 07:19:57 2012
New Revision: 825951

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/articles.html
    websites/production/camel/content/book-component-appendix.html
    websites/production/camel/content/book-in-one-page.html
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/jms.html

Modified: websites/production/camel/content/articles.html
==============================================================================
--- websites/production/camel/content/articles.html (original)
+++ websites/production/camel/content/articles.html Mon Jul 16 07:19:57 2012
@@ -96,7 +96,7 @@
 
 <p>These examples show usage of several different components and other concepts such as error handling.</p>
 
-<ul><li><a shape="rect" class="external-link" href="http://mikemclean.ca/muse/2009/05/a-bit-more-meat-camel-applied-jms-to-file/" rel="nofollow">A bit more meat: Camel applied : JMS to File</a> by Mike McLean</li><li>Matteo wrote a blog entry about <a shape="rect" class="external-link" href="http://matteoredaelli.wordpress.com/2008/10/08/using-apache-camel-with-ibatis/" rel="nofollow">using Camel with iBatis</a></li><li><a shape="rect" class="external-link" href="http://tmielke.blogspot.com/2009/01/using-camel-aggregator-correctly.html" rel="nofollow">Using the Camel aggregator correctly</a> by Torsten Mielke, a great blog entry how to use the Camel aggregator.</li><li><a shape="rect" class="external-link" href="http://aminsblog.wordpress.com/2008/05/06/15/" rel="nofollow">Spring Remoting with JMS Example</a> on <a shape="rect" class="external-link" href="http://searjeant.blogspot.com/2009/02/camel-routes-and-hl7.html" rel="nofollow">Amin Abbaspour's Weblog</a></li><li><a sh
 ape="rect" class="external-link" href="http://searjeant.blogspot.com/2009/02/camel-routes-and-hl7.html" rel="nofollow">Camel routes and HL7</a> by Roger Searjeant on using Camel and its HL7 support in the health care space.</li><li><a shape="rect" class="external-link" href="http://blog.brunoborges.com.br/2009/03/leverage-eip-with-apache-camel-and.html" rel="nofollow">Leverage EIP with Apache Camel and Twitter</a> by Bruno Borges</li><li><a shape="rect" class="external-link" href="http://blog.jeroenreijn.com/2009/03/apache-camel-open-source-integration.html" rel="nofollow">Using RSS with Apache Camel</a> by Jeroen Reijn</li><li><a shape="rect" class="external-link" href="http://ssagara.blogspot.com/2009/04/axis2-ride-with-camel.html" rel="nofollow">Axis 2 ride with Camel</a> how to use Axis 2 with Camel by Sagara</li><li><a shape="rect" class="external-link" href="http://christopherhunt-software.blogspot.com/2009/07/camel-based-xml-payload-http-polling.html" rel="nofollow">A
  Camel based XML payload HTTP polling provider</a> by Christopher Hunt to use Camel with AJAX. Interesting read.</li><li><a shape="rect" class="external-link" href="http://krasserm.blogspot.com/2009/10/first-steps-with-apache-camel-on-google.html" rel="nofollow">First steps with Apache Camel on Google App Engine</a> by Martin Krasser posts his findings to get Camel running on the GAE.</li><li><a shape="rect" class="external-link" href="http://blog.software-art.nl/2009/11/15/camel-cxf-and-jms-by-example/" rel="nofollow">Camel, CXF and JMS by Example</a> by Silvester van der Bijl. Good blog entry how to use CXF and Camel together.</li><li><a shape="rect" class="external-link" href="http://www.andrejkoelewijn.com/wp/2009/10/27/simple-log-console-with-camel-and-cometd/" rel="nofollow">A simple file monitoring console with camel, cometd and jquery</a> by Andrej Koelewijn. Shows how to use Camel to monitor log files and  push lines changed using cometd to a webpage. All in a few f
 iles using  Groovy.</li><li><a shape="rect" class="external-link" href="http://spring-java-ee.blogspot.com/2010/01/advanced-event-notification-framework.html" rel="nofollow">Advanced Event Notification Framework with Apache Camel</a> by Hendy showing how to use Camel for a lightweight even notification system.</li><li><a shape="rect" class="external-link" href="http://github.com/jamescarr/irc-camel-example" rel="nofollow">Camel IRC Message Route Example</a> by James Carr. An IRC bot which can parse JavaScript and Ruby expressions.</li><li><a shape="rect" class="external-link" href="http://www.andrejkoelewijn.com/wp/2010/06/13/a-composite-rest-service-using-camel/" rel="nofollow">A composite REST service using Apache Camel</a> by Andrej Koelewijn. A blog entry how to expose a REST service and have  Camel aggregate data from multiple sources to be returned.</li><li><a shape="rect" class="external-link" href="http://fornax-sculptor.blogspot.com/2010/08/eda-events-over-system-bo
 undaries-with.html" rel="nofollow">EDA events over system boundaries with Camel</a> by <a shape="rect" class="external-link" href="http://sites.google.com/site/fornaxsculptor/" rel="nofollow">Sculptur</a> team blog.</li><li><a shape="rect" class="external-link" href="http://blog.jayway.com/2010/08/12/dynamic-ftp-client-using-apache-camel-and-spring/" rel="nofollow">Dynamic FTP Client using Apache Camel and Spring</a> by Mattias Severson, showing how to develop an FTP client that could  transmit files to various FTP servers as a part of a delivery system in a  Java enterprise application.</li><li><a shape="rect" class="external-link" href="http://www.jroller.com/gmazza/entry/camel_jms_and_soap" rel="nofollow">Using Apache Camel to route SOAP calls through message queues</a> by <a shape="rect" class="external-link" href="http://www.jroller.com/gmazza/" rel="nofollow">Glen Mazza</a></li><li><a shape="rect" class="external-link" href="http://pjagielski.blogspot.com/2010/09/virtu
 al-esb-application-integration.html" rel="nofollow">Virtual ESB - application integration made painless with Apache Camel</a> by Piotr Jagielski shows how to use Camel as a lightweight integration using web service and XML.</li><li><a shape="rect" class="external-link" href="http://waterback.github.com/blog/2011/12/08/application-monitoring-with-camel/" rel="nofollow">Application-Monitoring &amp; Statistics-Collection with Apache Camel</a> by Martin Huber - Talks about how to gather Camel route statistics and persist those in a database using JPA.</li><li><a shape="rect" class="external-link" href="http://benoday.blogspot.com/2010/08/camel-exception-handling-overview.html" rel="nofollow">Camel exception handling overview</a> by Ben O'Day giving a nice and short summary of some of the error handling capabilities in Camel.</li><li><a shape="rect" class="external-link" href="http://spring-java-ee.blogspot.com/2010/12/remote-observer-pattern-with-publish.html" rel="nofollow">Rem
 ote Observer Pattern with Publish-Subscribe via XMPP</a> by Hendy showing how easy it is to implement this pattern with Apache Camel using XMPP as transport.</li><li><a shape="rect" class="external-link" href="http://spring-java-ee.blogspot.com/2010/12/implementing-asynchronous-observer.html" rel="nofollow">Implementing Asynchronous Observer Pattern with Bean Proxy</a> by Hendy showing how easy it is to implement this pattern with Apache Camel using Camel's BeanProxy.</li><li><a shape="rect" class="external-link" href="http://blog.srvme.de/2011/01/30/apache-camel-example-application-earthquake-mashup/" rel="nofollow">Apache Camel Example Application - Earthquake Mashups</a> showing how Camel using<span class="error">[\||]</span> EIPs can gather online earthquake and weather data and expose REST service.</li><li><a shape="rect" class="external-link" href="http://waterback.github.com/blog/2011/12/09/camel-inherit-errorhandling/" rel="nofollow">RouteBuilding with inherited conf
 igurations</a> by Martin Huber shows how to inherit configuration (such as error handling) when using Java DSL.</li><li><a shape="rect" class="external-link" href="http://blogs.justenougharchitecture.com/?p=310" rel="nofollow">Mathew's Thoughts on Apache Camel</a> shows how Apache Camel easily can route messages from a JMS topic to  files using the Content Based Router EIP. More blog posts to come.</li><li><a shape="rect" class="external-link" href="http://hwellmann.blogspot.com/2011/03/transparent-asynchronous-remoting-via.html" rel="nofollow">Transparent Asynchronous Remoting via JMS</a> by Harald Wellman, who blogs how to use Camel for asynchronous remoting over<span class="error">[\||]</span> JMS, having the middleware hidden, so the client is unaware of this fact, its just using a interface.</li><li><a shape="rect" class="external-link" href="http://www.springerlink.com/content/h486777744gw1025/" rel="nofollow">Dynamic Routing Using Health Information Policy with Apache
  Camel</a> by Edward Brown and Jamie Goodyear. Published in Springer  Communications in Computer and Information Science under the publication  for "Biomedical Engineering Systems and Technologies, Third  International Joint Conference, BIOSTEC 2010, Valencia, Spain, January  20-23, 2010, Revised Selected Papers".</li><li><a shape="rect" class="external-link" href="http://www.catify.com/2011/03/29/transforming-and-splitting-huge-edi-files-with-smooks/" rel="nofollow">Transforming and splitting huge EDI files using Smooks and Camel</a> by Claus Straube from <a shape="rect" class="external-link" href="http://www.catify.com/" rel="nofollow">Catify</a> shows how to process huge EDI files with low CPU and memory footprint.</li><li><a shape="rect" class="external-link" href="http://labs.bsb.com/2011/04/jdbc-persistence-for-camel-aggregator/" rel="nofollow">JDBC Persistence for Camel Aggregator</a> talks about how to use the Agreggator EIP with persistence support.</li><li><a shape
 ="rect" class="external-link" href="http://scottcranton.blogspot.com/2011/04/socat-is-so-cool.html" rel="nofollow">TCP proxy with Apache Camel</a> by Scott Cranton, showing how you can easily use Camel as a TCP proxy with Apache Mina.</li><li><a shape="rect" class="external-link" href="http://www.catify.com/2011/06/06/process-driven-form-with-apache-camel-and-websockets/" rel="nofollow">Process driven Froms with Apache Camel and websockets</a> shows how to use web sockets with Camel with an Web UI example.</li><li><a shape="rect" class="external-link" href="http://marcelojabali.blogspot.com/2011/07/calling-web-services-with-apache-camel.html" rel="nofollow">Calling WebServices with Apache Camel</a> by Marcelo Jabali shows how to call the public Stock Quote Web Service over the internet using CXF with Camel.</li><li><a shape="rect" class="external-link" href="http://blog.jayway.com/2011/07/14/apache_camel_and_soap/" rel="nofollow">Apache Camel and SOAP</a> by Jan Kronquist sh
 owing an integration scenario using freely available  SOAP web services to create a service that can return the weather at an  airport.</li><li><a shape="rect" class="external-link" href="http://marcelojabali.blogspot.com/2011/07/using-apache-camel-to-monitor-snmp.html" rel="nofollow">Using Apache Camel to monitor SNMP devices</a> by Marcelo Jabali showing how to monitor SNMP devices using Apache Camel in a few lines of code</li><li><a shape="rect" class="external-link" href="http://blog.nanthrax.net/2011/07/website-mashup-with-apache-camel/" rel="nofollow">Website mashup with Apache Camel</a> by Jean-Baptiste Onofr&#233; shows how to extract data from HTML web sites using Apache Camel</li><li><a shape="rect" class="external-link" href="http://tmielke.blogspot.com/2011/07/error-handling-in-camel-for-jms.html" rel="nofollow">Error handling in Camel for JMS consumer endpoint</a> by Torsten Mielke explains some of the options you have for error handling when using JMS.</li><li>
 <a shape="rect" class="external-link" href="http://www.kai-waehner.de/blog/2011/08/30/cloud-integration-with-apache-camel-and-amazon-web-services-aws-s3-sqs-and-sns/" rel="nofollow">Cloud integration with Apache Camel and Amazon web services s3 sqs and sns</a> by Kai W&#228;hner explains how to interface Amazon Web Services (S3, SQS and SNS) with Apache Camel.</li><li><a shape="rect" class="external-link" href="http://searchsoa.techtarget.com/news/2240035028/Visual-IDE-said-to-jump-start-Camel-mediation-routing" rel="nofollow">Visual IDE said to jump start Camel mediation routing</a> - Article from TechTarget magazine about visual IDE for Camel development</li><li><a shape="rect" class="external-link" href="http://marcelojabali.blogspot.com/2011/09/using-apache-mina-in-camel.html" rel="nofollow">Using the MINA component in Apache Camel</a> - Blog post by Marcelo Jabali showing how to talk to a server using TCP with the Camel MINA component.</li><li><a shape="rect" class="ext
 ernal-link" href="http://marcelojabali.blogspot.com/2011/10/using-http-based-endpoints-with-apache.html?spref=tw" rel="nofollow">Using HTTP-based endpoints with Apache Camel</a> - Blog post by Marcelo Jabali showing how to expose a HTTP servie with the Camel Jetty component.</li><li><a shape="rect" class="external-link" href="http://iocanel.blogspot.com/2011/11/cloud-notifications-with-apache-camel.html" rel="nofollow">Cloud Notifications with Apache Camel</a> - Blog post by Ioannis Canellos writing about how to use camel-jclouds to be notified about your running nodes in the cloud</li><li><a shape="rect" class="external-link" href="http://www.liquid-reality.de/x/XYBe" rel="nofollow">Hot Standby failover for Apache Camel</a> by Christian Schneider</li><li><a shape="rect" class="external-link" href="http://tech.robbieone.com/post/15341612892/combine-yahoo-finance-and-hbase-using-camel-and-rest" rel="nofollow">Combine Yahoo Finance and HBase using Camel</a> - Blog post Robert 
 Felker writing about how to gather finance statistics from Yahoo using Camel with HBase and REST.</li><li><a shape="rect" class="external-link" href="http://davsclaus.blogspot.com/2011/11/splitting-big-xml-files-with-apache.html" rel="nofollow">Splitting big XML files with Camel - Part 1</a> - This blog post covers how to split big XML files in a streaming mode  using new functionality introduced in Camel 2.9, and explains some of  its inner details.</li><li><a shape="rect" class="external-link" href="http://davsclaus.blogspot.com/2011/11/splitting-big-xml-files-with-apache_24.html" rel="nofollow">Splitting big XML files with Camel - Part 2</a> - This covers splitting big XML files using the new <tt>camel-stax</tt> component, introduced in Camel 2.9.</li><li><a shape="rect" class="external-link" href="http://davsclaus.blogspot.com/2012/02/correlating-logs-from-redelivered.html" rel="nofollow">Correlating logs from redelivered messages</a> - By Claus Ibsen, talks how you can 
 correlate externally redelivered  message in the logs, to know what is what. The blog also shows how you  can customize logging levels, and what you can tell from JMX as well.</li><li><a shape="rect" class="external-link" href="http://jeff-davis.blogspot.com/2012/02/using-apache-camel-to-manage-amazon-ec2.html" rel="nofollow">Using Apache Camel to Manage Amazon EC2 Startup/Shutdown</a> by Jeff Davis.</li><li><a shape="rect" class="external-link" href="http://waterback.github.com/blog/2012/03/02/easy-handmade-ws-addresssing-with-apache-camel/" rel="nofollow">Easy Handmade SOAP-Webservice-Versioning With Apache Camel</a> by Martin Huber, blogs how to do WS versioning with Apache CXF and Camel.</li><li><a shape="rect" class="external-link" href="http://davsclaus.blogspot.se/2012/03/camel-now-with-twitter-and-websocket.html" rel="nofollow">Using twitter and web socket with Apache Camel</a> by Claus Ibsen, blogs how to use the new Twitter component to post live twitter search fee
 ds to a web page using WebSocket.</li><li><a shape="rect" class="external-link" href="http://java.dzone.com/articles/gotcha-when-using-camel" rel="nofollow">Gotcha when using Camel Servlet</a> - A blog post with some advice when using the Camel Servlet component.</li><li><a shape="rect" class="external-link" href="http://jason-sherman.blogspot.se/2012/04/camel-working-with-email-attachments.html" rel="nofollow">Working with EMail attachments</a> - by Jason Sherman, whom blogs about how to split emails with multiple  attachments into multiple messages with a single attachment each, for  further processing in Camel.</li><li><a shape="rect" class="external-link" href="http://thinkinginsoftware.blogspot.se/2012/05/using-quartz-camel-and-spring-for.html" rel="nofollow">Using Quartz, Camel and Spring for Distributed Service Orchestration</a> - by Nestor Urquiza blogs about using Quartz and Camel to build a distributed solution running a clustered Camel application on multiple Tomc
 at instances.</li><li><a shape="rect" class="external-link" href="http://blog.raulkr.net/2012/06/camel-and-mongodb-match-made-in-heaven.html" rel="nofollow">Camel and MongoDB: a match made in heaven</a> - Introduction to the Camel MongoDB component launched with the Camel 2.10 release.</li></ul>
+<ul><li><a shape="rect" class="external-link" href="http://mikemclean.ca/muse/2009/05/a-bit-more-meat-camel-applied-jms-to-file/" rel="nofollow">A bit more meat: Camel applied : JMS to File</a> by Mike McLean</li><li>Matteo wrote a blog entry about <a shape="rect" class="external-link" href="http://matteoredaelli.wordpress.com/2008/10/08/using-apache-camel-with-ibatis/" rel="nofollow">using Camel with iBatis</a></li><li><a shape="rect" class="external-link" href="http://tmielke.blogspot.com/2009/01/using-camel-aggregator-correctly.html" rel="nofollow">Using the Camel aggregator correctly</a> by Torsten Mielke, a great blog entry how to use the Camel aggregator.</li><li><a shape="rect" class="external-link" href="http://aminsblog.wordpress.com/2008/05/06/15/" rel="nofollow">Spring Remoting with JMS Example</a> on <a shape="rect" class="external-link" href="http://searjeant.blogspot.com/2009/02/camel-routes-and-hl7.html" rel="nofollow">Amin Abbaspour's Weblog</a></li><li><a sh
 ape="rect" class="external-link" href="http://searjeant.blogspot.com/2009/02/camel-routes-and-hl7.html" rel="nofollow">Camel routes and HL7</a> by Roger Searjeant on using Camel and its HL7 support in the health care space.</li><li><a shape="rect" class="external-link" href="http://blog.brunoborges.com.br/2009/03/leverage-eip-with-apache-camel-and.html" rel="nofollow">Leverage EIP with Apache Camel and Twitter</a> by Bruno Borges</li><li><a shape="rect" class="external-link" href="http://blog.jeroenreijn.com/2009/03/apache-camel-open-source-integration.html" rel="nofollow">Using RSS with Apache Camel</a> by Jeroen Reijn</li><li><a shape="rect" class="external-link" href="http://ssagara.blogspot.com/2009/04/axis2-ride-with-camel.html" rel="nofollow">Axis 2 ride with Camel</a> how to use Axis 2 with Camel by Sagara</li><li><a shape="rect" class="external-link" href="http://christopherhunt-software.blogspot.com/2009/07/camel-based-xml-payload-http-polling.html" rel="nofollow">A
  Camel based XML payload HTTP polling provider</a> by Christopher Hunt to use Camel with AJAX. Interesting read.</li><li><a shape="rect" class="external-link" href="http://krasserm.blogspot.com/2009/10/first-steps-with-apache-camel-on-google.html" rel="nofollow">First steps with Apache Camel on Google App Engine</a> by Martin Krasser posts his findings to get Camel running on the GAE.</li><li><a shape="rect" class="external-link" href="http://blog.software-art.nl/2009/11/15/camel-cxf-and-jms-by-example/" rel="nofollow">Camel, CXF and JMS by Example</a> by Silvester van der Bijl. Good blog entry how to use CXF and Camel together.</li><li><a shape="rect" class="external-link" href="http://www.andrejkoelewijn.com/wp/2009/10/27/simple-log-console-with-camel-and-cometd/" rel="nofollow">A simple file monitoring console with camel, cometd and jquery</a> by Andrej Koelewijn. Shows how to use Camel to monitor log files and  push lines changed using cometd to a webpage. All in a few f
 iles using  Groovy.</li><li><a shape="rect" class="external-link" href="http://spring-java-ee.blogspot.com/2010/01/advanced-event-notification-framework.html" rel="nofollow">Advanced Event Notification Framework with Apache Camel</a> by Hendy showing how to use Camel for a lightweight even notification system.</li><li><a shape="rect" class="external-link" href="http://github.com/jamescarr/irc-camel-example" rel="nofollow">Camel IRC Message Route Example</a> by James Carr. An IRC bot which can parse JavaScript and Ruby expressions.</li><li><a shape="rect" class="external-link" href="http://www.andrejkoelewijn.com/wp/2010/06/13/a-composite-rest-service-using-camel/" rel="nofollow">A composite REST service using Apache Camel</a> by Andrej Koelewijn. A blog entry how to expose a REST service and have  Camel aggregate data from multiple sources to be returned.</li><li><a shape="rect" class="external-link" href="http://fornax-sculptor.blogspot.com/2010/08/eda-events-over-system-bo
 undaries-with.html" rel="nofollow">EDA events over system boundaries with Camel</a> by <a shape="rect" class="external-link" href="http://sites.google.com/site/fornaxsculptor/" rel="nofollow">Sculptur</a> team blog.</li><li><a shape="rect" class="external-link" href="http://blog.jayway.com/2010/08/12/dynamic-ftp-client-using-apache-camel-and-spring/" rel="nofollow">Dynamic FTP Client using Apache Camel and Spring</a> by Mattias Severson, showing how to develop an FTP client that could  transmit files to various FTP servers as a part of a delivery system in a  Java enterprise application.</li><li><a shape="rect" class="external-link" href="http://www.jroller.com/gmazza/entry/camel_jms_and_soap" rel="nofollow">Using Apache Camel to route SOAP calls through message queues</a> by <a shape="rect" class="external-link" href="http://www.jroller.com/gmazza/" rel="nofollow">Glen Mazza</a></li><li><a shape="rect" class="external-link" href="http://pjagielski.blogspot.com/2010/09/virtu
 al-esb-application-integration.html" rel="nofollow">Virtual ESB - application integration made painless with Apache Camel</a> by Piotr Jagielski shows how to use Camel as a lightweight integration using web service and XML.</li><li><a shape="rect" class="external-link" href="http://waterback.github.com/blog/2011/12/08/application-monitoring-with-camel/" rel="nofollow">Application-Monitoring &amp; Statistics-Collection with Apache Camel</a> by Martin Huber - Talks about how to gather Camel route statistics and persist those in a database using JPA.</li><li><a shape="rect" class="external-link" href="http://benoday.blogspot.com/2010/08/camel-exception-handling-overview.html" rel="nofollow">Camel exception handling overview</a> by Ben O'Day giving a nice and short summary of some of the error handling capabilities in Camel.</li><li><a shape="rect" class="external-link" href="http://spring-java-ee.blogspot.com/2010/12/remote-observer-pattern-with-publish.html" rel="nofollow">Rem
 ote Observer Pattern with Publish-Subscribe via XMPP</a> by Hendy showing how easy it is to implement this pattern with Apache Camel using XMPP as transport.</li><li><a shape="rect" class="external-link" href="http://spring-java-ee.blogspot.com/2010/12/implementing-asynchronous-observer.html" rel="nofollow">Implementing Asynchronous Observer Pattern with Bean Proxy</a> by Hendy showing how easy it is to implement this pattern with Apache Camel using Camel's BeanProxy.</li><li><a shape="rect" class="external-link" href="http://blog.srvme.de/2011/01/30/apache-camel-example-application-earthquake-mashup/" rel="nofollow">Apache Camel Example Application - Earthquake Mashups</a> showing how Camel using<span class="error">[\||]</span> EIPs can gather online earthquake and weather data and expose REST service.</li><li><a shape="rect" class="external-link" href="http://waterback.github.com/blog/2011/12/09/camel-inherit-errorhandling/" rel="nofollow">RouteBuilding with inherited conf
 igurations</a> by Martin Huber shows how to inherit configuration (such as error handling) when using Java DSL.</li><li><a shape="rect" class="external-link" href="http://blogs.justenougharchitecture.com/?p=310" rel="nofollow">Mathew's Thoughts on Apache Camel</a> shows how Apache Camel easily can route messages from a JMS topic to  files using the Content Based Router EIP. More blog posts to come.</li><li><a shape="rect" class="external-link" href="http://hwellmann.blogspot.com/2011/03/transparent-asynchronous-remoting-via.html" rel="nofollow">Transparent Asynchronous Remoting via JMS</a> by Harald Wellman, who blogs how to use Camel for asynchronous remoting over<span class="error">[\||]</span> JMS, having the middleware hidden, so the client is unaware of this fact, its just using a interface.</li><li><a shape="rect" class="external-link" href="http://www.springerlink.com/content/h486777744gw1025/" rel="nofollow">Dynamic Routing Using Health Information Policy with Apache
  Camel</a> by Edward Brown and Jamie Goodyear. Published in Springer  Communications in Computer and Information Science under the publication  for "Biomedical Engineering Systems and Technologies, Third  International Joint Conference, BIOSTEC 2010, Valencia, Spain, January  20-23, 2010, Revised Selected Papers".</li><li><a shape="rect" class="external-link" href="http://www.catify.com/2011/03/29/transforming-and-splitting-huge-edi-files-with-smooks/" rel="nofollow">Transforming and splitting huge EDI files using Smooks and Camel</a> by Claus Straube from <a shape="rect" class="external-link" href="http://www.catify.com/" rel="nofollow">Catify</a> shows how to process huge EDI files with low CPU and memory footprint.</li><li><a shape="rect" class="external-link" href="http://labs.bsb.com/2011/04/jdbc-persistence-for-camel-aggregator/" rel="nofollow">JDBC Persistence for Camel Aggregator</a> talks about how to use the Agreggator EIP with persistence support.</li><li><a shape
 ="rect" class="external-link" href="http://scottcranton.blogspot.com/2011/04/socat-is-so-cool.html" rel="nofollow">TCP proxy with Apache Camel</a> by Scott Cranton, showing how you can easily use Camel as a TCP proxy with Apache Mina.</li><li><a shape="rect" class="external-link" href="http://www.catify.com/2011/06/06/process-driven-form-with-apache-camel-and-websockets/" rel="nofollow">Process driven Froms with Apache Camel and websockets</a> shows how to use web sockets with Camel with an Web UI example.</li><li><a shape="rect" class="external-link" href="http://marcelojabali.blogspot.com/2011/07/calling-web-services-with-apache-camel.html" rel="nofollow">Calling WebServices with Apache Camel</a> by Marcelo Jabali shows how to call the public Stock Quote Web Service over the internet using CXF with Camel.</li><li><a shape="rect" class="external-link" href="http://blog.jayway.com/2011/07/14/apache_camel_and_soap/" rel="nofollow">Apache Camel and SOAP</a> by Jan Kronquist sh
 owing an integration scenario using freely available  SOAP web services to create a service that can return the weather at an  airport.</li><li><a shape="rect" class="external-link" href="http://marcelojabali.blogspot.com/2011/07/using-apache-camel-to-monitor-snmp.html" rel="nofollow">Using Apache Camel to monitor SNMP devices</a> by Marcelo Jabali showing how to monitor SNMP devices using Apache Camel in a few lines of code</li><li><a shape="rect" class="external-link" href="http://blog.nanthrax.net/2011/07/website-mashup-with-apache-camel/" rel="nofollow">Website mashup with Apache Camel</a> by Jean-Baptiste Onofr&#233; shows how to extract data from HTML web sites using Apache Camel</li><li><a shape="rect" class="external-link" href="http://tmielke.blogspot.com/2011/07/error-handling-in-camel-for-jms.html" rel="nofollow">Error handling in Camel for JMS consumer endpoint</a> by Torsten Mielke explains some of the options you have for error handling when using JMS.</li><li>
 <a shape="rect" class="external-link" href="http://www.kai-waehner.de/blog/2011/08/30/cloud-integration-with-apache-camel-and-amazon-web-services-aws-s3-sqs-and-sns/" rel="nofollow">Cloud integration with Apache Camel and Amazon web services s3 sqs and sns</a> by Kai W&#228;hner explains how to interface Amazon Web Services (S3, SQS and SNS) with Apache Camel.</li><li><a shape="rect" class="external-link" href="http://searchsoa.techtarget.com/news/2240035028/Visual-IDE-said-to-jump-start-Camel-mediation-routing" rel="nofollow">Visual IDE said to jump start Camel mediation routing</a> - Article from TechTarget magazine about visual IDE for Camel development</li><li><a shape="rect" class="external-link" href="http://marcelojabali.blogspot.com/2011/09/using-apache-mina-in-camel.html" rel="nofollow">Using the MINA component in Apache Camel</a> - Blog post by Marcelo Jabali showing how to talk to a server using TCP with the Camel MINA component.</li><li><a shape="rect" class="ext
 ernal-link" href="http://marcelojabali.blogspot.com/2011/10/using-http-based-endpoints-with-apache.html?spref=tw" rel="nofollow">Using HTTP-based endpoints with Apache Camel</a> - Blog post by Marcelo Jabali showing how to expose a HTTP servie with the Camel Jetty component.</li><li><a shape="rect" class="external-link" href="http://iocanel.blogspot.com/2011/11/cloud-notifications-with-apache-camel.html" rel="nofollow">Cloud Notifications with Apache Camel</a> - Blog post by Ioannis Canellos writing about how to use camel-jclouds to be notified about your running nodes in the cloud</li><li><a shape="rect" class="external-link" href="http://www.liquid-reality.de/x/XYBe" rel="nofollow">Hot Standby failover for Apache Camel</a> by Christian Schneider</li><li><a shape="rect" class="external-link" href="http://tech.robbieone.com/post/15341612892/combine-yahoo-finance-and-hbase-using-camel-and-rest" rel="nofollow">Combine Yahoo Finance and HBase using Camel</a> - Blog post Robert 
 Felker writing about how to gather finance statistics from Yahoo using Camel with HBase and REST.</li><li><a shape="rect" class="external-link" href="http://davsclaus.blogspot.com/2011/11/splitting-big-xml-files-with-apache.html" rel="nofollow">Splitting big XML files with Camel - Part 1</a> - This blog post covers how to split big XML files in a streaming mode  using new functionality introduced in Camel 2.9, and explains some of  its inner details.</li><li><a shape="rect" class="external-link" href="http://davsclaus.blogspot.com/2011/11/splitting-big-xml-files-with-apache_24.html" rel="nofollow">Splitting big XML files with Camel - Part 2</a> - This covers splitting big XML files using the new <tt>camel-stax</tt> component, introduced in Camel 2.9.</li><li><a shape="rect" class="external-link" href="http://davsclaus.blogspot.com/2012/02/correlating-logs-from-redelivered.html" rel="nofollow">Correlating logs from redelivered messages</a> - By Claus Ibsen, talks how you can 
 correlate externally redelivered  message in the logs, to know what is what. The blog also shows how you  can customize logging levels, and what you can tell from JMX as well.</li><li><a shape="rect" class="external-link" href="http://jeff-davis.blogspot.com/2012/02/using-apache-camel-to-manage-amazon-ec2.html" rel="nofollow">Using Apache Camel to Manage Amazon EC2 Startup/Shutdown</a> by Jeff Davis.</li><li><a shape="rect" class="external-link" href="http://waterback.github.com/blog/2012/03/02/easy-handmade-ws-addresssing-with-apache-camel/" rel="nofollow">Easy Handmade SOAP-Webservice-Versioning With Apache Camel</a> by Martin Huber, blogs how to do WS versioning with Apache CXF and Camel.</li><li><a shape="rect" class="external-link" href="http://davsclaus.blogspot.se/2012/03/camel-now-with-twitter-and-websocket.html" rel="nofollow">Using twitter and web socket with Apache Camel</a> by Claus Ibsen, blogs how to use the new Twitter component to post live twitter search fee
 ds to a web page using WebSocket.</li><li><a shape="rect" class="external-link" href="http://java.dzone.com/articles/gotcha-when-using-camel" rel="nofollow">Gotcha when using Camel Servlet</a> - A blog post with some advice when using the Camel Servlet component.</li><li><a shape="rect" class="external-link" href="http://jason-sherman.blogspot.se/2012/04/camel-working-with-email-attachments.html" rel="nofollow">Working with EMail attachments</a> - by Jason Sherman, whom blogs about how to split emails with multiple  attachments into multiple messages with a single attachment each, for  further processing in Camel.</li><li><a shape="rect" class="external-link" href="http://thinkinginsoftware.blogspot.se/2012/05/using-quartz-camel-and-spring-for.html" rel="nofollow">Using Quartz, Camel and Spring for Distributed Service Orchestration</a> - by Nestor Urquiza blogs about using Quartz and Camel to build a distributed solution running a clustered Camel application on multiple Tomc
 at instances.</li><li><a shape="rect" class="external-link" href="http://blog.raulkr.net/2012/06/camel-and-mongodb-match-made-in-heaven.html" rel="nofollow">Camel and MongoDB: a match made in heaven</a> - Introduction to the Camel MongoDB component launched with the Camel 2.10 release.</li><li><a shape="rect" class="external-link" href="http://michalwarecki.blogspot.com/2012/07/eip-in-action.html" rel="nofollow">EIP in Action</a> - A blog post with 4 use-cases that demonstrates how to use EIPs in theory and Camel in practice.</li></ul>
 
 
 <h3><a shape="rect" name="Articles-Tooling%2FCombinationwithotherProducts"></a>Tooling / Combination with other Products</h3>

Modified: websites/production/camel/content/book-component-appendix.html
==============================================================================
--- websites/production/camel/content/book-component-appendix.html (original)
+++ websites/production/camel/content/book-component-appendix.html Mon Jul 16 07:19:57 2012
@@ -8904,6 +8904,8 @@ rnc:someLocalOrRemoteResource
 
 <div class="panelMacro"><table class="tipMacro"><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/check.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Transacted and caching</b><br clear="none">See section <em>Transactions and Cache Levels</em> below if you are using transactions with <a shape="rect" href="jms.html" title="JMS">JMS</a> as it can impact performance.</td></tr></table></div>
 
+<div class="panelMacro"><table class="tipMacro"><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/check.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Request/Reply over JMS</b><br clear="none">Make sure to read the section <em>Request-reply over JMS</em> further below on this page for important notes about request/reply, as Camel offers a number of options to configure for performance, and clustered environments.</td></tr></table></div>
+
 <p>The JMS component allows messages to be sent to (or consumed from) a <a shape="rect" class="external-link" href="http://java.sun.com/products/jms/" rel="nofollow">JMS</a> Queue or Topic. The implementation of the JMS Component uses Spring's JMS support for declarative transactions, using Spring's <tt>JmsTemplate</tt> for sending and a <tt>MessageListenerContainer</tt> for consuming.</p>
 
 <p>Maven users will need to add the following dependency to their <tt>pom.xml</tt> for this component:</p>
@@ -9000,7 +9002,7 @@ In Camel 2.8 onwards, the default settin
 
 <h4><a shape="rect" name="BookComponentAppendix-Mostcommonlyusedoptions"></a>Most commonly used options</h4>
 <div class="confluenceTableSmall"><div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"> Option </th><th colspan="1" rowspan="1" class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>clientId</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions. You may prefer to use <a shape="rect" class="external-link" href="http://activemq.apache.org/virtual-destinations.html">Virtual Topics</a> instead. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>concurrentConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="1" class
 ="confluenceTd"> Specifies the default number of concurrent consumers. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>disableReplyTo</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> If <tt>true</tt>, a producer will behave like a InOnly exchange with the exception that <tt>JMSReplyTo</tt> header is sent out and not be suppressed like in the case of <tt>InOnly</tt>. Like <tt>InOnly</tt> the producer will not wait for a reply. A consumer with this flag will behave like <tt>InOnly</tt>. This feature can be used to bridge <tt>InOut</tt> requests to another queue so that a route on the other queue will send it&#180;s response directly back to the original <tt>JMSReplyTo</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>durableSubscriptionName</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="c
 onfluenceTd"> The durable subscriber name for specifying durable topic subscriptions. The <tt>clientId</tt> option <b>must</b> be configured as well. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>maxConcurrentConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies the maximum number of concurrent consumers. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>preserveMessageQos</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Set to <tt>true</tt>, if you want to send message using the QoS settings specified on the message, instead of the QoS settings on the JMS endpoint. The following three headers are considered <tt>JMSPriority</tt>, <tt>JMSDeliveryMode</tt>, and <tt>JMSExpiration</tt>. You can provide all or only some of them. If not provided, Camel will fall back to u
 se the values from the endpoint instead. So, when using this option, the headers override the values from the endpoint. The <tt>explicitQosEnabled</tt> option, by contrast, will only use options set on the endpoint, and not values from the message header. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>replyTo</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Provides an explicit ReplyTo destination, which overrides any incoming value of <tt>Message.getJMSReplyTo()</tt>. If you do <a shape="rect" href="request-reply.html" title="Request Reply">Request Reply</a> over JMS then read the section further below for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>replyToType</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.9:</b> Allows for explicitly specifying
  which kind of strategy to use for replyTo queues when doing request/reply over JMS. Possible values are: <tt>Temporary</tt>, <tt>Shared</tt>, or <tt>Exclusive</tt>. By default Camel will use temporary queues. However if <tt>replyTo</tt> has been configured, then <tt>Shared</tt> is used by default. This option allows you to use exclusive queues instead of shared ones. See further below for more details, and especially the notes about the implications if running in a clustered environment. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>requestTimeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>20000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Producer only:</b> The timeout for waiting for a reply when using the InOut <a shape="rect" href="exchange-pattern.html" title="Exchange Pattern">Exchange Pattern</a> (in milliseconds). The default is 20 seconds. See below in section <em>About time to live</em> for more details.
  See also the <em>requestTimeoutCheckerInterval</em> option. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>selector</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Sets the JMS Selector, which is an SQL 92 predicate that is used to filter messages within the broker. You may have to encode special characters such as = as %3D <b>Before Camel 2.3.0</b>, we don't support this option in CamelConsumerTemplate </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>timeToLive</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> When sending messages, specifies the time-to-live of the message (in milliseconds). See below in section <em>About time to live</em> for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>transacted</tt> </td><td colspan="1" rowspan="1" cla
 ss="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies whether to use transacted mode for sending/receiving messages using the InOnly <a shape="rect" href="exchange-pattern.html" title="Exchange Pattern">Exchange Pattern</a>.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>testConnectionOnStartup</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.1:</b> Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. From <b>Camel 2.8</b> onwards also the JMS producers is tested as well. </td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"> Option </th><th colspan="1" rowspan="1" class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>clientId</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions. You may prefer to use <a shape="rect" class="external-link" href="http://activemq.apache.org/virtual-destinations.html">Virtual Topics</a> instead. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>concurrentConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="1" class
 ="confluenceTd"> Specifies the default number of concurrent consumers. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>disableReplyTo</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> If <tt>true</tt>, a producer will behave like a InOnly exchange with the exception that <tt>JMSReplyTo</tt> header is sent out and not be suppressed like in the case of <tt>InOnly</tt>. Like <tt>InOnly</tt> the producer will not wait for a reply. A consumer with this flag will behave like <tt>InOnly</tt>. This feature can be used to bridge <tt>InOut</tt> requests to another queue so that a route on the other queue will send it&#180;s response directly back to the original <tt>JMSReplyTo</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>durableSubscriptionName</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="c
 onfluenceTd"> The durable subscriber name for specifying durable topic subscriptions. The <tt>clientId</tt> option <b>must</b> be configured as well. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>maxConcurrentConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies the maximum number of concurrent consumers. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>preserveMessageQos</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Set to <tt>true</tt>, if you want to send message using the QoS settings specified on the message, instead of the QoS settings on the JMS endpoint. The following three headers are considered <tt>JMSPriority</tt>, <tt>JMSDeliveryMode</tt>, and <tt>JMSExpiration</tt>. You can provide all or only some of them. If not provided, Camel will fall back to u
 se the values from the endpoint instead. So, when using this option, the headers override the values from the endpoint. The <tt>explicitQosEnabled</tt> option, by contrast, will only use options set on the endpoint, and not values from the message header. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>replyTo</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Provides an explicit ReplyTo destination, which overrides any incoming value of <tt>Message.getJMSReplyTo()</tt>. If you do <a shape="rect" href="request-reply.html" title="Request Reply">Request Reply</a> over JMS then <b>make sure</b> to read the section <em>Request-reply over JMS</em> further below for more details, and the <tt>replyToType</tt> option as well. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>replyToType</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td
  colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.9:</b> Allows for explicitly specifying which kind of strategy to use for replyTo queues when doing request/reply over JMS. Possible values are: <tt>Temporary</tt>, <tt>Shared</tt>, or <tt>Exclusive</tt>. By default Camel will use temporary queues. However if <tt>replyTo</tt> has been configured, then <tt>Shared</tt> is used by default. This option allows you to use exclusive queues instead of shared ones. See further below for more details, and especially the notes about the implications if running in a clustered environment, and the fact that <tt>Shared</tt> reply queues has lower performance than its alternatives <tt>Temporary</tt> and <tt>Exclusive</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>requestTimeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>20000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Producer only:</b> The timeout for waiting for a
  reply when using the InOut <a shape="rect" href="exchange-pattern.html" title="Exchange Pattern">Exchange Pattern</a> (in milliseconds). The default is 20 seconds. See below in section <em>About time to live</em> for more details. See also the <em>requestTimeoutCheckerInterval</em> option. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>selector</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Sets the JMS Selector, which is an SQL 92 predicate that is used to filter messages within the broker. You may have to encode special characters such as = as %3D <b>Before Camel 2.3.0</b>, we don't support this option in CamelConsumerTemplate </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>timeToLive</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> When sending messages, specifies the tim
 e-to-live of the message (in milliseconds). See below in section <em>About time to live</em> for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>transacted</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies whether to use transacted mode for sending/receiving messages using the InOnly <a shape="rect" href="exchange-pattern.html" title="Exchange Pattern">Exchange Pattern</a>.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>testConnectionOnStartup</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.1:</b> Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures 
 that Camel is not started with failed connections. From <b>Camel 2.8</b> onwards also the JMS producers is tested as well. </td></tr></tbody></table>
 </div>
 
 
@@ -9242,8 +9244,16 @@ from(<span class="code-quote">"jms:SomeQ
 
 <h3><a shape="rect" name="BookComponentAppendix-RequestreplyoverJMS"></a>Request-reply over JMS</h3>
 
-<p>Camel supports <a shape="rect" href="request-reply.html" title="Request Reply">Request Reply</a> over JMS. In essence the MEP of the Exchange should be <tt>InOut</tt> when you send a message to a JMS queue.<br clear="none">
-The <tt>JmsProducer</tt> detects the <tt>InOut</tt> and provides a <tt>JMSReplyTo</tt> header with the reply destination to be used. By default Camel uses a temporary queue, but you can use the <tt>replyTo</tt> option on the endpoint to specify a fixed reply queue (see more below about fixed reply queue). </p>
+<p>Camel supports <a shape="rect" href="request-reply.html" title="Request Reply">Request Reply</a> over JMS. In essence the MEP of the Exchange should be <tt>InOut</tt> when you send a message to a JMS queue.</p>
+
+<p>Camel offers a number of options to configure request/reply over JMS that influence performance and clustered environments. The table below summaries the options.</p>
+
+<div class="confluenceTableSmall"><div class="table-wrap">
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"> Option </th><th colspan="1" rowspan="1" class="confluenceTh"> Performance </th><th colspan="1" rowspan="1" class="confluenceTh"> Cluster </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Temporary</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Fast </td><td colspan="1" rowspan="1" class="confluenceTd"> Yes </td><td colspan="1" rowspan="1" class="confluenceTd"> A temporary queue is used as reply queue, and automatic created by Camel. To use this do <b>not</b> specify a replyTo queue name. And you can optionally configure <tt>replyToType=Temporary</tt> to make it stand out that temporary queues are in use. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Shared</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Slow </td><td colspan="1" rowspan="1" class="conflue
 nceTd"> Yes </td><td colspan="1" rowspan="1" class="confluenceTd"> A shared persistent queue is used as reply queue. The queue must be created beforehand, although some brokers can create them on the fly such as Apache ActiveMQ. To use this you must specify the replyTo queue name. And you can optionally configure <tt>replyToType=Shared</tt> to make it stand out that shared queues are in use. A shared queue can be used in a clustered environment with multiple nodes running this Camel application at the same time. All using the same shared reply queue. This is possible because JMS Message selectors are used to correlate expected reply messages; this impacts performance though. JMS Message selectors is slower, and therefore not as fast as <tt>Temporary</tt> or <tt>Exclusive</tt> queues. See further below how to tweak this for better performance. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Exclusive</tt> </td><td colspan="1" rowspan="1" class="confluenceT
 d"> Fast </td><td colspan="1" rowspan="1" class="confluenceTd"> No </td><td colspan="1" rowspan="1" class="confluenceTd"> An exclusive persistent queue is used as reply queue. The queue must be created beforehand, although some brokers can create them on the fly such as Apache ActiveMQ. To use this you must specify the replyTo queue name. And you <b>must</b> configure <tt>replyToType=Exclusive</tt> to instruct Camel to use exclusive queues, as <tt>Shared</tt> is used by default, if a <tt>replyTo</tt> queue name was configured. When using exclusive reply queues, then JMS Message selectors are <b>not</b> in use, and therefore other applications must not use this queue as well. An exclusive queue <b>cannot</b> be used in a clustered environment with multiple nodes running this Camel application at the same time; as we do not have control if the reply queue comes back to the same node that sent the request message; that is why shared queues use JMS Message selectors to make sure
  of this. </td></tr></tbody></table>
+</div>
+</div>
+
+<p>The <tt>JmsProducer</tt> detects the <tt>InOut</tt> and provides a <tt>JMSReplyTo</tt> header with the reply destination to be used. By default Camel uses a temporary queue, but you can use the <tt>replyTo</tt> option on the endpoint to specify a fixed reply queue (see more below about fixed reply queue). </p>
 
 <p>Camel will automatic setup a consumer which listen on the reply queue, so you should <b>not</b> do anything.<br clear="none">
 This consumer is a Spring <tt>DefaultMessageListenerContainer</tt> which listen for replies. However it's fixed to 1 concurrent consumer.<br clear="none">

Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Mon Jul 16 07:19:57 2012
@@ -29396,6 +29396,8 @@ rnc:someLocalOrRemoteResource
 
 <div class="panelMacro"><table class="tipMacro"><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/check.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Transacted and caching</b><br clear="none">See section <em>Transactions and Cache Levels</em> below if you are using transactions with <a shape="rect" href="jms.html" title="JMS">JMS</a> as it can impact performance.</td></tr></table></div>
 
+<div class="panelMacro"><table class="tipMacro"><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/check.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Request/Reply over JMS</b><br clear="none">Make sure to read the section <em>Request-reply over JMS</em> further below on this page for important notes about request/reply, as Camel offers a number of options to configure for performance, and clustered environments.</td></tr></table></div>
+
 <p>The JMS component allows messages to be sent to (or consumed from) a <a shape="rect" class="external-link" href="http://java.sun.com/products/jms/" rel="nofollow">JMS</a> Queue or Topic. The implementation of the JMS Component uses Spring's JMS support for declarative transactions, using Spring's <tt>JmsTemplate</tt> for sending and a <tt>MessageListenerContainer</tt> for consuming.</p>
 
 <p>Maven users will need to add the following dependency to their <tt>pom.xml</tt> for this component:</p>
@@ -29492,7 +29494,7 @@ In Camel 2.8 onwards, the default settin
 
 <h4><a shape="rect" name="BookInOnePage-Mostcommonlyusedoptions"></a>Most commonly used options</h4>
 <div class="confluenceTableSmall"><div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"> Option </th><th colspan="1" rowspan="1" class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>clientId</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions. You may prefer to use <a shape="rect" class="external-link" href="http://activemq.apache.org/virtual-destinations.html">Virtual Topics</a> instead. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>concurrentConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="1" class
 ="confluenceTd"> Specifies the default number of concurrent consumers. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>disableReplyTo</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> If <tt>true</tt>, a producer will behave like a InOnly exchange with the exception that <tt>JMSReplyTo</tt> header is sent out and not be suppressed like in the case of <tt>InOnly</tt>. Like <tt>InOnly</tt> the producer will not wait for a reply. A consumer with this flag will behave like <tt>InOnly</tt>. This feature can be used to bridge <tt>InOut</tt> requests to another queue so that a route on the other queue will send it&#180;s response directly back to the original <tt>JMSReplyTo</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>durableSubscriptionName</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="c
 onfluenceTd"> The durable subscriber name for specifying durable topic subscriptions. The <tt>clientId</tt> option <b>must</b> be configured as well. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>maxConcurrentConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies the maximum number of concurrent consumers. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>preserveMessageQos</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Set to <tt>true</tt>, if you want to send message using the QoS settings specified on the message, instead of the QoS settings on the JMS endpoint. The following three headers are considered <tt>JMSPriority</tt>, <tt>JMSDeliveryMode</tt>, and <tt>JMSExpiration</tt>. You can provide all or only some of them. If not provided, Camel will fall back to u
 se the values from the endpoint instead. So, when using this option, the headers override the values from the endpoint. The <tt>explicitQosEnabled</tt> option, by contrast, will only use options set on the endpoint, and not values from the message header. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>replyTo</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Provides an explicit ReplyTo destination, which overrides any incoming value of <tt>Message.getJMSReplyTo()</tt>. If you do <a shape="rect" href="request-reply.html" title="Request Reply">Request Reply</a> over JMS then read the section further below for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>replyToType</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.9:</b> Allows for explicitly specifying
  which kind of strategy to use for replyTo queues when doing request/reply over JMS. Possible values are: <tt>Temporary</tt>, <tt>Shared</tt>, or <tt>Exclusive</tt>. By default Camel will use temporary queues. However if <tt>replyTo</tt> has been configured, then <tt>Shared</tt> is used by default. This option allows you to use exclusive queues instead of shared ones. See further below for more details, and especially the notes about the implications if running in a clustered environment. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>requestTimeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>20000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Producer only:</b> The timeout for waiting for a reply when using the InOut <a shape="rect" href="exchange-pattern.html" title="Exchange Pattern">Exchange Pattern</a> (in milliseconds). The default is 20 seconds. See below in section <em>About time to live</em> for more details.
  See also the <em>requestTimeoutCheckerInterval</em> option. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>selector</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Sets the JMS Selector, which is an SQL 92 predicate that is used to filter messages within the broker. You may have to encode special characters such as = as %3D <b>Before Camel 2.3.0</b>, we don't support this option in CamelConsumerTemplate </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>timeToLive</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> When sending messages, specifies the time-to-live of the message (in milliseconds). See below in section <em>About time to live</em> for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>transacted</tt> </td><td colspan="1" rowspan="1" cla
 ss="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies whether to use transacted mode for sending/receiving messages using the InOnly <a shape="rect" href="exchange-pattern.html" title="Exchange Pattern">Exchange Pattern</a>.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>testConnectionOnStartup</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.1:</b> Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. From <b>Camel 2.8</b> onwards also the JMS producers is tested as well. </td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"> Option </th><th colspan="1" rowspan="1" class="confluenceTh"> Default Value </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>clientId</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions. You may prefer to use <a shape="rect" class="external-link" href="http://activemq.apache.org/virtual-destinations.html">Virtual Topics</a> instead. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>concurrentConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="1" class
 ="confluenceTd"> Specifies the default number of concurrent consumers. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>disableReplyTo</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> If <tt>true</tt>, a producer will behave like a InOnly exchange with the exception that <tt>JMSReplyTo</tt> header is sent out and not be suppressed like in the case of <tt>InOnly</tt>. Like <tt>InOnly</tt> the producer will not wait for a reply. A consumer with this flag will behave like <tt>InOnly</tt>. This feature can be used to bridge <tt>InOut</tt> requests to another queue so that a route on the other queue will send it&#180;s response directly back to the original <tt>JMSReplyTo</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>durableSubscriptionName</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="c
 onfluenceTd"> The durable subscriber name for specifying durable topic subscriptions. The <tt>clientId</tt> option <b>must</b> be configured as well. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>maxConcurrentConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies the maximum number of concurrent consumers. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>preserveMessageQos</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Set to <tt>true</tt>, if you want to send message using the QoS settings specified on the message, instead of the QoS settings on the JMS endpoint. The following three headers are considered <tt>JMSPriority</tt>, <tt>JMSDeliveryMode</tt>, and <tt>JMSExpiration</tt>. You can provide all or only some of them. If not provided, Camel will fall back to u
 se the values from the endpoint instead. So, when using this option, the headers override the values from the endpoint. The <tt>explicitQosEnabled</tt> option, by contrast, will only use options set on the endpoint, and not values from the message header. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>replyTo</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Provides an explicit ReplyTo destination, which overrides any incoming value of <tt>Message.getJMSReplyTo()</tt>. If you do <a shape="rect" href="request-reply.html" title="Request Reply">Request Reply</a> over JMS then <b>make sure</b> to read the section <em>Request-reply over JMS</em> further below for more details, and the <tt>replyToType</tt> option as well. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>replyToType</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td
  colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.9:</b> Allows for explicitly specifying which kind of strategy to use for replyTo queues when doing request/reply over JMS. Possible values are: <tt>Temporary</tt>, <tt>Shared</tt>, or <tt>Exclusive</tt>. By default Camel will use temporary queues. However if <tt>replyTo</tt> has been configured, then <tt>Shared</tt> is used by default. This option allows you to use exclusive queues instead of shared ones. See further below for more details, and especially the notes about the implications if running in a clustered environment, and the fact that <tt>Shared</tt> reply queues has lower performance than its alternatives <tt>Temporary</tt> and <tt>Exclusive</tt>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>requestTimeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>20000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Producer only:</b> The timeout for waiting for a
  reply when using the InOut <a shape="rect" href="exchange-pattern.html" title="Exchange Pattern">Exchange Pattern</a> (in milliseconds). The default is 20 seconds. See below in section <em>About time to live</em> for more details. See also the <em>requestTimeoutCheckerInterval</em> option. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>selector</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Sets the JMS Selector, which is an SQL 92 predicate that is used to filter messages within the broker. You may have to encode special characters such as = as %3D <b>Before Camel 2.3.0</b>, we don't support this option in CamelConsumerTemplate </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>timeToLive</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> When sending messages, specifies the tim
 e-to-live of the message (in milliseconds). See below in section <em>About time to live</em> for more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>transacted</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies whether to use transacted mode for sending/receiving messages using the InOnly <a shape="rect" href="exchange-pattern.html" title="Exchange Pattern">Exchange Pattern</a>.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>testConnectionOnStartup</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.1:</b> Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures 
 that Camel is not started with failed connections. From <b>Camel 2.8</b> onwards also the JMS producers is tested as well. </td></tr></tbody></table>
 </div>
 
 
@@ -29734,8 +29736,16 @@ from(<span class="code-quote">"jms:SomeQ
 
 <h3><a shape="rect" name="BookInOnePage-RequestreplyoverJMS"></a>Request-reply over JMS</h3>
 
-<p>Camel supports <a shape="rect" href="request-reply.html" title="Request Reply">Request Reply</a> over JMS. In essence the MEP of the Exchange should be <tt>InOut</tt> when you send a message to a JMS queue.<br clear="none">
-The <tt>JmsProducer</tt> detects the <tt>InOut</tt> and provides a <tt>JMSReplyTo</tt> header with the reply destination to be used. By default Camel uses a temporary queue, but you can use the <tt>replyTo</tt> option on the endpoint to specify a fixed reply queue (see more below about fixed reply queue). </p>
+<p>Camel supports <a shape="rect" href="request-reply.html" title="Request Reply">Request Reply</a> over JMS. In essence the MEP of the Exchange should be <tt>InOut</tt> when you send a message to a JMS queue.</p>
+
+<p>Camel offers a number of options to configure request/reply over JMS that influence performance and clustered environments. The table below summaries the options.</p>
+
+<div class="confluenceTableSmall"><div class="table-wrap">
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"> Option </th><th colspan="1" rowspan="1" class="confluenceTh"> Performance </th><th colspan="1" rowspan="1" class="confluenceTh"> Cluster </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Temporary</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Fast </td><td colspan="1" rowspan="1" class="confluenceTd"> Yes </td><td colspan="1" rowspan="1" class="confluenceTd"> A temporary queue is used as reply queue, and automatic created by Camel. To use this do <b>not</b> specify a replyTo queue name. And you can optionally configure <tt>replyToType=Temporary</tt> to make it stand out that temporary queues are in use. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Shared</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Slow </td><td colspan="1" rowspan="1" class="conflue
 nceTd"> Yes </td><td colspan="1" rowspan="1" class="confluenceTd"> A shared persistent queue is used as reply queue. The queue must be created beforehand, although some brokers can create them on the fly such as Apache ActiveMQ. To use this you must specify the replyTo queue name. And you can optionally configure <tt>replyToType=Shared</tt> to make it stand out that shared queues are in use. A shared queue can be used in a clustered environment with multiple nodes running this Camel application at the same time. All using the same shared reply queue. This is possible because JMS Message selectors are used to correlate expected reply messages; this impacts performance though. JMS Message selectors is slower, and therefore not as fast as <tt>Temporary</tt> or <tt>Exclusive</tt> queues. See further below how to tweak this for better performance. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Exclusive</tt> </td><td colspan="1" rowspan="1" class="confluenceT
 d"> Fast </td><td colspan="1" rowspan="1" class="confluenceTd"> No </td><td colspan="1" rowspan="1" class="confluenceTd"> An exclusive persistent queue is used as reply queue. The queue must be created beforehand, although some brokers can create them on the fly such as Apache ActiveMQ. To use this you must specify the replyTo queue name. And you <b>must</b> configure <tt>replyToType=Exclusive</tt> to instruct Camel to use exclusive queues, as <tt>Shared</tt> is used by default, if a <tt>replyTo</tt> queue name was configured. When using exclusive reply queues, then JMS Message selectors are <b>not</b> in use, and therefore other applications must not use this queue as well. An exclusive queue <b>cannot</b> be used in a clustered environment with multiple nodes running this Camel application at the same time; as we do not have control if the reply queue comes back to the same node that sent the request message; that is why shared queues use JMS Message selectors to make sure
  of this. </td></tr></tbody></table>
+</div>
+</div>
+
+<p>The <tt>JmsProducer</tt> detects the <tt>InOut</tt> and provides a <tt>JMSReplyTo</tt> header with the reply destination to be used. By default Camel uses a temporary queue, but you can use the <tt>replyTo</tt> option on the endpoint to specify a fixed reply queue (see more below about fixed reply queue). </p>
 
 <p>Camel will automatic setup a consumer which listen on the reply queue, so you should <b>not</b> do anything.<br clear="none">
 This consumer is a Spring <tt>DefaultMessageListenerContainer</tt> which listen for replies. However it's fixed to 1 concurrent consumer.<br clear="none">

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



Mime
View raw message