Re: HTTP session handling sample on Context level

2020-01-29 Thread Claus Ibsen
Hi You can just use a singleton bean and share data via the bean between routes. There are also the cache components On Wed, Jan 29, 2020 at 9:25 PM Tom Coudyzer wrote: > > Hi, > > I was able to use a cookieHandler in the URI. However the result remains > the same I still get the 401. I also

Re: HTTP session handling sample on Context level

2020-01-29 Thread Tom Coudyzer
Hi, I was able to use a cookieHandler in the URI. However the result remains the same I still get the 401. I also tried to instantiate the instanceCookieHandler via the JNDIRegistry override but that did not work either and in addition this method is now deprecated. So still searching for some

Re: SEDA consumer and parallelism

2020-01-29 Thread Alex Soto
Thanks Claus, I tested adding synchronous=true to the SEDA consumer, but it does not make any difference. The only thing that worked was to add asyncDelayed=“false” to the delay EIP. Is this perhaps a bug? Best regards, Alex soto > On Jan 29, 2020, at 1:48 PM, Claus Ibsen wrote: > > On

Re: SEDA consumer and parallelism

2020-01-29 Thread Claus Ibsen
On the consumer, eg the from On Wed, Jan 29, 2020 at 5:41 PM Alex Soto wrote: > > Thanks Claus…. > > Oh, I see, after returning from the delay, it is a different thread that > processes the rest of the route. > Where should the synchronous=true be added, in the Producer or Consumer or > both

Re: SEDA consumer and parallelism

2020-01-29 Thread Alex Soto
Thanks Claus…. Oh, I see, after returning from the delay, it is a different thread that processes the rest of the route. Where should the synchronous=true be added, in the Producer or Consumer or both URIs? Best regards, Alex soto > On Jan 29, 2020, at 11:13 AM, Claus Ibsen wrote: >

Re: SEDA consumer and parallelism

2020-01-29 Thread Claus Ibsen
The delay makes it asynchronous, set synchronous=true on the seda endpoint On Wed, Jan 29, 2020 at 4:52 PM Alex Soto wrote: > > Hello, > > I have a question about SEDA consumer and parallelism. When I set the > concurrentConsumers=1 and send multiple messages in parallel, I expect to see >

SEDA consumer and parallelism

2020-01-29 Thread Alex Soto
Hello, I have a question about SEDA consumer and parallelism. When I set the concurrentConsumers=1 and send multiple messages in parallel, I expect to see the messages being processed in sequence, but what I see in the logs is that they are being processed in parallel. My route looks more or

Re: Camel 3.0.1 standalone main cdi fat jar not working

2020-01-29 Thread Dennis Holunder
Hi, thank you for looking into this. Ss shade plugin uses the services from all jars are merged into fat jar. It must be something else. The application itself didn't change, only the camel version Am Mi., 29. Jan. 2020 um 14:52 Uhr schrieb Claus Ibsen-2 [via Camel] : > > Hi > > See this

Re: Camel 3.0.1 standalone main cdi fat jar not working

2020-01-29 Thread Claus Ibsen
Hi See this FAQ https://camel.apache.org/manual/latest/faq/how-do-i-use-a-big-uber-jar.html uber-jar self made are on your own. And it's a hazzle to do. The JARs have files in META-INF/services which you need to ensure all of them gets shaded, and whatelse. On Wed, Jan 29, 2020 at 2:19 PM

Re: java.lang.NoClassDefFoundError: groovy/lang/Script

2020-01-29 Thread Alex Soto
Thank you JB, I created a new ticket: https://issues.apache.org/jira/browse/CAMEL-14457 Best regards, Alex soto > On Jan 29, 2020, at 3:15 AM, Claus Ibsen wrote: > > On Wed, Jan 29, 2020 at 6:57 AM Jean-Baptiste Onofré

Camel 3.0.1 standalone main cdi fat jar not working

2020-01-29 Thread Dennis Holunder
Hello, I've migrated an app to camel 3 which works fine in IDE, but starting fat jar produces the errors like: java.lang.NoClassDefFoundError: com/lmax/disruptor/EventTranslatorVararg. The approach works with camel 2.22 version I'm using latest weld-se-shaded, deltaspike-cdictrl-weld and

Re: java.lang.NoClassDefFoundError: groovy/lang/Script

2020-01-29 Thread Claus Ibsen
On Wed, Jan 29, 2020 at 6:57 AM Jean-Baptiste Onofré wrote: > > Hi Alex, > > It's what I thought, you are welcome ;) > > Not sure if we consider this as an issue in camel-groovy or in usage. > > Can you reopen CAMEL-4171 and assign to me ? I will improve the current > state. No do not reopen old

Re: Property placeholder causes an error

2020-01-29 Thread Gerald Kallas
Thanks Claus. I tried the Property Placeholder as described here https://camel.apache.org/manual/latest/using-propertyplaceholder.html It works. Sent by my mobile device - Gerald Kallas > Claus Ibsen hat am 28. Januar 2020 22:45 geschrieben: > > > Hi > > You should NOT use spring stuff