Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Not A Problem
-
servicemix-camel-2008.01
-
None
-
Proposed 3.3 release (http://people.apache.org/~ffang/servicemix3.3-2nd-try/)
with smx-camel-2008.01 component patched to include camel-core-1.5.0.jar and camel-spring-1.5.0.jar
from http://people.apache.org/~hadrian/apache-camel-1.5.0-RC1/maven2/org/apache/camel/apache-camel/1.5.0/apache-camel-1.5.0.zip.Proposed 3.3 release ( http://people.apache.org/~ffang/servicemix3.3-2nd-try/ ) with smx-camel-2008.01 component patched to include camel-core-1.5.0.jar and camel-spring-1.5.0.jar from http://people.apache.org/~hadrian/apache-camel-1.5.0-RC1/maven2/org/apache/camel/apache-camel/1.5.0/apache-camel-1.5.0.zip .
Description
I have a variant of the cxf-wsdl-first example that includes a smx-cxf-bc (in-out) consumer <> smx-camel errorHandler w/handleFault="true" <> smx-cxf-bc (in-out) provider <> JMS BROKER <> smx-cxf-bc (in-out) consumer <-> smx-cxf-se.
I use client.html to send a request with no personId which triggers the smx-cxf-se PersonImpl class to throw an UnknownPersonFault. The smx-camel errorHandler does not intercept the JBIFault and redeliver as expected.
I have attached a test case, my patched servicemix-camel-2008.01-updated-installer.zip, and the corresponding servicemix.log. In order to exercise the test,
1. deploy wsdl-first-cxf-sa-3.3.zip from the test case archive
2. open client.html from the test case archive in a browser, delete the personId value, then click send.
3. notice that the camel errorHandler performs no redeliveries