request-reply acknowledgment

Hello, I have a set of processor and queue in this design: q1 -> p1 -> q2 -> p2 -> ... -> qn -> pn My queues are in InOut exchange pattern. I would like to know if it is possible to get the ack for a queue after each processor consumption, instead of having that after the last consumer (pn)? Th

Re: No Groovy support after upgrade to 3.0.0-M4

It worked like a charm, thanks. Regards. On 2019/07/18 12:48:55, Andrea Cosentino wrote: > Let su know how it goes please. Feedback are welcome > > Il gio 18 lug 2019, 14:41 Claus Ibsen ha scritto: > > > Hi > > > > Just use camel-groovy and the groovy language, that can be used as > > script

RE: Cannot auto create component: vm

Hi. Ok Thanks, The error seems goes way now. I am still running Spring 4.3.20, Camel 2.21.5, Tomcat 9.0.12 and open JDK 11.0.3 Previously in the Spring XM looks like this and it works and runs in production on camel 2.8 http://camel.apache.org/schema/spring";>

Re: No Groovy support after upgrade to 3.0.0-M4

Let su know how it goes please. Feedback are welcome Il gio 18 lug 2019, 14:41 Claus Ibsen ha scritto: > Hi > > Just use camel-groovy and the groovy language, that can be used as > scripting with groovy > > On Thu, Jul 18, 2019 at 2:36 PM Francesco Chicchiriccò > wrote: > > > > Hi all, > > afte

Re: Cannot auto create component: vm

Hi Try with a newer Camel version On Thu, Jul 18, 2019 at 11:55 AM Steve Pan wrote: > > Thanks Camel. > > I am now trying to migrate the project to Spring 4.3.20 and Camel 2.21.5 > Still running on Tomcat 9.0.12 and open JDK 11.0.3 > > I am still having problem with the vm component, but this ti

Re: No Groovy support after upgrade to 3.0.0-M4

Hi Just use camel-groovy and the groovy language, that can be used as scripting with groovy On Thu, Jul 18, 2019 at 2:36 PM Francesco Chicchiriccò wrote: > > Hi all, > after upgrade to 3.0.0-M4 from 3.0.0-M2 I see there is no more camel-script > artifact; I have found > > https://github.com/apa

No Groovy support after upgrade to 3.0.0-M4

Hi all, after upgrade to 3.0.0-M4 from 3.0.0-M2 I see there is no more camel-script artifact; I have found https://github.com/apache/camel/blob/master/MIGRATION.md#javaxscript explaining the removal. We used to depend on camel-script to support Groovy, not JS, as scripting language: how can I

RE: Cannot auto create component: vm

Thanks Camel. I am now trying to migrate the project to Spring 4.3.20 and Camel 2.21.5 Still running on Tomcat 9.0.12 and open JDK 11.0.3 I am still having problem with the vm component, but this time I get another error. In my Spring XML I have two camel proxy: and I get

RE: Cannot auto create component: vm

Thanks Camel, I will try that. Best regards Steve Pan -Original Message- From: Claus Ibsen Sent: Wednesday, 17 July 2019 16:45 To: users@camel.apache.org Subject: Re: Cannot auto create component: vm Hi Java 11 is not supported with this older version of Camel. Try with a newer versi

http://camel.465427.n5.nabble.com/exchange-getIn-setBody-does-not-work-for-OnException-block-tc5838544.html

@ Claus Thanks for your quick reply. i used exchange.getMessage(), it does not work it prints out below information , what i expected result should be "Error happened , please contact Admin" ### This page contains the following errors: error on line 1 at column 1: Docum