Camel NotifyBuilder does not match when exception is thrown

I asked this question on stack overflow but didn't get a response so asking here https://stackoverflow.com/questions/78720143/camel-notifybuilder-does-not-match-when-exception-is-thrown It seems that camel's NotifyBuilder works in normal messag

Re: Camel NotifyBuilder does not match when exception is thrown

e(); assertThat(notifierB.matches(5, TimeUnit.SECONDS)).isTrue(); assertThat(notifierDead.matches(5, TimeUnit.SECONDS)).isTrue(); } On Thu, 11 Jul 2024 at 12:04, Claus Ibsen wrote: > Hi > > whenFrom is from the original route, so that would be "direct:route-a" > > You can use fromCurr

setExceptionListener(...) for SjmsComponent and Sjsm2Component

I'd like to set an exception listener for all topics using "sjms2" but SjmsComponent is missing a setExceptionListener(...) method https://github.com/apache/camel/blob/main/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/SjmsComponent.java You can see that the "jms" component h

Re: setExceptionListener(...) for SjmsComponent and Sjsm2Component

R against main branch > > On Wed, Jun 15, 2022 at 10:35 AM Lance Java > wrote: > > > I'd like to set an exception listener for all topics using "sjms2" but > > SjmsComponent is missing a setExceptionListener(...) method > > > > > https://github.com/a

Bluetooth

Hi, is there an API to connect to bluetooth? I've searched the mailing lists but cannot find any reference to a bluetooth endpoint. FYI, my end goal is to send an image to a pogo printer [1] [1] http://store.polaroid.com/product/9/538437/CZA-10011/_/PoGo%26%238482%3B_Instant_Mobile_Printer -- V

Passing parameters as headers feels a bit hacky

Hi, I'm a newbie to Camel and I'm currently evaluating the product. I am reading through the http://camel.apache.org/tutorial-example-reportincident-part5.html ReportIncident tutorial and I see the following example: from(cxfEndpoint) .setHeader(FileComponent.HEADER_FILE_NAME, BeanLanguage.b

Re: Passing parameters as headers feels a bit hacky

I'm sure it could be kept generic if every endpoint was able to accept it's own Configuration object (ie FileEndpoint accepts FileEndpointConfig and FtpEndpoint accepts FtpEndpointConfig). 1. By using headers, am I correct to assume that these headers are passed to every endpoint (not just the fil