camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From acosent...@apache.org
Subject [3/3] camel git commit: CAMEL-10666: Regenerated docs and camel-jms-starter
Date Mon, 09 Jan 2017 11:52:21 GMT
CAMEL-10666: Regenerated docs and camel-jms-starter


Project: http://git-wip-us.apache.org/repos/asf/camel/repo
Commit: http://git-wip-us.apache.org/repos/asf/camel/commit/c8b835e6
Tree: http://git-wip-us.apache.org/repos/asf/camel/tree/c8b835e6
Diff: http://git-wip-us.apache.org/repos/asf/camel/diff/c8b835e6

Branch: refs/heads/master
Commit: c8b835e6fb6c40398d5de6c5ee37fd5f9c4c6fc2
Parents: 2f29e50
Author: Andrea Cosentino <ancosen@gmail.com>
Authored: Mon Jan 9 12:51:28 2017 +0100
Committer: Andrea Cosentino <ancosen@gmail.com>
Committed: Mon Jan 9 12:51:28 2017 +0100

----------------------------------------------------------------------
 .../jms/springboot/JmsComponentConfiguration.java    | 15 +++++++++++++++
 .../camel-jms/src/main/docs/jms-component.adoc       |  3 ++-
 2 files changed, 17 insertions(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/camel/blob/c8b835e6/components-starter/camel-jms-starter/src/main/java/org/apache/camel/component/jms/springboot/JmsComponentConfiguration.java
----------------------------------------------------------------------
diff --git a/components-starter/camel-jms-starter/src/main/java/org/apache/camel/component/jms/springboot/JmsComponentConfiguration.java
b/components-starter/camel-jms-starter/src/main/java/org/apache/camel/component/jms/springboot/JmsComponentConfiguration.java
index 3fd040a..d367b3a 100644
--- a/components-starter/camel-jms-starter/src/main/java/org/apache/camel/component/jms/springboot/JmsComponentConfiguration.java
+++ b/components-starter/camel-jms-starter/src/main/java/org/apache/camel/component/jms/springboot/JmsComponentConfiguration.java
@@ -1610,6 +1610,13 @@ public class JmsComponentConfiguration {
          */
         private Boolean transferExchange;
         /**
+         * Controls whether or not to include serialized headers. Applies only
+         * when {@link #isTransferExchange()} is {@code true} . This requires
+         * that the objects are serializable. Camel will exclude any
+         * non-serializable objects and log it at WARN level.
+         */
+        private Boolean allowSerializedHeaders;
+        /**
          * If enabled and you are using Request Reply messaging (InOut) and an
          * Exchange failed on the consumer side, then the caused Exception will
          * be send back in response as a javax.jms.ObjectMessage. If the client
@@ -2339,6 +2346,14 @@ public class JmsComponentConfiguration {
             this.transferExchange = transferExchange;
         }
 
+        public Boolean getAllowSerializedHeaders() {
+            return allowSerializedHeaders;
+        }
+
+        public void setAllowSerializedHeaders(Boolean allowSerializedHeaders) {
+            this.allowSerializedHeaders = allowSerializedHeaders;
+        }
+
         public Boolean getTransferException() {
             return transferException;
         }

http://git-wip-us.apache.org/repos/asf/camel/blob/c8b835e6/components/camel-jms/src/main/docs/jms-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-jms/src/main/docs/jms-component.adoc b/components/camel-jms/src/main/docs/jms-component.adoc
index 7062947..0647fd7 100644
--- a/components/camel-jms/src/main/docs/jms-component.adoc
+++ b/components/camel-jms/src/main/docs/jms-component.adoc
@@ -320,7 +320,7 @@ Endpoint options
 
 
 // endpoint options: START
-The JMS component supports 85 endpoint options which are listed below:
+The JMS component supports 86 endpoint options which are listed below:
 
 {% raw %}
 [width="100%",cols="2,1,1m,1m,5",options="header"]
@@ -374,6 +374,7 @@ The JMS component supports 85 endpoint options which are listed below:
 | includeSentJMSMessageID | producer (advanced) | false | boolean | Only applicable when
sending to JMS destination using InOnly (eg fire and forget). Enabling this option will enrich
the Camel Exchange with the actual JMSMessageID that was used by the JMS client when the message
was sent to the JMS destination.
 | replyToCacheLevelName | producer (advanced) |  | String | Sets the cache level by name
for the reply consumer when doing request/reply over JMS. This option only applies when using
fixed reply queues (not temporary). Camel will by default use: CACHE_CONSUMER for exclusive
or shared w/ replyToSelectorName. And CACHE_SESSION for shared without replyToSelectorName.
Some JMS brokers such as IBM WebSphere may require to set the replyToCacheLevelName=CACHE_NONE
to work. Note: If using temporary queues then CACHE_NONE is not allowed and you must use a
higher value such as CACHE_CONSUMER or CACHE_SESSION.
 | replyToDestinationSelectorName | producer (advanced) |  | String | Sets the JMS Selector
using the fixed name to be used so you can filter out your own replies from the others when
using a shared queue (that is if you are not using a temporary reply queue).
+| allowSerializedHeaders | advanced | false | boolean | Controls whether or not to include
serialized headers. Applies only when link isTransferExchange() is true. This requires that
the objects are serializable. Camel will exclude any non-serializable objects and log it at
WARN level.
 | asyncStartListener | advanced | false | boolean | Whether to startup the JmsConsumer message
listener asynchronously when starting a route. For example if a JmsConsumer cannot get a connection
to a remote JMS broker then it may block while retrying and/or failover. This will cause Camel
to block while starting routes. By setting this option to true you will let routes startup
while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous
mode. If this option is used then beware that if the connection could not be established then
an exception is logged at WARN level and the consumer will not be able to receive messages;
You can then restart the route to retry.
 | asyncStopListener | advanced | false | boolean | Whether to stop the JmsConsumer message
listener asynchronously when stopping a route.
 | destinationResolver | advanced |  | DestinationResolver | A pluggable org.springframework.jms.support.destination.DestinationResolver
that allows you to use your own resolver (for example to lookup the real destination in a
JNDI registry).


Mime
View raw message