Re: [VOTE] Release Apache Camel Kamelets 3.20.0

[Claudio Miranda]

+1 (non binding)

-- 
  Claudio Miranda

clau...@claudius.com.br
http://www.claudius.com.br

Re: camel-docker operation error

[Mark Webb]

I'd love to help you.  Thanks !!


On Thu, Dec 22, 2022 at 12:40 PM Claus Ibsen  wrote:

> Hi
>
> On Thu, Dec 22, 2022 at 6:37 PM Mark Webb  wrote:
>
> > Thanks Claus.  I started digging through the Java source code.  It
> appears
> > that only "stats" and "events" can be used by the Consumer, see
> > DockerEndpoint.createConsumer(Processor).  That's not clear in the
> > documentation.
> >
> >
> Ah yeah, good point. We can improve this. If you want to contribute, then
> you can send a PR where you update the javadoc setOperation method, where
> you can
> say that events and stats are only for the consumer, and all others for the
> producer.
>
>
>
>
> > On Thu, Dec 22, 2022 at 12:28 PM Claus Ibsen 
> > wrote:
> >
> > > Hi
> > >
> > > When browsing the documentation on the website, then make sure to
> select
> > > the Camel version you use, see bottom left corner.
> > >
> > > It may be that info is a new operation added in a newer version. If you
> > > choose the correct Camel version in the docs, then it should list what
> > > operations are valid.
> > >
> > > On Thu, Dec 22, 2022 at 6:14 PM Mark Webb 
> wrote:
> > >
> > > > I am trying to get a Camel-Docker route working.  The beginning of my
> > > > simple route is (I have a valid IP Address listed in the route):
> > > >
> > > > from("docker://info?host=IP_ADDRESS=2375").to("log:info");
> > > >
> > > > And I get the following error:
> > > >
> > > > *info is not a valid consumer operation*
> > > >
> > > > Are there any other tutorials or documentation I can look at to
> figure
> > > out
> > > > why the "info" operation is not valid?
> > > >
> > > > Thanks,
> > > > Mark
> > > >
> > >
> > >
> > > --
> > > Claus Ibsen
> > > -
> > > @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
> > >
> >
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Re: camel-docker operation error

[Claus Ibsen]

Hi

On Thu, Dec 22, 2022 at 6:37 PM Mark Webb  wrote:

> Thanks Claus.  I started digging through the Java source code.  It appears
> that only "stats" and "events" can be used by the Consumer, see
> DockerEndpoint.createConsumer(Processor).  That's not clear in the
> documentation.
>
>
Ah yeah, good point. We can improve this. If you want to contribute, then
you can send a PR where you update the javadoc setOperation method, where
you can
say that events and stats are only for the consumer, and all others for the
producer.




> On Thu, Dec 22, 2022 at 12:28 PM Claus Ibsen 
> wrote:
>
> > Hi
> >
> > When browsing the documentation on the website, then make sure to select
> > the Camel version you use, see bottom left corner.
> >
> > It may be that info is a new operation added in a newer version. If you
> > choose the correct Camel version in the docs, then it should list what
> > operations are valid.
> >
> > On Thu, Dec 22, 2022 at 6:14 PM Mark Webb  wrote:
> >
> > > I am trying to get a Camel-Docker route working.  The beginning of my
> > > simple route is (I have a valid IP Address listed in the route):
> > >
> > > from("docker://info?host=IP_ADDRESS=2375").to("log:info");
> > >
> > > And I get the following error:
> > >
> > > *info is not a valid consumer operation*
> > >
> > > Are there any other tutorials or documentation I can look at to figure
> > out
> > > why the "info" operation is not valid?
> > >
> > > Thanks,
> > > Mark
> > >
> >
> >
> > --
> > Claus Ibsen
> > -
> > @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
>


-- 
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: camel-docker operation error

[Mark Webb]

Thanks Claus.  I started digging through the Java source code.  It appears
that only "stats" and "events" can be used by the Consumer, see
DockerEndpoint.createConsumer(Processor).  That's not clear in the
documentation.

On Thu, Dec 22, 2022 at 12:28 PM Claus Ibsen  wrote:

