svn commit: r996895 [2/3] - in /websites/production/camel/content: book-component-appendix.html book-in-one-page.html cache/main.pageCache jms.html
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 Wed Sep 7 22:19:06 2016 @@ -3625,11 +3625,11 @@ The tutorial has been designed in two pa While not actual tutorials you might find working through the source of the various Examples useful. Tutorial on Spring Remoting with JMSThanksThis tutorial was kindly donated to Apache Camel by Martin Gilday.PrefaceThis 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 http://www.springramework.org; rel="nofollow">Spring service. The route works in a synchronous fashion returning a response to the client./**/ +/*]]>*/ Tutorial on Spring Remoting with JMSPrefacePrerequisitesDistributionAboutCreate the Camel Project Update the POM with Dependencies Writing the Server @@ -5744,11 +5744,11 @@ So we completed the last piece in the pi This example has been removed from Camel 2.9 onwards. Apache Axis 1.4 is a very old and unsupported framework. We encourage users to use CXF instead of Axis. /**/ +/*]]>*/ Tutorial using Axis 1.4 with Apache Camel PrerequisitesDistributionIntroductionSetting up the project to run Axis Maven 2wsdlConfiguring AxisRunning the Example @@ -17175,11 +17175,11 @@ template.send(direct:alias-verify& ]]> See Also Configuring CamelComponentEndpointGetting StartedCrypto Crypto is also available as a Data Format CXF ComponentWhen using CXF as a consumer, the CXF Bean Component allows you to factor out how message payloads are received from their processing as a RESTful or SOAP web service. This has the potential of using a multitude of transports to consume web services. The bean component's configuration is also simpler and provides the fastest method to implement web services using Camel and CXF.When using CXF in streaming modes (see DataFormat option), then also read about Stream caching.The cxf: component provides integration with http://cxf.apache.org;>Apache CXF for connecting to JAX-WS services hosted in CXF./**/ +/*]]>*/ CXF Component URI formatOptions The descriptions of the dataformats @@ -21514,7 +21514,7 @@ rnc:someLocalOrRemoteResource]]>To connect to a topic, you must include the topic: prefix. For example, to connect to the topic, Stocks.Prices, use: -You append query options to the URI using the following format: ?option=valueoption=value...NotesUsing ActiveMQThe JMS component reuses Spring 2's JmsTemplate for sending messages. This is not ideal for use in a non-J2EE container and typically requires some caching in the JMS provider to avoid http://activemq.apache.org/jmstemplate-gotchas.html;>poor performance.If you intend to use http://activemq.apache.org/;>Apache ActiveMQ as your Message Broker - which is a good choice as ActiveMQ rocks https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/smile.png; data-emoticon-name="smile" alt="(smile)"> , then we recommend that you either:Use the ActiveMQ component, which is already optimized to use ActiveMQ efficientlyUse the PoolingConnectionFactory in ActiveMQTransactions and Cache Levels If you are consuming messages and using transactions (transacted=true) then the default cache level can negatively impact performance. If you are using XA transactions then you cannot cache as it can cause the XA transaction to not work properly.If you are not using XA, then you shoul d consider caching as it speeds up performance, such as setting cacheLevelName=CACHE_CONSUMER. Through Camel 2.7.x, the default setting for cacheLevelName is CACHE_CONSUMER. You will
svn commit: r996895 [3/3] - in /websites/production/camel/content: book-component-appendix.html book-in-one-page.html cache/main.pageCache jms.html
Modified: websites/production/camel/content/jms.html == --- websites/production/camel/content/jms.html (original) +++ websites/production/camel/content/jms.html Wed Sep 7 22:19:06 2016 @@ -106,7 +106,7 @@ To connect to a topic, you must include the topic: prefix. For example, to connect to the topic, Stocks.Prices, use: -You append query options to the URI using the following format: ?option=valueoption=value...NotesUsing ActiveMQThe JMS component reuses Spring 2's JmsTemplate for sending messages. This is not ideal for use in a non-J2EE container and typically requires some caching in the JMS provider to avoid http://activemq.apache.org/jmstemplate-gotchas.html;>poor performance.If you intend to use http://activemq.apache.org/;>Apache ActiveMQ as your Message Broker - which is a good choice as ActiveMQ rocks https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/smile.png; data-emoticon-name="smile" alt="(smile)"> , then we recommend that you either:Use the ActiveMQ component, which is already optimized to use ActiveMQ efficientlyUse the PoolingConnectionFactory in ActiveMQTransactions and Cache Levels If you are consuming messages and using transactions (transacted=true) then the default cache level can negatively impact performance. If you are using XA transactions then you cannot cache as it can cause the XA transaction to not work properly.If you are not using XA, then you should consider caching as it speed s up performance, such as setting cacheLevelName=CACHE_CONSUMER. Through Camel 2.7.x, the default setting for cacheLevelName is CACHE_CONSUMER. You will need to explicitly set cacheLevelName=CACHE_NONE. In Camel 2.8 onward, the default setting for cacheLevelName is CACHE_AUTO. This default auto detects the mode and sets the cache level accordingly to:CACHE_CONSUMER whentransacted=falseCACHE_NONE whentransacted=trueSo you can say the default setting is conservative. Consider using cacheLevelName=CACHE_CONSUMER if you are using non-XA transactions.Durable SubscriptionsIf you wish to use durable topic subscriptions, >you need to specify bothclientId >and durableSubscriptionName. The value of >the clientId must be unique and can only be >used by a single JMS connection instance in your entire network. You may >prefer to use href="http://activemq.apache.org/virtual-destinations.html;>Virtual >Topics instead to avoid this limitation. More background on durable >messaging href="http://activemq.apache.org/how-do-durable-queues-and-topics-work.html;>here. id="JMS-MessageHeaderMapping">Message Header MappingWhen using >message headers, the JMS specification states that header names must be valid >Java identifiers. So try to name your headers to be valid Java identifiers. >One benefit of doing this is that you can then use your headers in side a JMS Selector (whose SQL92 syntax mandates Java identifier syntax for headers).A simple strategy for mapping header names is used by default. The strategy is to replace any dots and hyphens in the header name as shown below and to reverse the replacement when the header name is restored from a JMS message sent over the wire. What does this mean? No more losing method names to invoke on a bean component, no more losing the filename header for the File Component, and so on.The current header name strategy for accepting header names in Camel is:Dots are replaced by _DOT_ and the replacement is reversed when Camel consume the messageHyphen is replaced by _HYPHEN_ and the replacement is reversed when Camel consumes the messageConfiguration OptionsYou can configure many different properties on the JMS endpo int which map to properties on the http://camel.apache.org/maven/current/camel-jms/apidocs/org/apache/camel/component/jms/JmsConfiguration.html;>JMSConfiguration POJO.Mapping to Spring JMSMany of these properties map to properties on Spring JMS, which Camel uses for sending and receiving messages. Therefore for more information about these properties consult the Spring documentation.The options are divided into two tables, the first one contains the most common options. The second table contains the less common and more advanced options.Common OptionsOptionDefault ValueDescriptionclientIdnullSets 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 http://activemq.apache.org/virtual-destinations.html;>Virtual Topics instead.concurrentConsumers1 Specifies the default number of concurrent consumers.From Camel 2.10.3: this option can also be used when doing request/reply over JMS.From Camel 2.16: there is a new replyToConcurrentConsumers. See also the
svn commit: r996895 [1/3] - in /websites/production/camel/content: book-component-appendix.html book-in-one-page.html cache/main.pageCache jms.html
Author: buildbot Date: Wed Sep 7 22:19:06 2016 New Revision: 996895 Log: Production update by buildbot for camel Modified: websites/production/camel/content/book-component-appendix.html websites/production/camel/content/book-in-one-page.html websites/production/camel/content/cache/main.pageCache websites/production/camel/content/jms.html Modified: websites/production/camel/content/book-component-appendix.html == --- websites/production/camel/content/book-component-appendix.html (original) +++ websites/production/camel/content/book-component-appendix.html Wed Sep 7 22:19:06 2016 @@ -1042,11 +1042,11 @@ template.send(direct:alias-verify& ]]> See Also Configuring CamelComponentEndpointGetting StartedCrypto Crypto is also available as a Data Format CXF ComponentWhen using CXF as a consumer, the CXF Bean Component allows you to factor out how message payloads are received from their processing as a RESTful or SOAP web service. This has the potential of using a multitude of transports to cons ume web services. The bean component's configuration is also simpler and provides the fastest method to implement web services using Camel and CXF.When using CXF in streaming modes (see DataFormat option), then also read about Stream caching.The cxf: component provides integration with http://cxf.apache.org;>Apache CXF for connecting to JAX-WS services hosted in CXF./**/ +/*]]>*/ CXF Component URI formatOptions The descriptions of the dataformats @@ -5381,7 +5381,7 @@ rnc:someLocalOrRemoteResource]]>To connect to a topic, you must include the topic: prefix. For example, to connect to the topic, Stocks.Prices, use: -You append query options to the URI using the following format: ?option=valueoption=value...NotesUsing ActiveMQThe JMS component reuses Spring 2's JmsTemplate for sending messages. This is not ideal for use in a non-J2EE container and typically requires some caching in the JMS provider to avoid http://activemq.apache.org/jmstemplate-gotchas.html;>poor performance.If you intend to use http://activemq.apache.org/;>Apache ActiveMQ as your Message Broker - which is a good choice as ActiveMQ rocks https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/smile.png; data-emoticon-name="smile" alt="(smile)"> , then we recommend that you either:Use the ActiveMQ component, which is already optimized to use ActiveMQ efficientlyUse the PoolingConnectionFactory in ActiveMQTransactions and Cache Levels If you are consuming messages and using transactions (transacted=true) then the default cache level can negatively impact performance. If you are using XA transactions then you cannot cache as it can cause the XA transaction to not work properly.If you are not using XA, then you should consider caching as it speeds up performance, such as setting cacheLevelName=CACHE_CONSUMER. Through Camel 2.7.x, the default setting for cacheLevelName is CACHE_CONSUMER. You will need to explicitly set cacheLevelName=CACHE_NONE. In Camel 2.8 onward, the default setting for cacheLevelName is CACHE_AUTO. This default auto detects the mode and sets the cache level accordingly to:CACHE_CONSUMER whentransacted=falseCACHE_NONE whentransacted=trueSo you can say the default setting is conservative. Consider using cacheLevelName=CACHE_CONSUMER if you are using non -XA transactions.Durable SubscriptionsIf you wish to use durable topic subscriptions, you need to specify bothclientId and durableSubscriptionName. The value of the clientId must be unique and can only be used by a single JMS connection instance in your entire network. You may prefer to use http://activemq.apache.org/virtual-destinations.html;>Virtual Topics instead to avoid this limitation. More background on durable messaging http://activemq.apache.org/how-do-durable-queues-and-topics-work.html;>here.Message Header MappingWhen using message headers, the JMS specification states that header names must be valid Java identifiers. So try to name your headers to be valid Java identifiers. One benefit of doing this is that you can then use your headers inside a JMS Selector (whose SQL92 syntax mandates Java identifier syntax for headers).A simple strategy for mapping header names is used by default. The strategy is to replace any dots and hyphens in the header name as shown below and to reverse the replacement when the header name is restored from a JMS message sent over the wire. What
svn commit: r996892 [1/3] - in /websites/production/camel/content: book-component-appendix.html book-in-one-page.html cache/main.pageCache jms.html
Author: buildbot Date: Wed Sep 7 21:20:53 2016 New Revision: 996892 Log: Production update by buildbot for camel Modified: websites/production/camel/content/book-component-appendix.html websites/production/camel/content/book-in-one-page.html websites/production/camel/content/cache/main.pageCache websites/production/camel/content/jms.html Modified: websites/production/camel/content/book-component-appendix.html == --- websites/production/camel/content/book-component-appendix.html (original) +++ websites/production/camel/content/book-component-appendix.html Wed Sep 7 21:20:53 2016 @@ -1042,11 +1042,11 @@ template.send(direct:alias-verify& ]]> See Also Configuring CamelComponentEndpointGetting StartedCrypto Crypto is also available as a Data Format CXF ComponentWhen using CXF as a consumer, the CXF Bean Component allows you to factor out how message payloads are received from their processing as a RESTful or SOAP web service. This has the potential of using a multitude of transports to cons ume web services. The bean component's configuration is also simpler and provides the fastest method to implement web services using Camel and CXF.When using CXF in streaming modes (see DataFormat option), then also read about Stream caching.The cxf: component provides integration with http://cxf.apache.org;>Apache CXF for connecting to JAX-WS services hosted in CXF./**/ +/*]]>*/ CXF Component URI formatOptions The descriptions of the dataformats @@ -5361,7 +5361,7 @@ rnc:someLocalOrRemoteResource]]> See Also -Configuring CamelComponentEndpointGetting Started JMS ComponentUsing ActiveMQIf you are using http://activemq.apache.org/;>Apache ActiveMQ, you should prefer the ActiveMQ component as it has been optimized for ActiveMQ. All of the options and samples on this page are also valid for the ActiveMQ comp onent.Transacted and cachingSee section Transactions and Cache Levels below if you are using transactions with JMS as it can impact performance.Request/Reply over JMSMake sure to read the section Request-reply over JMS 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.Thiscomponent allows messages to be sent to (or consumed from) a http://java.sun.com/products/jms/; rel="nofollow">JMS Queue or Topic. It uses Spring's JMS support for declarative transactions, including Spring's JmsTemplate for sending and a MessageListenerContainer for consuming.Maven users will need to add the following dependency to their pom.xml for this component: +Configuring CamelComponentEndpointGetting Started JMS ComponentUsing ActiveMQIf you are using http://activemq.apache.org/;>Apache ActiveMQ, you should prefer the ActiveMQ component as it has been optimized for ActiveMQ. All of the options and samples on this page are also valid for the ActiveMQ comp onent.Transacted and cachingSee section Transactions and Cache Levels below if you are using transactions with JMS as it can impact performance.Request/Reply over JMSMake sure to read the section Request-reply over JMS 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.Thiscomponent allows messages to be sent to (or consumed from) a http://java.sun.com/products/jms/; rel="nofollow">JMS Queue or Topic. It uses Spring's JMS support for declarative transactions, including Spring's JmsTemplate for sending and a MessageListenerContainer for consuming.Maven users will need to add the following dependency to their pom.xml for this component: