From c6315609689f5f1ef816e78a5f253127fa6a5a71 Mon Sep 17 00:00:00 2001 From: Gary Russell Date: Wed, 4 Mar 2015 17:40:42 -0500 Subject: [PATCH] INT-3670: JMS Doc Polishing --- src/reference/docbook/jms.xml | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/src/reference/docbook/jms.xml b/src/reference/docbook/jms.xml index 87172bc189..a9f0b8968a 100644 --- a/src/reference/docbook/jms.xml +++ b/src/reference/docbook/jms.xml @@ -144,9 +144,11 @@ 'error-channel' should also be one-way. For example, it could simply send to a logging handler, or it could be connected to a different JMS <outbound-channel-adapter> element. - + + Inbound Conversion Errors Starting with version 4.2 the 'error-channel' is used for the conversion errors, too. - Previously, if a JMS <message-driven-channel-adapter> or <inbound gateway> could + Previously, if a JMS <message-driven-channel-adapter/> + or <inbound-gateway/> could not deliver a message due to a conversion error, an exception would be thrown back to the container. If the container was configured to use transactions, the message would be rolled back and redelivered repeatedly. The conversion process occurs before and during @@ -156,7 +158,7 @@ defined, the integration flow on the 'error-channel' must re-throw the exception (or another). If the error flow does not throw an exception, the transaction will be committed and the message removed. If no 'error-channel' is defined, the exception is thrown back to the container, as before. - +
@@ -252,6 +254,9 @@ the "nullChannel" to suppress the errors, or you could leave 'error-channel' out to let the Exception propagate. + + See . +