Camel 3.x Message Filter by JSONPath expression?

Dear community, is it possible to filter a message by JSONPath als the following snippet? $.names Many thanks in advance - Gerald

[ANNOUNCEMENT] Apache Camel 3.2.0 with Spring Boot and Karaf Sub-Projects Released

The Camel community announces the immediate availability of Camel, Camel Spring Boot and Camel Karaf 3.2.0, a new minor release with over 160 new features, improvements and fixes. Please read our Camel 3.x upgrade guide [1] that describes how to upgrade Camel 3.1 applications to Camel 3.2. The ar

Re: Camel 3.x Message Filter by JSONPath expression?

Found it .. ... $.surnames > Gerald Kallas hat am 6. Ap

Broken feature dependencies in 3.2.0

Hi! Tried to update to 3.2.0 on karaf-4.2.8, got following error:     Caused by: java.io.IOException: Error resolving artifact org.apache.camel:camel-commands-core:jar:3.2.0: [Could not find artifact org.apache.camel:camel-commands-core:jar:3.2.0 in central (https://repo1.maven.org/mave

Re: Broken feature dependencies in 3.2.0

Hi, It moved to camel-karaf repo and the feature should be updated. Can you please create a Jira ? I will fix that. Sorry for the inconvenience. Regards JB > Le 6 avr. 2020 à 14:42, Константин Чернов a écrit : > > Hi! > > > > Tried to update to 3.2.0 on karaf-4.2.8, got following error: >

Re: Broken feature dependencies in 3.2.0

No, it's a known bug. We released it You just need to update the feature mvn:org.apache.camel/camel-commands-core/3.2.0 to mvn:org.apache.camel.karaf/camel-commands-core/3.2.0 It's already fixed for the next release. Il giorno lun 6 apr 2020 alle ore 14:42 Константин Чернов < k.j.cher...@gmail

Re: Broken feature dependencies in 3.2.0

Ah, okay. I confirm it works with added to etc/org.apache.karaf.features.xml (just in case someone may find this workaround useful). So no JIRA issue needed? Best regards, Konstantin Chernov. 06.04.2020, 19:46 пользователь "Andrea Cosentino" написал: No, it's a known

Re: Broken feature dependencies in 3.2.0

Thanks for spotting this by the way! Il giorno lun 6 apr 2020 alle ore 14:50 Andrea Cosentino ha scritto: > No, I fixed that days ago. > > Il giorno lun 6 apr 2020 alle ore 14:49 Константин Чернов < > k.j.cher...@gmail.com> ha scritto: > >> Ah, okay. >> >> I confirm it works with >> >>

Re: Broken feature dependencies in 3.2.0

No, I fixed that days ago. Il giorno lun 6 apr 2020 alle ore 14:49 Константин Чернов < k.j.cher...@gmail.com> ha scritto: > Ah, okay. > > I confirm it works with > > originalUri="mvn:org.apache.camel/camel-commands-core/3.2.0" > replacement="mvn:org.apache.camel.karaf/camel-commands

Re: Broken feature dependencies in 3.2.0

Ah yes, I just saw that. It’s already fixed but not released yet. Regards JB > Le 6 avr. 2020 à 14:50, Andrea Cosentino a écrit : > > No, I fixed that days ago. > > Il giorno lun 6 apr 2020 alle ore 14:49 Константин Чернов < > k.j.cher...@gmail.com> ha scritto: > >> Ah, okay. >> >> I confirm

Re: Broken feature dependencies in 3.2.0

Don’t we have to update the provided feature in camel-karat ? It would be easier for users. Regards JB > Le 6 avr. 2020 à 14:46, Andrea Cosentino a écrit : > > No, it's a known bug. > > We released it > > You just need to update the feature > > mvn:org.apache.camel/camel-commands-core/3.2.0

logging inside global onException block with multiple logger names

Hi Team, We have setup separate log4j logger names for each route inside camel context. We have common exception block and we have set the logger name in exchange property . Is there a way to set the logger name from property or header without calling a bean method in below case. Not workin