Help with Splitter/Aggregator-like behavior

So, I have a situation where I need something like a Splitter and an Aggregator. But as far as I can tell from reading and googling, maybe my situation is nonstandard? >From what I can tell, a Splitter and Aggregator are used together within a >single route. In my case, I need the Splitter and A

Re: OSGI component not in Camel registry

Gotcha that explains it! Thank you both Claus and Francois On Wed, Sep 19, 2018 at 7:30 AM, Claus Ibsen wrote: > On Wed, Sep 19, 2018 at 1:24 PM Francois Papon > wrote: > > > > Hi, > > > > The annotations @Component is for Declarative Service. > > > > As Claus say, Camel support OSGi Blueprint

Re: camel-mail validation process

Unfortunately, it does not work Il giorno mar 18 set 2018 alle ore 16:41 Claus Ibsen ha scritto: > Hi > > You can try to turn of peek with peek=false > On Mon, Sep 17, 2018 at 4:12 PM Marco Pampaloni > wrote: > > > > Hi everyone, I've been trying to write down a camel route that listens > to a

Re: seda default queue size

Hi I have fixed the docs On Wed, Sep 19, 2018 at 12:50 PM Claus Ibsen wrote: > > Hi > > Its this ticket about the 1000 as new default size > https://issues.apache.org/jira/browse/CAMEL-12542 > On Wed, Sep 19, 2018 at 12:48 PM Claus Ibsen wrote: > > > > Hi > > > > In the beginning there was only

Re: OSGI component not in Camel registry

On Wed, Sep 19, 2018 at 1:24 PM Francois Papon wrote: > > Hi, > > The annotations @Component is for Declarative Service. > > As Claus say, Camel support OSGi Blueprint so you have to declare your > component and your Camel context in a blueprint.xml > Ah yes that is correct. For DS then there is

***UNCHECKED*** Re: OSGI component not in Camel registry

Hi, The annotations @Component is for Declarative Service. As Claus say, Camel support OSGi Blueprint so you have to declare your component and your Camel context in a blueprint.xml Regards, François Papon fpa...@apache.org Le 19/09/2018 à 14:42, Claus Ibsen a écrit : > Hi > > How are you runn

Re: file endpoint to xquery problem

Hi Have you tried setting that as a header value - I think there is something with xquery where you can refer to headers by their name. On Tue, Sep 18, 2018 at 4:52 PM Wang Yan wrote: > > In my camel route has below route , which send file input to xquery to > generate file output. as below sho

Re: seda default queue size

Hi Its this ticket about the 1000 as new default size https://issues.apache.org/jira/browse/CAMEL-12542 On Wed, Sep 19, 2018 at 12:48 PM Claus Ibsen wrote: > > Hi > > In the beginning there was only one size you had to set per endpoint. > So later we added a default size on the component so you c

Re: seda default queue size

Hi In the beginning there was only one size you had to set per endpoint. So later we added a default size on the component so you can set it once. Then alter that default was reduced from infinitie to 1000. So today its 1000 and there is a glitch in the docs. On Tue, Sep 11, 2018 at 11:30 AM Denni

Re: OSGI component not in Camel registry

Hi How are you running this in OSGi - eg are you using camel-blueprint or something? For OSGi we generally only support OSGi blueprint and therefore you should setup your beans in the xml file as . For any kind of @Component scanning in OSGi then I dont think its something we tend to use so much