Hi
You can enable the soapFault=true on the CamelContext which turns
faults into exceptions.
Or you can simply add a processor step at the end of your route, and
check if the exchange is a fault
public void process(Exchange exchange) {
boolean isFault = exchange.hasOut() && exchange.getOut().isF
Hi,
I have a route that looks like this:
from( sourceEndpoint )
.onException( java.lang.Throwable.class
).process( new Processor() {
public void process(Exchange exchange)
throws Exception
{
Hi,
We are heavily using DSL routers to route messages from one bean to another
within our messaging application.
All the examples I find in the documentation using beans always show the
bean name and the method name as a string. This is fine and it works but
when we are debugging a DSL router a
I have converted the camel-jetty test to a standard spring inegration
test. Interestingly I did not need the Camel test classes (at least for
this case).
The test already only starts the spring context once. I had to reset the
mock endpoint but that was the only change I had to do to avoid side