> Hi
>
> When browsing the documentation on the website, then make sure to select
> the Camel version you use, see bottom left corner.
>
> It may be that info is a new operation added in a newer version. If you
> choose the correct Camel version in the docs, then it should list what
> operations are valid.
>
> On Thu, Dec 22, 2022 at 6:14 PM Mark Webb  wrote:
>
> > I am trying to get a Camel-Docker route working.  The beginning of my
> > simple route is (I have a valid IP Address listed in the route):
> >
> > from("docker://info?host=IP_ADDRESS=2375").to("log:info");
> >
> > And I get the following error:
> >
> > *info is not a valid consumer operation*
> >
> > Are there any other tutorials or documentation I can look at to figure
> out
> > why the "info" operation is not valid?
> >
> > Thanks,
> > Mark
> >
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Re: camel-docker operation error

[Claus Ibsen]

Hi

When browsing the documentation on the website, then make sure to select
the Camel version you use, see bottom left corner.

It may be that info is a new operation added in a newer version. If you
choose the correct Camel version in the docs, then it should list what
operations are valid.

On Thu, Dec 22, 2022 at 6:14 PM Mark Webb  wrote:

> I am trying to get a Camel-Docker route working.  The beginning of my
> simple route is (I have a valid IP Address listed in the route):
>
> from("docker://info?host=IP_ADDRESS=2375").to("log:info");
>
> And I get the following error:
>
> *info is not a valid consumer operation*
>
> Are there any other tutorials or documentation I can look at to figure out
> why the "info" operation is not valid?
>
> Thanks,
> Mark
>


-- 
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

camel-docker operation error

[Mark Webb]

I am trying to get a Camel-Docker route working.  The beginning of my
simple route is (I have a valid IP Address listed in the route):

from("docker://info?host=IP_ADDRESS=2375").to("log:info");

And I get the following error:

*info is not a valid consumer operation*

Are there any other tutorials or documentation I can look at to figure out
why the "info" operation is not valid?

Thanks,
Mark

Re: Does Camel Quarkus Support JDK 17?

[zineb bendhiba]

Hello,

Sorry, I missed this email.

CI jobs run tests ou both JDK11 and JDK17. So, it is  fine to use JDK 17 with 
Camel Quarkus.

In case you have any issue, please open a GitHub issue here: 
https://github.com/apache/camel-quarkus/issues

Regards, 
Zineb Bendhiba 

> Le 22 déc. 2022 à 16:43, Nick Paul  a écrit :
> 
> Any thoughts on this question?
> 
> Nick
> Paul
> 
>> On Thu, Dec 8, 2022 at 12:29 PM Nick Paul  wrote:
>> 
>> The documentation for  camel-quarkus lists version 11, but looking through
>> the dependencies I'm not sure why 17 is omitted. Does Camel Quarkus Support
>> JDK  17?
>> 
>> https://camel.apache.org/releases/q-2.14.0/
>> 
>> 
>> Nick
>> Paul
>> 
> -- 
> Nick
> Paul

Re: Does Camel Quarkus Support JDK 17?

[Nick Paul]

Any thoughts on this question?

Nick
Paul

On Thu, Dec 8, 2022 at 12:29 PM Nick Paul  wrote:

> The documentation for  camel-quarkus lists version 11, but looking through
> the dependencies I'm not sure why 17 is omitted. Does Camel Quarkus Support
> JDK  17?
>
> https://camel.apache.org/releases/q-2.14.0/
>
>
> Nick
> Paul
>
-- 
Nick
Paul

Re: RouteConfiguration#OnCompletion when error

[Babak Vahdat]

> On 22 Dec 2022, at 14:11, Babak Vahdat  
> wrote:
> 
> Thanks for the confirmation.
> 
> Yeah OnCompletionProcessor#onFailure callback was exactly where I stumbled 
> upon as I was debugging.
> 
> Will then create the JIRA with the corresponding fix.

Raised https://issues.apache.org/jira/browse/CAMEL-18835 


