Re: Re: interceptSendToEndpoint interceptedUri, scope and when issues

Hi You cannot do route scoped intercepting, it's always global scoped. The XML DSL just has a "flaw" as it is auto generated that it may expose the intercept as being available inside a element. On Tue, May 18, 2021 at 10:04 PM Yasser Zamani wrote: > > > > On 2021/05/18 18:03:47 Claus Ibsen wr

Re: Re: interceptSendToEndpoint interceptedUri, scope and when issues

Hi The after is always executed, however you can argue that it should not when you have a when filter. https://issues.apache.org/jira/browse/CAMEL-16629 On Tue, May 18, 2021 at 10:04 PM Yasser Zamani wrote: > > > > On 2021/05/18 18:03:47 Claus Ibsen wrote: > > Hi > > > > That is because you use

Re: SMTPS Throws Error

Hi Sending emails to google mail, via smtp is likely harder than trying to use the camel-google-mail component. If you need a test email server, then you can find smtp mail servers you can run as docker containers to use for testing purposes. On Wed, May 19, 2021 at 2:40 AM Mike Oliver wrote: >

SMTPS Throws Error

Trying to use Camel to send an email but getting the following error... javax.mail.MessagingException: Could not connect to SMTP host: smtp.gmail.com, port: 465; nested exception is: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPat

Re: Re: interceptSendToEndpoint interceptedUri, scope and when issues

On 2021/05/18 18:03:47 Claus Ibsen wrote: > Hi > > That is because you use toD with http that camel optimizes under the > hood to use a base endpoint and using headers with the dynamic > context-path part. > The interceptor can then not match that pattern. > > You can turn this off in toD > Or

Re: interceptSendToEndpoint interceptedUri, scope and when issues

Hi That is because you use toD with http that camel optimizes under the hood to use a base endpoint and using headers with the dynamic context-path part. The interceptor can then not match that pattern. You can turn this off in toD Or you can check the header (CamelHttpPath is the name I think) i

Re: interceptSendToEndpoint interceptedUri, scope and when issues

Thanks for the quick reply! (please see in-line) On 2021/05/18 15:59:34, Claus Ibsen wrote: > Hi > > What Camel version do you use? I use Camel 3.7.3. > > Also mind about matching by exact uri, then the order of the query > parameters also matter. So if that is not really what you need, the

Re: interceptSendToEndpoint interceptedUri, scope and when issues

Hi What Camel version do you use? Also mind about matching by exact uri, then the order of the query parameters also matter. So if that is not really what you need, then use a * to match with wildcard On Tue, May 18, 2021 at 5:17 PM Yasser Zamani wrote: > > Hi there, > > Assume following XML DS

Re: Update Logging Levels of Camel routes using Spring Boot Actuator

Yeah. This seems odd. I was looking at this on my phone last night so it was tough to see but see what you are doing now. Hopefully one of the Camel devs will know. On Tue, May 18, 2021 at 5:43 AM Simon Loy wrote: > Thanks for responding Mark, > > To clarify I can change the logging level of the

interceptSendToEndpoint interceptedUri, scope and when issues

Hi there, Assume following XML DSL: ${headers.messageType} != null && ${headers.serviceType} != null ${headers.messageType} == 'Property' . . . I found sever

Re: Update Logging Levels of Camel routes using Spring Boot Actuator

Thanks for responding Mark, To clarify I can change the logging level of the route to any level below and to the initial INFO level - I can change between ERROR, WARN and INFO and see the requisite changes in the apps logging. This issue seems to arise whenever I want to raise it above INFO, f

Re: How to override CXF version for Camel-CXF

You can try to override the dependency by dependency exclusion on camel-cxf, but it's not a best practice. We can eventually update on the LTS branch and release for 3.7.5 Il giorno mar 18 mag 2021 alle ore 11:34 Chio Chuan Ooi ha scritto: > Hi All, > > i am currently using camel 3.7.4 and noti

Re: How to override CXF version for Camel-CXF

Sure. Add the cxf dependencies in your pom.xml. Mind you will need to add all dependencies that camel-cxf artifact requires, otherwise you might encounter weird issues. On Tue, May 18, 2021, 12:35 Chio Chuan Ooi wrote: > Hi All, > > i am currently using camel 3.7.4 and notice that camel-cxf is u

How to override CXF version for Camel-CXF

Hi All, i am currently using camel 3.7.4 and notice that camel-cxf is using cxf 3.4.2. For cxf 3.4.2, notice there is a vulnerability in 3.4.2 and already fixed in cxf 3.4.3. when checking on jira CAMEL-16434 , it seems that the cxf 3.4.3 is only

Re: Apacke Karaf, Camel and Kafka component

Hi Nico, Thanks for the update, I’m suspecting the same cause (a refresh due to snappy feature). Regards JB > Le 18 mai 2021 à 09:35, Nicola Cisternino a écrit : > > Hi JB, > > The problem seems to be the snappy feature, not camel-sql. > Any other feature installed after snappy (not only cam

Re: Apacke Karaf, Camel and Kafka component

Hi JB, The problem seems to be the snappy feature, not camel-sql. Any other feature installed after snappy (not only camel-sql...) raise errors mentioned above. In the morning I will create a Jira issue. Thanks. NC On 5/18/21 7:50 AM, Jean-Baptiste Onofre wrote: Hi, That’s a refresh issue