Re: deadLetterHandleNewException(false) seems to not work as expected

Hi, But that's exactly what I found confusing: the option name "deadLetterHandle*New*Exception" suggests that we are configuring the behavior of the DeadLetterChannel in the case of a new exception only, while we actually also disable the handling of the original exception... The unit test you li

Re: deadLetterHandleNewException(false) seems to not work as expected

- Bump - Still having to work around the issue. Anyone having an idea ? -- View this message in context: http://camel.465427.n5.nabble.com/deadLetterHandleNewException-false-seems-to-not-work-as-expected-tp5775138p5776020.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel / SpringBoot integration - Invalid shutdown sequence

Done ! CAMEL-9431 -- View this message in context: http://camel.465427.n5.nabble.com/Camel-SpringBoot-integration-Invalid-shutdown-sequence-tp5775220p5775223.html Sent from the Camel - Users mailing list archive at Nabble.com.

Camel / SpringBoot integration - Invalid shutdown sequence

I ran into the following problem when using autoconfiguration provided by /camel-spring-boot/ artifact. By default, there is a configuration classes that automatically registers a /TypeConverter/ bean into the Spring context: The returned bean is an instance of /DefaultTypeConverter/, which in tu

deadLetterHandleNewException(false) seems to not work as expected

I am trying to use the option /deadLetterHandleNewException(false)/ in order to have any new Exception occurring during the dead letter processing be propagated back. Unfortunately, when doing so, it seems that the dead letter channel propagates back the original exception as well, even if the Dead