> 
> —
> Babak
> 
>> On 22 Dec 2022, at 13:52, Claus Ibsen  wrote:
>> 
>> Hi
>> 
>> Yes it appears to be a bug.
>> 
>> In the OnCompletionProcessor the code in onComplete should be copied to
>> onFailure. Its the code in the beginning that checks that its only invoked
>> at the correct point.
>> If you copy that code then it looks like it works.
>> 
>> You are welcome to create a JIRA and "fix" this. And would be good to
>> include unit test with the fix.
>> 
>> 
>> On Thu, Dec 22, 2022 at 7:38 AM Babak Vahdat
>>  wrote:
>> 
>>> And using 3.20.0 here...
>>> 
 On 22 Dec 2022, at 07:36, Babak Vahdat 
 
>>> wrote:
 
 Hi
 
 There seems to be a bug in RouteConfiguration#OnCompletion support which
>>> in case of an error, then it would run a given Callback as many times as
>>> the number of the routes that you have. However if no error then it gets
>>> called exactly once which is as expected.
 
 Here a simple reproducible:
>>> https://gist.github.com/bvahdat/db518d4f4abde3ece6c5698f07f8e63d <
>>> https://gist.github.com/bvahdat/db518d4f4abde3ece6c5698f07f8e63d>
 
 Am I right?
 
 —
 Babak
>>> 
>>> 
>> 
>> -- 
>> Claus Ibsen
>> -
>> @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
> 

Re: RouteConfiguration#OnCompletion when error

[Babak Vahdat]

Thanks for the confirmation.

Yeah OnCompletionProcessor#onFailure callback was exactly where I stumbled upon 
as I was debugging.

Will then create the JIRA with the corresponding fix.

—
Babak

> On 22 Dec 2022, at 13:52, Claus Ibsen  wrote:
> 
> Hi
> 
> Yes it appears to be a bug.
> 
> In the OnCompletionProcessor the code in onComplete should be copied to
> onFailure. Its the code in the beginning that checks that its only invoked
> at the correct point.
> If you copy that code then it looks like it works.
> 
> You are welcome to create a JIRA and "fix" this. And would be good to
> include unit test with the fix.
> 
> 
> On Thu, Dec 22, 2022 at 7:38 AM Babak Vahdat
>  wrote:
> 
>> And using 3.20.0 here...
>> 
>>> On 22 Dec 2022, at 07:36, Babak Vahdat 
>> wrote:
>>> 
>>> Hi
>>> 
>>> There seems to be a bug in RouteConfiguration#OnCompletion support which
>> in case of an error, then it would run a given Callback as many times as
>> the number of the routes that you have. However if no error then it gets
>> called exactly once which is as expected.
>>> 
>>> Here a simple reproducible:
>> https://gist.github.com/bvahdat/db518d4f4abde3ece6c5698f07f8e63d <
>> https://gist.github.com/bvahdat/db518d4f4abde3ece6c5698f07f8e63d>
>>> 
>>> Am I right?
>>> 
>>> —
>>> Babak
>> 
>> 
> 
> -- 
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2

Re: RouteConfiguration#OnCompletion when error

[Claus Ibsen]

Hi

Yes it appears to be a bug.

In the OnCompletionProcessor the code in onComplete should be copied to
onFailure. Its the code in the beginning that checks that its only invoked
at the correct point.
If you copy that code then it looks like it works.

You are welcome to create a JIRA and "fix" this. And would be good to
include unit test with the fix.


On Thu, Dec 22, 2022 at 7:38 AM Babak Vahdat
 wrote:

> And using 3.20.0 here...
>
> > On 22 Dec 2022, at 07:36, Babak Vahdat 
> wrote:
> >
> > Hi
> >
> > There seems to be a bug in RouteConfiguration#OnCompletion support which
> in case of an error, then it would run a given Callback as many times as
> the number of the routes that you have. However if no error then it gets
> called exactly once which is as expected.
> >
> > Here a simple reproducible:
> https://gist.github.com/bvahdat/db518d4f4abde3ece6c5698f07f8e63d <
> https://gist.github.com/bvahdat/db518d4f4abde3ece6c5698f07f8e63d>
> >
> > Am I right?
> >
> > —
> > Babak
>
>

-- 
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2