Could you do something like -
from("jbi:service:http://a.com/b/camelFlowToIps";).
to("jbi:service:urn:wsdl.a.ips.b.com/2010-01/PrimeIntegratedProductService?mep=in-out
").errorHandler(deadLetterChannel("log:errors"))
.process(new IPSAckResponse());
And provide a second queue or file on the JBI side that you then re-
polled?
L.S.,
Could you send me more details about the route and the MEPs you're
using -- I'm guessing it's InOnly or RobustInOnly, right? And are
these fault messages you're trying to handle or exchanges that end in
error? Also, could you enable DEBUG logging and see what that says
about the exception being handled.
Regards,
Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
2009/9/26 iocanel <[email protected]>:
Thanks Gert for the quick response.
The solution you proposed disabled the camel error handler, however
the
failure did not propagate back to the Jms Consumer. So when an
error occurs
I can't have a Jms Redelivery.
It seems that if I use errorHandler(noErrorHandler()); in my camel
route
builder the error goes to a black whole instead of traveling back
to the jms
consumer.
Any ideas?
--
View this message in context:
http://www.nabble.com/servicemix-camel-and-error-handling-tp25623679p25625927.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Johan Edstrom
[email protected]
They that can give up essential liberty to purchase a little temporary
safety, deserve neither liberty nor safety.
Benjamin Franklin, Historical Review of Pennsylvania, 1759
