[VOTE] Release Apache Camel Kamelets 4.6.0

[Andrea Cosentino]

Hello all,

This is a vote for releasing camel-kamelets 4.6.0

This is a release supporting Camel 4.6.0

Kamelets release files:
https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.6.0
Kamelets staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1712
Kamelets Tag:
https://github.com/apache/camel-kamelets/releases/tag/v4.6.0

Please cast your vote.

[ ] +1 Release camel-kamelets 4.6.0
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Here's my +1.

Thanks,
Andrea Cosentino

[RESULT] [VOTE] Release Apache Camel Kamelets 4.4.2

[Andrea Cosentino]

Hello all,

The vote passes with the following result

4 +1 binding votes: Andrea Cosentino, Claus Ibsen, Jean-Baptiste Onofrè and
Zineb Bendhiba

2 +1 non-binding votes: Claudio Miranda, Miguel de Barros and Gaelle
Fournier

Thanks to all the voters,

I'll go ahead with the process.

Have a good week.

[VOTE] Release Apache Camel Kamelets 4.4.2

[Andrea Cosentino]

Hello all,

This is a vote for releasing camel-kamelets 4.4.2

This is a release supporting Camel 4.4.2 and it's an LTS release.

Kamelets release files:
https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.4.2
Kamelets staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1707
Kamelets Tag:
https://github.com/apache/camel-kamelets/releases/tag/v4.4.2

Please cast your vote.

[ ] +1 Release camel-kamelets 4.4.2
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Here's my +1.

Thanks,
Andrea Cosentino

[RESULT] [VOTE] Release Apache Camel Kamelets 4.5.0

[Andrea Cosentino]

Hello all,

The vote passes with the following result

4 +1 binding votes: Andrea Cosentino, Claus Ibsen, Pasquale Congiusti and
Marat Gubaidullin

2 +1 non-binding votes: Claudio Miranda and Gaelle Fournier

Thanks to all the voters,

I'll go ahead with the process.

Have a good week.

[VOTE] Release Apache Camel Kamelets 4.5.0

[Andrea Cosentino]

Hello all,

This is a vote for releasing camel-kamelets 4.5.0

This is a release supporting Camel 4.5.0 and it's a development release.

Kamelets release files:
https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.5.0
Kamelets staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1692
Kamelets Tag:
https://github.com/apache/camel-kamelets/releases/tag/v4.5.0

Please cast your vote.

[ ] +1 Release camel-kamelets 4.5.0
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Here's my +1.

Thanks,
Andrea Cosentino

[RESULT] [VOTE] Release Apache Camel Kamelets 4.4.1

[Andrea Cosentino]

Hello all,

The vote passes with the following result:

7 +1 binding votes: Andrea Cosentino, Claus Ibsen, Babak Vahdat,
Jean-Baptiste Onofrè, Zineb Bendhiba, Pasquale Congiusti and Otavio Rodolfo
Piske

2 +1 non-binding votes: Claudio Miranda and Gaelle Fournier

Thanks to all the voters.

I'll go ahead with the process.

Re: [VOTE] Release Apache Camel Kamelets 4.4.1

[Andrea Cosentino]

Thanks all,

The vote passes. I'll go ahead.

Il giorno lun 25 mar 2024 alle ore 17:30 Otavio Rodolfo Piske <
angusyo...@gmail.com> ha scritto:

> +1 (binding)
>
> Thanks!
>
> On Mon, Mar 25, 2024 at 12:22 PM Pasquale Congiusti <
> pasquale.congiu...@gmail.com> wrote:
>
> > +1 (binding)
> >
> > Thanks!
> >
> > Pasquale.
> >
> > On Fri, Mar 22, 2024 at 7:05 AM Andrea Cosentino 
> > wrote:
> >
> > > Hello all,
> > >
> > > This is a vote for releasing camel-kamelets 4.4.1
> > >
> > > This is the second release of camel-kamelets supporting LTS Camel 4.4.x
> > and
> > > it contains alignment to 4.4.1 and some fixes.
> > >
> > > Kamelets release files:
> > > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.4.1
> > > Kamelets staging repository:
> > > https://repository.apache.org/content/repositories/orgapachecamel-1687
> > > Kamelets Tag:
> > > https://github.com/apache/camel-kamelets/releases/tag/v4.4.1
> > >
> > > Please cast your vote.
> > >
> > > [ ] +1 Release camel-kamelets 4.4.1
> > > [ ] -1 Veto the release (provide specific comments)
> > >
> > > The vote is open for at least 72 hours.
> > >
> > > Here's my +1.
> > >
> > > Thanks,
> > > Andrea Cosentino
> > >
> >
>
>
> --
> Otavio R. Piske
> http://orpiske.net
>

[VOTE] Release Apache Camel Kamelets 4.4.1

[Andrea Cosentino]

Hello all,

This is a vote for releasing camel-kamelets 4.4.1

This is the second release of camel-kamelets supporting LTS Camel 4.4.x and
it contains alignment to 4.4.1 and some fixes.

Kamelets release files:
https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.4.1
Kamelets staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1687
Kamelets Tag:
https://github.com/apache/camel-kamelets/releases/tag/v4.4.1

Please cast your vote.

[ ] +1 Release camel-kamelets 4.4.1
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Here's my +1.

Thanks,
Andrea Cosentino

Re: Camel AWS-S3 prefixes do not accept wildcards

[Andrea Cosentino]

There is no method for sync from CLI in SDK.

I'll add a note in the prefix description about wildcards and regexes
missing support from SDK.

Thanks for the suggestion!

Il giorno mer 13 mar 2024 alle ore 21:13 Andrea Cosentino 
ha scritto:

> I'll investigate if there is a way of using sync somewhat through the sdk.
> I'll keep you posted
>
> Il mer 13 mar 2024, 20:47 Mitch Trachtenberg  ha
> scritto:
>
>> My mistake.  What I'd thought was just aws cli ls was actually output
>> piped
>> through a grep.
>>
>> Again, though, for many people used to non-AWS file listings this may come
>> as a surprise, so it would IMO be helpful to tell people up front that
>> wildcards, regexes, etc... won't work.  And thanks for letting me know
>> that
>> the asterisk is a legal character in an AWS S3 object name.
>>
>> My situation is I expect only objects whose names match a particular
>> pattern, but I want to prevent the download of any surprise objects that
>> might get deposited.  It looks like list, eliminate, and download the ones
>> you want is going to have to be the approach to accomplish that.
>>
>> On Wed, Mar 13, 2024 at 12:13 PM Andrea Cosentino 
>> wrote:
>>
>> > Hi,
>> > In the CLI it was escalated but it doesn't seem to be supported:
>> > https://github.com/aws/aws-cli/issues/3784
>> >
>> > Usually the CLI/SDK/Rest are aligned, so if it was possible natively
>> > through CLI it would have been possible through SDK.
>> >
>> > The prefix is only a String in v1 and v2 and most importantly * is valid
>> > character in the key name for an S3 object.
>> >
>> > My suggestion is to list the objects by prefix and then check through
>> > regular expression if the key name responds to your regex or not.
>> >
>> > As far as I know and see in the documentation, list objects through
>> > wildcards is not supported with AWS S3 ls, it works with AWS S3 sync but
>> > sync is a different command than list objects and I guess is a different
>> > Java library too.
>> >
>> > Cheers
>> >
>> > Il giorno mer 13 mar 2024 alle ore 19:37 Mitch Trachtenberg <
>> > mjt...@gmail.com> ha scritto:
>> >
>> > > Thanks, Claus.  I'm sure you're correct and I've looked at the
>> > > documentation for ListObjectsRequest.
>> > >
>> > >
>> >
>> https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/model/ListObjectsRequest.html
>> > >
>> > > But it seems like something that is such a common need that it would
>> be
>> > > helpful IMO to include a note to that effect in the docs.
>> > >
>> > > On Wed, Mar 13, 2024 at 11:30 AM Claus Ibsen 
>> > > wrote:
>> > >
>> > > > Hi
>> > > >
>> > > > Camel uses the AWS Java SDK and it set the prefix on this SDK so its
>> > > > depends on if this SDK has any kind of support for wildcards.
>> > > > As you write its likely it does not have that.
>> > > >
>> > > > You can try to dive into the AWS SDK and see more deeper.
>> > > >
>> > > > On Wed, Mar 13, 2024 at 7:19 PM Mitch Trachtenberg <
>> mjt...@gmail.com>
>> > > > wrote:
>> > > >
>> > > > > I cannot specifically find this stated in either AWS S3 or Camel
>> > > > > documentation, but it appears that I can give a prefix 1234- to
>> > > restrict
>> > > > > Camel's (4.3.0) downloads to files starting 1234-, but cannot
>> give a
>> > > > prefix
>> > > > > - to restrict Camel's downloads to files beginning with four
>> > > > characters
>> > > > > and a hyphen.
>> > > > >
>> > > > > I believe AWS CLI does provide a way to do this.  If I'm correct,
>> it
>> > > > would
>> > > > > be helpful if this could be added to the documentation.
>> > > > >
>> > > > > If someone were to want to instruct me in where/how to do that,
>> I'd
>> > be
>> > > > > happy to generate a pull request, but it might be easier to just
>> add:
>> > > > > "Note: due to AWS S3 limitations, the prefix parameter does not
>> work
>> > > with
>> > > > > wildcards."
>> > > > >
>> > > > > It would be even more helpful, of course, if the component were
>> > > modified
>> > > > in
>> > > > > some way to allow for wildcards.
>> > > > >
>> > > >
>> > > >
>> > > > --
>> > > > Claus Ibsen
>> > > > -
>> > > > @davsclaus
>> > > > Camel in Action 2: https://www.manning.com/ibsen2
>> > > >
>> > >
>> >
>>
>

Re: Camel AWS-S3 prefixes do not accept wildcards

[Andrea Cosentino]

I'll investigate if there is a way of using sync somewhat through the sdk.
I'll keep you posted

Il mer 13 mar 2024, 20:47 Mitch Trachtenberg  ha scritto:

> My mistake.  What I'd thought was just aws cli ls was actually output piped
> through a grep.
>
> Again, though, for many people used to non-AWS file listings this may come
> as a surprise, so it would IMO be helpful to tell people up front that
> wildcards, regexes, etc... won't work.  And thanks for letting me know that
> the asterisk is a legal character in an AWS S3 object name.
>
> My situation is I expect only objects whose names match a particular
> pattern, but I want to prevent the download of any surprise objects that
> might get deposited.  It looks like list, eliminate, and download the ones
> you want is going to have to be the approach to accomplish that.
>
> On Wed, Mar 13, 2024 at 12:13 PM Andrea Cosentino 
> wrote:
>
> > Hi,
> > In the CLI it was escalated but it doesn't seem to be supported:
> > https://github.com/aws/aws-cli/issues/3784
> >
> > Usually the CLI/SDK/Rest are aligned, so if it was possible natively
> > through CLI it would have been possible through SDK.
> >
> > The prefix is only a String in v1 and v2 and most importantly * is valid
> > character in the key name for an S3 object.
> >
> > My suggestion is to list the objects by prefix and then check through
> > regular expression if the key name responds to your regex or not.
> >
> > As far as I know and see in the documentation, list objects through
> > wildcards is not supported with AWS S3 ls, it works with AWS S3 sync but
> > sync is a different command than list objects and I guess is a different
> > Java library too.
> >
> > Cheers
> >
> > Il giorno mer 13 mar 2024 alle ore 19:37 Mitch Trachtenberg <
> > mjt...@gmail.com> ha scritto:
> >
> > > Thanks, Claus.  I'm sure you're correct and I've looked at the
> > > documentation for ListObjectsRequest.
> > >
> > >
> >
> https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/model/ListObjectsRequest.html
> > >
> > > But it seems like something that is such a common need that it would be
> > > helpful IMO to include a note to that effect in the docs.
> > >
> > > On Wed, Mar 13, 2024 at 11:30 AM Claus Ibsen 
> > > wrote:
> > >
> > > > Hi
> > > >
> > > > Camel uses the AWS Java SDK and it set the prefix on this SDK so its
> > > > depends on if this SDK has any kind of support for wildcards.
> > > > As you write its likely it does not have that.
> > > >
> > > > You can try to dive into the AWS SDK and see more deeper.
> > > >
> > > > On Wed, Mar 13, 2024 at 7:19 PM Mitch Trachtenberg  >
> > > > wrote:
> > > >
> > > > > I cannot specifically find this stated in either AWS S3 or Camel
> > > > > documentation, but it appears that I can give a prefix 1234- to
> > > restrict
> > > > > Camel's (4.3.0) downloads to files starting 1234-, but cannot give
> a
> > > > prefix
> > > > > - to restrict Camel's downloads to files beginning with four
> > > > characters
> > > > > and a hyphen.
> > > > >
> > > > > I believe AWS CLI does provide a way to do this.  If I'm correct,
> it
> > > > would
> > > > > be helpful if this could be added to the documentation.
> > > > >
> > > > > If someone were to want to instruct me in where/how to do that, I'd
> > be
> > > > > happy to generate a pull request, but it might be easier to just
> add:
> > > > > "Note: due to AWS S3 limitations, the prefix parameter does not
> work
> > > with
> > > > > wildcards."
> > > > >
> > > > > It would be even more helpful, of course, if the component were
> > > modified
> > > > in
> > > > > some way to allow for wildcards.
> > > > >
> > > >
> > > >
> > > > --
> > > > Claus Ibsen
> > > > -
> > > > @davsclaus
> > > > Camel in Action 2: https://www.manning.com/ibsen2
> > > >
> > >
> >
>

Re: Camel AWS-S3 prefixes do not accept wildcards

[Andrea Cosentino]

Hi,
In the CLI it was escalated but it doesn't seem to be supported:
https://github.com/aws/aws-cli/issues/3784

Usually the CLI/SDK/Rest are aligned, so if it was possible natively
through CLI it would have been possible through SDK.

The prefix is only a String in v1 and v2 and most importantly * is valid
character in the key name for an S3 object.

My suggestion is to list the objects by prefix and then check through
regular expression if the key name responds to your regex or not.

As far as I know and see in the documentation, list objects through
wildcards is not supported with AWS S3 ls, it works with AWS S3 sync but
sync is a different command than list objects and I guess is a different
Java library too.

Cheers

Il giorno mer 13 mar 2024 alle ore 19:37 Mitch Trachtenberg <
mjt...@gmail.com> ha scritto:

> Thanks, Claus.  I'm sure you're correct and I've looked at the
> documentation for ListObjectsRequest.
>
> https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/model/ListObjectsRequest.html
>
> But it seems like something that is such a common need that it would be
> helpful IMO to include a note to that effect in the docs.
>
> On Wed, Mar 13, 2024 at 11:30 AM Claus Ibsen 
> wrote:
>
> > Hi
> >
> > Camel uses the AWS Java SDK and it set the prefix on this SDK so its
> > depends on if this SDK has any kind of support for wildcards.
> > As you write its likely it does not have that.
> >
> > You can try to dive into the AWS SDK and see more deeper.
> >
> > On Wed, Mar 13, 2024 at 7:19 PM Mitch Trachtenberg 
> > wrote:
> >
> > > I cannot specifically find this stated in either AWS S3 or Camel
> > > documentation, but it appears that I can give a prefix 1234- to
> restrict
> > > Camel's (4.3.0) downloads to files starting 1234-, but cannot give a
> > prefix
> > > - to restrict Camel's downloads to files beginning with four
> > characters
> > > and a hyphen.
> > >
> > > I believe AWS CLI does provide a way to do this.  If I'm correct, it
> > would
> > > be helpful if this could be added to the documentation.
> > >
> > > If someone were to want to instruct me in where/how to do that, I'd be
> > > happy to generate a pull request, but it might be easier to just add:
> > > "Note: due to AWS S3 limitations, the prefix parameter does not work
> with
> > > wildcards."
> > >
> > > It would be even more helpful, of course, if the component were
> modified
> > in
> > > some way to allow for wildcards.
> > >
> >
> >
> > --
> > Claus Ibsen
> > -
> > @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
>

Re: using Camel with CloudKarafka

[Andrea Cosentino]

Hi,

Have a look at how we implement the Kafka SCRAM source Kamelet.

https://github.com/apache/camel-kamelets/blob/main/kamelets/kafka-scram-source.kamelet.yaml

As far as I see, you need to set also saslMechanism and securityProtocol

Cheers.

Il giorno ven 1 mar 2024 alle ore 02:20 Chirag 
ha scritto:

> Hi,
>
> I am working on a Proof of concept with CloudKarafka (Kafka hosting
> provider) and camel.
>
> I am using camel-jbang 4.4.0
>
> Route to write to Kafka@CloudKarafka works fine.
> But trying to read from Kafka seems to run into challenge.
>
> here is my route:
> - route:
> id: route-09c3
> nodePrefixId: route-229
> from:
>   id: from-f775
>   uri: kafka
>   parameters:
> topic: 4422e1r5-default
> brokers: moped.srvs.cloudkafka.com:9094
> saslJaasConfig: >-
>   org.apache.kafka.common.security.scram.ScramLoginModule
>   required username='user'
>   password='password' securityProtocol: SASL_SSL
>   steps:
> - log:
> id: log-1987
> message: ${body}
>
> Here are logs:
>  he.kafka.common.utils.AppInfoParser : Kafka version: 3.6.1
>  he.kafka.common.utils.AppInfoParser : Kafka commitId: 5e3c2b738d253ff5
>  he.kafka.common.utils.AppInfoParser : Kafka startTimeMs: 1709255355232
>  ort.classic.AssignmentAdapterHelper : Using NO-OP resume strategy
>  l.component.kafka.KafkaFetchRecords : Subscribing 4422e1r5-default-Thread
> 0 to topic 4422e1r5-default
>  afka.clients.consumer.KafkaConsumer : [Consumer
> clientId=consumer-12da9c71-2e7d-4726-935f-cf60c349fee3-1,
> groupId=12da9c71-2e7d-4726-935f-cf60c349fee3] Subscribed to topic(s):
> 4422e1r5-default
>  .apache.kafka.clients.NetworkClient : [Consumer
> clientId=consumer-12da9c71-2e7d-4726-935f-cf60c349fee3-1,
> groupId=12da9c71-2e7d-4726-935f-cf60c349fee3] Node -1 disconnected.
>  .apache.kafka.clients.NetworkClient : [Consumer
> clientId=consumer-12da9c71-2e7d-4726-935f-cf60c349fee3-1,
> groupId=12da9c71-2e7d-4726-935f-cf60c349fee3] Cancelled in-flight
> API_VERSIONS request with correlation id 1 due to node -1 being
> disconnected (elapsed time since creation: 401ms, elapsed time since send:
> 401ms, request timeout: 3ms)
>  .apache.kafka.clients.NetworkClient : [Consumer
> clientId=consumer-12da9c71-2e7d-4726-935f-cf60c349fee3-1,
> groupId=12da9c71-2e7d-4726-935f-cf60c349fee3] Bootstrap broker
> moped.srvs.cloudkafka.com:9094 (id: -1 rack: null) disconnected
>  .apache.kafka.clients.NetworkClient : [Consumer
> clientId=consumer-12da9c71-2e7d-4726-935f-cf60c349fee3-1,
> groupId=12da9c71-2e7d-4726-935f-cf60c349fee3] Node -1 disconnected.
>  .apache.kafka.clients.NetworkClient : [Consumer
> clientId=consumer-12da9c71-2e7d-4726-935f-cf60c349fee3-1,
> groupId=12da9c71-2e7d-4726-935f-cf60c349fee3] Cancelled in-flight
> API_VERSIONS request with correlation id 2 due to node -1 being
> disconnected (elapsed time since creation: 216ms, elapsed time since send:
> 216ms, request timeout: 3ms)
>  .apache.kafka.clients.NetworkClient : [Consumer
> clientId=consumer-12da9c71-2e7d-4726-935f-cf60c349fee3-1,
> groupId=12da9c71-2e7d-4726-935f-cf60c349fee3] Bootstrap broker
> moped.srvs.cloudkafka.com:9094 (id: -1 rack: null) disconnected
>  .apache.kafka.clients.NetworkClient : [Consumer
> clientId=consumer-12da9c71-2e7d-4726-935f-cf60c349fee3-1,
> groupId=12da9c71-2e7d-4726-935f-cf60c349fee3] Node -1 disconnected.
>  .apache.kafka.clients.NetworkClient : [Consumer
> clientId=consumer-12da9c71-2e7d-4726-935f-cf60c349fee3-1,
> groupId=12da9c71-2e7d-4726-935f-cf60c349fee3] Cancelled in-flight
> API_VERSIONS request with correlation id 3 due to node -1 being
> disconnected (elapsed time since creation: 313ms, elapsed time since send:
> 313ms, request timeout: 3ms)
>
> Does this require any other type of param to read successfully?
>
> ચિરાગ/चिराग/Chirag
> --
> Sent from My Gmail Account
>

[RESULT] [VOTE] Release Apache Camel Kamelets 4.4.0

[Andrea Cosentino]

Hello all,

The vote passes with the following results:

4 +1 binding votes: Andrea Cosentino, Claus Ibsen, Nicolas Filotto and
Babak Vahdat

1 +1 non-binding vote: Claudio Miranda

Thanks to all the voters,

I'll go ahead with the release.

Re: How to set custom header(s) on message sent to Azure Service Bus

[Andrea Cosentino]

To clarify:
there is no plan to backport bug fix or new features to Java 8 based Camel 
releases.
--Andrea Cosentino --Apache Camel PMC 
ChairApache Karaf CommitterApache Servicemix PMC MemberEmail: 
ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd 

On Wednesday, February 21, 2024 at 11:43:31 AM GMT+1, Andrea Cosentino 
 wrote:  
 
 It turns out that the correlationId was supported only as consumer header.
I created CAMEL-20444 and opened this PR 
https://github.com/apache/camel/pull/13237
For the backport, I see you're using 3.14.10, but 3.14.x won't take any new 
release, at least this could be backported to 3.21.x or 3.22.x, but those 
releases are JDK 11.
There is now plan to backport any feature or bug fix to Java 8 Camel releases 
now.
--Andrea Cosentino --Apache Camel PMC 
ChairApache Karaf CommitterApache Servicemix PMC MemberEmail: 
ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd 

On Tuesday, February 20, 2024 at 08:08:45 PM GMT+1, Shultz, Dmitry 
 wrote:  
 
 When I test it using Quarkus (camel-azure-servicebus 4.3.0) I can see the 
CamelAzureServiceBusApplicationProperties map is preserved (I see the values on 
the receive side), but CamelAzureServiceBusCorrelationId is still null (setting 
CamelAzureServiceBusApplicationProperties and CamelAzureServiceBusCorrelationId 
at the same time).

In case there would be a fix for the CamelAzureServiceBusCorrelationId, how 
likely that is would be ported to the Java 8 Camel?

From: Andrea Cosentino 
Sent: Tuesday, February 20, 2024 9:45 AM
To: Shultz, Dmitry 
Cc: users@camel.apache.org
Subject: Re: How to set custom header(s) on message sent to Azure Service Bus

I can try to have a look, but probably with Camel 4. x. Can you double check if 
with 4. 0. 4 or 4. 4. 0 is still the case? Il giorno mar 20 feb 2024 alle ore 
18: 11 Shultz, Dmitry  ha scritto: Yes, I followed 
this
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
ZjQcmQRYFpfptBannerEnd
I can try to have a look, but probably with Camel 4.x.

Can you double check if with 4.0.4 or 4.4.0 is still the case?

Il giorno mar 20 feb 2024 alle ore 18:11 Shultz, Dmitry 
mailto:dmitry_shu...@kaltire.com>> ha scritto:
Yes, I followed this code https://stackoverflow.com/a/73886983 
[stackoverflow.com]<https://urldefense.com/v3/__https:/stackoverflow.com/a/73886983__;!!LdWlNaMnLCM!aNdA0OgZVoMVEnVszt4Sxyy4wlFxCMa2Gr__jp3ek9WQQ-do3lvIcVoQL6l3rbq7tGkXhn6GRNsuz2j2_wwp$>
 and nothing ended up being set.
Also, as I said setting the ServiceBusConstants.CORRELATION_ID has no effect 
when checked at the destination.


From: Andrea Cosentino mailto:anco...@gmail.com>>
Sent: Tuesday, February 20, 2024 3:17 AM
To: Shultz, Dmitry mailto:dmitry_shu...@kaltire.com>>
Cc: users@camel.apache.org<mailto:users@camel.apache.org>
Subject: Re: How to set custom header(s) on message sent to Azure Service Bus

I find some time this morning and sorry for the long delay. Did you had a look 
at the ServiceBusConstants. APPLICATION_PROPERTIES? They are meant for this 
purpose. Il giorno ven 9 feb 2024 alle ore 21: 20 Shultz, Dmitry 

ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
ZjQcmQRYFpfptBannerEnd
I find some time this morning and sorry for the long delay.

Did you had a look at the ServiceBusConstants.APPLICATION_PROPERTIES?

They are meant for this purpose.

Il giorno ven 9 feb 2024 alle ore 21:20 Shultz, Dmitry 
mailto:dmitry_shu...@kaltire.com>> ha scritto:
Next week would be awesome! Thanks Andrea.

From: Andrea Cosentino mailto:anco...@gmail.com>>
Sent: Friday, February 9, 2024 11:06 AM
To: Shultz, Dmitry mailto:dmitry_shu...@kaltire.com>>
Cc: users@camel.apache.org<mailto:users@camel.apache.org>
Subject: Re: How to set custom header(s) on message sent to Azure Service Bus

Sorry, i still have to look at this. I hope to find some time next week. Il ven 
9 feb 2024, 19: 47 Shultz, Dmitry  ha scritto: Hi 
Andrea, Thanks for getting back to me! JFYI, I’m trying to set the 
ServiceBusConstants. CORRELATION_ID
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
ZjQcmQRYFpfptBannerEnd
Sorry, i still have to look at this.

I hope to find some time next week.

Il ven 9 feb 2024, 19:47 Shultz, Dmitry 
mailto:dmitry_shu...@kaltire.com>> ha scritto:
Hi Andrea,

Thanks for getting back to me!

JFYI, I’m trying to set the ServiceBusConstants.CORRELATION_ID header on the 
exchange before sending it to service bus and it doesn’t do anything (no 
correlationId on the receiving side) as well. Looks like all the headers being 
reset by something.

Dmitry

From: Andrea Cosentino mailto:anco...@gmail.com>>
Sent: Wednesday, January 17, 2024 10:18 AM
To: users@camel.apache.org<mailto:users@camel.apache.org>
Subject: Re: How to set custom header(s) on message sent to Azure Service Bus

I'll try to check tomorrow and get back to you. Sorry for the la

Re: How to set custom header(s) on message sent to Azure Service Bus

[Andrea Cosentino]

It turns out that the correlationId was supported only as consumer header.
I created CAMEL-20444 and opened this PR 
https://github.com/apache/camel/pull/13237
For the backport, I see you're using 3.14.10, but 3.14.x won't take any new 
release, at least this could be backported to 3.21.x or 3.22.x, but those 
releases are JDK 11.
There is now plan to backport any feature or bug fix to Java 8 Camel releases 
now.
--Andrea Cosentino --Apache Camel PMC 
ChairApache Karaf CommitterApache Servicemix PMC MemberEmail: 
ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd 

On Tuesday, February 20, 2024 at 08:08:45 PM GMT+1, Shultz, Dmitry 
 wrote:  
 
 When I test it using Quarkus (camel-azure-servicebus 4.3.0) I can see the 
CamelAzureServiceBusApplicationProperties map is preserved (I see the values on 
the receive side), but CamelAzureServiceBusCorrelationId is still null (setting 
CamelAzureServiceBusApplicationProperties and CamelAzureServiceBusCorrelationId 
at the same time).

In case there would be a fix for the CamelAzureServiceBusCorrelationId, how 
likely that is would be ported to the Java 8 Camel?

From: Andrea Cosentino 
Sent: Tuesday, February 20, 2024 9:45 AM
To: Shultz, Dmitry 
Cc: users@camel.apache.org
Subject: Re: How to set custom header(s) on message sent to Azure Service Bus

I can try to have a look, but probably with Camel 4. x. Can you double check if 
with 4. 0. 4 or 4. 4. 0 is still the case? Il giorno mar 20 feb 2024 alle ore 
18: 11 Shultz, Dmitry  ha scritto: Yes, I followed 
this
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
ZjQcmQRYFpfptBannerEnd
I can try to have a look, but probably with Camel 4.x.

Can you double check if with 4.0.4 or 4.4.0 is still the case?

Il giorno mar 20 feb 2024 alle ore 18:11 Shultz, Dmitry 
mailto:dmitry_shu...@kaltire.com>> ha scritto:
Yes, I followed this code https://stackoverflow.com/a/73886983 
[stackoverflow.com]<https://urldefense.com/v3/__https:/stackoverflow.com/a/73886983__;!!LdWlNaMnLCM!aNdA0OgZVoMVEnVszt4Sxyy4wlFxCMa2Gr__jp3ek9WQQ-do3lvIcVoQL6l3rbq7tGkXhn6GRNsuz2j2_wwp$>
 and nothing ended up being set.
Also, as I said setting the ServiceBusConstants.CORRELATION_ID has no effect 
when checked at the destination.


From: Andrea Cosentino mailto:anco...@gmail.com>>
Sent: Tuesday, February 20, 2024 3:17 AM
To: Shultz, Dmitry mailto:dmitry_shu...@kaltire.com>>
Cc: users@camel.apache.org<mailto:users@camel.apache.org>
Subject: Re: How to set custom header(s) on message sent to Azure Service Bus

I find some time this morning and sorry for the long delay. Did you had a look 
at the ServiceBusConstants. APPLICATION_PROPERTIES? They are meant for this 
purpose. Il giorno ven 9 feb 2024 alle ore 21: 20 Shultz, Dmitry 

ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
ZjQcmQRYFpfptBannerEnd
I find some time this morning and sorry for the long delay.

Did you had a look at the ServiceBusConstants.APPLICATION_PROPERTIES?

They are meant for this purpose.

Il giorno ven 9 feb 2024 alle ore 21:20 Shultz, Dmitry 
mailto:dmitry_shu...@kaltire.com>> ha scritto:
Next week would be awesome! Thanks Andrea.

From: Andrea Cosentino mailto:anco...@gmail.com>>
Sent: Friday, February 9, 2024 11:06 AM
To: Shultz, Dmitry mailto:dmitry_shu...@kaltire.com>>
Cc: users@camel.apache.org<mailto:users@camel.apache.org>
Subject: Re: How to set custom header(s) on message sent to Azure Service Bus

Sorry, i still have to look at this. I hope to find some time next week. Il ven 
9 feb 2024, 19: 47 Shultz, Dmitry  ha scritto: Hi 
Andrea, Thanks for getting back to me! JFYI, I’m trying to set the 
ServiceBusConstants. CORRELATION_ID
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
ZjQcmQRYFpfptBannerEnd
Sorry, i still have to look at this.

I hope to find some time next week.

Il ven 9 feb 2024, 19:47 Shultz, Dmitry 
mailto:dmitry_shu...@kaltire.com>> ha scritto:
Hi Andrea,

Thanks for getting back to me!

JFYI, I’m trying to set the ServiceBusConstants.CORRELATION_ID header on the 
exchange before sending it to service bus and it doesn’t do anything (no 
correlationId on the receiving side) as well. Looks like all the headers being 
reset by something.

Dmitry

From: Andrea Cosentino mailto:anco...@gmail.com>>
Sent: Wednesday, January 17, 2024 10:18 AM
To: users@camel.apache.org<mailto:users@camel.apache.org>
Subject: Re: How to set custom header(s) on message sent to Azure Service Bus

I'll try to check tomorrow and get back to you. Sorry for the late reply Il mer 
17 gen 2024, 19: 08 Shultz, Dmitry  ha scritto: > 
Have anybody used/successfully set headers on the message sent to Azure >
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
ZjQcmQRYFpfptBannerEnd

I'll try to check tomorrow and get back to you.



Sorry for the late reply



Il mer 17 gen 2024, 19:08 Shultz, Dmitry 
mailto:dmitry_shu

Re: How to set custom header(s) on message sent to Azure Service Bus

[Andrea Cosentino]

I can try to have a look, but probably with Camel 4.x.

Can you double check if with 4.0.4 or 4.4.0 is still the case?

Il giorno mar 20 feb 2024 alle ore 18:11 Shultz, Dmitry <
dmitry_shu...@kaltire.com> ha scritto:

> Yes, I followed this code https://stackoverflow.com/a/73886983 and
> nothing ended up being set.
>
> Also, as I said setting the ServiceBusConstants.CORRELATION_ID has no
> effect when checked at the destination.
>
>
>
>
>
> *From:* Andrea Cosentino 
> *Sent:* Tuesday, February 20, 2024 3:17 AM
> *To:* Shultz, Dmitry 
> *Cc:* users@camel.apache.org
> *Subject:* Re: How to set custom header(s) on message sent to Azure
> Service Bus
>
>
>
> I find some time this morning and sorry for the long delay. Did you had a
> look at the ServiceBusConstants. APPLICATION_PROPERTIES? They are meant
> for this purpose. Il giorno ven 9 feb 2024 alle ore 21: 20 Shultz, Dmitry
> 
>
> ZjQcmQRYFpfptBannerStart
>
> *This Message Is From an External Sender *
>
> ZjQcmQRYFpfptBannerEnd
>
> I find some time this morning and sorry for the long delay.
>
>
>
> Did you had a look at the ServiceBusConstants.APPLICATION_PROPERTIES?
>
>
>
> They are meant for this purpose.
>
>
>
> Il giorno ven 9 feb 2024 alle ore 21:20 Shultz, Dmitry <
> dmitry_shu...@kaltire.com> ha scritto:
>
> Next week would be awesome! Thanks Andrea.
>
>
>
> *From:* Andrea Cosentino 
> *Sent:* Friday, February 9, 2024 11:06 AM
> *To:* Shultz, Dmitry 
> *Cc:* users@camel.apache.org
> *Subject:* Re: How to set custom header(s) on message sent to Azure
> Service Bus
>
>
>
> Sorry, i still have to look at this. I hope to find some time next week.
> Il ven 9 feb 2024, 19: 47 Shultz, Dmitry  ha
> scritto: Hi Andrea, Thanks for getting back to me! JFYI, I’m trying to set
> the ServiceBusConstants. CORRELATION_ID
>
> ZjQcmQRYFpfptBannerStart
>
> *This Message Is From an External Sender *
>
> ZjQcmQRYFpfptBannerEnd
>
> Sorry, i still have to look at this.
>
>
>
> I hope to find some time next week.
>
>
>
> Il ven 9 feb 2024, 19:47 Shultz, Dmitry  ha
> scritto:
>
> Hi Andrea,
>
>
>
> Thanks for getting back to me!
>
>
>
> JFYI, I’m trying to set the ServiceBusConstants.CORRELATION_ID header on
> the exchange before sending it to service bus and it doesn’t do anything
> (no correlationId on the receiving side) as well. Looks like all the
> headers being reset by something.
>
>
>
> Dmitry
>
>
>
> *From:* Andrea Cosentino 
> *Sent:* Wednesday, January 17, 2024 10:18 AM
> *To:* users@camel.apache.org
> *Subject:* Re: How to set custom header(s) on message sent to Azure
> Service Bus
>
>
>
> I'll try to check tomorrow and get back to you. Sorry for the late reply
> Il mer 17 gen 2024, 19: 08 Shultz, Dmitry 
> ha scritto: > Have anybody used/successfully set headers on the message
> sent to Azure >
>
> ZjQcmQRYFpfptBannerStart
>
> *This Message Is From an External Sender *
>
> ZjQcmQRYFpfptBannerEnd
>
> I'll try to check tomorrow and get back to you.
>
>
>
> Sorry for the late reply
>
>
>
> Il mer 17 gen 2024, 19:08 Shultz, Dmitry  ha
>
> scritto:
>
>
>
> > Have anybody used/successfully set headers on the message sent to Azure
>
> > Service Bus before?
>
> >
>
> >
>
> > Dmitry Shultz
>
> > Senior Software Developer
>
> >
>
> > [cid:image001.png@01D051C6.BA585530]
>
> >
>
> > 1540 Kalamalka Lake Rd.
>
> > Vernon, BC V1T 6V2
>
> > t: 1-250-541-5447
>
> > KalTire.com
>
> >
>
> >
>
> > 
>
> > From: Shultz, Dmitry
>
> > Sent: 03 January 2024 19:08
>
> > To: users@camel.apache.org 
>
> > Subject: How to set custom header(s) on message sent to Azure Service Bus
>
> >
>
> >
>
> > Hi,
>
> >
>
> >
>
> >
>
> > I’m following this
>
> > https://urldefense.com/v3/__https://stackoverflow.com/questions/73886170/how-to-add-custom-properties-or-label-subject-for-azure-servicebus-topic-message__;!!LdWlNaMnLCM!fvRT9rucP7nxRYY_uiE0J6DPxhFrtSjgdkqKbHDou8H7hkTvafcdbNFZ5tPRrz-14z6qcJdtX5OqP-tCd5TD$
> >  
> > <https://urldefense.com/v3/__https:/stackoverflow.com/questions/73886170/how-to-add-custom-properties-or-label-subject-for-azure-servicebus-topic-message__;!!LdWlNaMnLCM!fvRT9rucP7nxRYY_uiE0J6DPxhFrtSjgdkqKbHDou8H7hkTvafcdbNFZ5tPRrz-14z6qcJdtX5OqP-tCd5TD$>
>
> > trying to set some custom headers for messages sent to Azure Service Bus,
>
> > but when I read the same message from the service bus it has no custom
>
> > headers and empty CamelAzureServiceBusApplicationProperties map.  Using
>
> > Camel 3.14.10
>
> >
>
> >
>
> >
>
> > Is there a bug or I’m doing/expecting something wrong?
>
> >
>
> >
>
> >
>
> > Thanks,
>
> >
>
> > Dmitry
>
> >
>
>

Re: How to set custom header(s) on message sent to Azure Service Bus

[Andrea Cosentino]

I find some time this morning and sorry for the long delay.

Did you had a look at the ServiceBusConstants.APPLICATION_PROPERTIES?

They are meant for this purpose.

Il giorno ven 9 feb 2024 alle ore 21:20 Shultz, Dmitry <
dmitry_shu...@kaltire.com> ha scritto:

> Next week would be awesome! Thanks Andrea.
>
>
>
> *From:* Andrea Cosentino 
> *Sent:* Friday, February 9, 2024 11:06 AM
> *To:* Shultz, Dmitry 
> *Cc:* users@camel.apache.org
> *Subject:* Re: How to set custom header(s) on message sent to Azure
> Service Bus
>
>
>
> Sorry, i still have to look at this. I hope to find some time next week.
> Il ven 9 feb 2024, 19: 47 Shultz, Dmitry  ha
> scritto: Hi Andrea, Thanks for getting back to me! JFYI, I’m trying to set
> the ServiceBusConstants. CORRELATION_ID
>
> ZjQcmQRYFpfptBannerStart
>
> *This Message Is From an External Sender *
>
> ZjQcmQRYFpfptBannerEnd
>
> Sorry, i still have to look at this.
>
>
>
> I hope to find some time next week.
>
>
>
> Il ven 9 feb 2024, 19:47 Shultz, Dmitry  ha
> scritto:
>
> Hi Andrea,
>
>
>
> Thanks for getting back to me!
>
>
>
> JFYI, I’m trying to set the ServiceBusConstants.CORRELATION_ID header on
> the exchange before sending it to service bus and it doesn’t do anything
> (no correlationId on the receiving side) as well. Looks like all the
> headers being reset by something.
>
>
>
> Dmitry
>
>
>
> *From:* Andrea Cosentino 
> *Sent:* Wednesday, January 17, 2024 10:18 AM
> *To:* users@camel.apache.org
> *Subject:* Re: How to set custom header(s) on message sent to Azure
> Service Bus
>
>
>
> I'll try to check tomorrow and get back to you. Sorry for the late reply
> Il mer 17 gen 2024, 19: 08 Shultz, Dmitry 
> ha scritto: > Have anybody used/successfully set headers on the message
> sent to Azure >
>
> ZjQcmQRYFpfptBannerStart
>
> *This Message Is From an External Sender *
>
> ZjQcmQRYFpfptBannerEnd
>
> I'll try to check tomorrow and get back to you.
>
>
>
> Sorry for the late reply
>
>
>
> Il mer 17 gen 2024, 19:08 Shultz, Dmitry  ha
>
> scritto:
>
>
>
> > Have anybody used/successfully set headers on the message sent to Azure
>
> > Service Bus before?
>
> >
>
> >
>
> > Dmitry Shultz
>
> > Senior Software Developer
>
> >
>
> > [cid:image001.png@01D051C6.BA585530]
>
> >
>
> > 1540 Kalamalka Lake Rd.
>
> > Vernon, BC V1T 6V2
>
> > t: 1-250-541-5447
>
> > KalTire.com
>
> >
>
> >
>
> > 
>
> > From: Shultz, Dmitry
>
> > Sent: 03 January 2024 19:08
>
> > To: users@camel.apache.org 
>
> > Subject: How to set custom header(s) on message sent to Azure Service Bus
>
> >
>
> >
>
> > Hi,
>
> >
>
> >
>
> >
>
> > I’m following this
>
> > https://urldefense.com/v3/__https://stackoverflow.com/questions/73886170/how-to-add-custom-properties-or-label-subject-for-azure-servicebus-topic-message__;!!LdWlNaMnLCM!fvRT9rucP7nxRYY_uiE0J6DPxhFrtSjgdkqKbHDou8H7hkTvafcdbNFZ5tPRrz-14z6qcJdtX5OqP-tCd5TD$
> >  
> > <https://urldefense.com/v3/__https:/stackoverflow.com/questions/73886170/how-to-add-custom-properties-or-label-subject-for-azure-servicebus-topic-message__;!!LdWlNaMnLCM!fvRT9rucP7nxRYY_uiE0J6DPxhFrtSjgdkqKbHDou8H7hkTvafcdbNFZ5tPRrz-14z6qcJdtX5OqP-tCd5TD$>
>
> > trying to set some custom headers for messages sent to Azure Service Bus,
>
> > but when I read the same message from the service bus it has no custom
>
> > headers and empty CamelAzureServiceBusApplicationProperties map.  Using
>
> > Camel 3.14.10
>
> >
>
> >
>
> >
>
> > Is there a bug or I’m doing/expecting something wrong?
>
> >
>
> >
>
> >
>
> > Thanks,
>
> >
>
> > Dmitry
>
> >
>
>

[VOTE] Release Apache Camel Kamelets 4.4.0

[Andrea Cosentino]

Hello all,

This is a vote for releasing camel-kamelets 4.4.0

This is the first release of camel-kamelets supporting LTS Camel 4.4.0 and
it contains many new Kamelets and a lot of fixes.

Kamelets release files:
https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.4.0
Kamelets staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1681
Kamelets Tag:
https://github.com/apache/camel-kamelets/releases/tag/v4.4.0

Please cast your vote.

[ ] +1 Release camel-kamelets 4.4.0
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Here's my +1.

Thanks,
Andrea Cosentino

https://camel.apache.org/security/CVE-2024-23114.html: CVE-2024-23114: Apache Camel: Camel-CassandraQL: Unsafe Deserialization from CassandraAggregationRepository

[Andrea Cosentino]

Severity: important

Affected versions:

- Apache Camel 3.0.0 before 3.21.4
- Apache Camel 3.22.0 before 3.22.1
- Apache Camel 4.0.0 before 4.0.4
- Apache Camel 4.1.0 before 4.4.0

Description:

Deserialization of Untrusted Data vulnerability in Apache Camel CassandraQL 
Component AggregationRepository which is vulnerable to unsafe deserialization. 
Under specific conditions it is possible to deserialize malicious payload.This 
issue affects Apache Camel: from 3.0.0 before 3.21.4, from 3.22.0 before 
3.22.1, from 4.0.0 before 4.0.4, from 4.1.0 before 4.4.0.

Users are recommended to upgrade to version 4.4.0, which fixes the issue. If 
users are on the 4.0.x LTS releases stream, then they are suggested to upgrade 
to 4.0.4. If users are on 3.x, they are suggested to move to 3.21.4 or 3.22.1

This issue is being tracked as CAMEL-20306 

Credit:

Federico Mariani From Apache Software Foundation (finder)
Andrea Cosentino from Apache Software Foundation (finder)

References:

https://camel.apache.org/
https://www.cve.org/CVERecord?id=CVE-2024-23114
https://issues.apache.org/jira/browse/CAMEL-20306

https://camel.apache.org/security/CVE-2024-22369.html: CVE-2024-22369: Apache Camel: Camel-SQL: Unsafe Deserialization from JDBCAggregationRepository

[Andrea Cosentino]

Severity: important

Affected versions:

- Apache Camel 3.0.0 before 3.21.4
- Apache Camel 3.22.0 before 3.22.1
- Apache Camel 4.0.0 before 4.0.4
- Apache Camel 4.1.0 before 4.4.0

Description:

Deserialization of Untrusted Data vulnerability in Apache Camel SQL 
ComponentThis issue affects Apache Camel: from 3.0.0 before 3.21.4, from 3.22.0 
before 3.22.1, from 4.0.0 before 4.0.4, from 4.1.0 before 4.4.0.

Users are recommended to upgrade to version 4.4.0, which fixes the issue. If 
users are on the 4.0.x LTS releases stream, then they are suggested to upgrade 
to 4.0.4. If users are on 3.x, they are suggested to move to 3.21.4 or 3.22.1

This issue is being tracked as CAMEL-20303 

Credit:

Ziyang Chen from HuaWei Open Source Management Center (finder)
Pingtao Wei from HuaWei Open Source Management Center (finder)
Haoran Zhi from HuaWei Open Source Management Center (finder)

References:

https://camel.apache.org/
https://www.cve.org/CVERecord?id=CVE-2024-22369
https://issues.apache.org/jira/browse/CAMEL-20303

Re: How to set custom header(s) on message sent to Azure Service Bus

[Andrea Cosentino]

Sorry, i still have to look at this.

I hope to find some time next week.

Il ven 9 feb 2024, 19:47 Shultz, Dmitry  ha
scritto:

> Hi Andrea,
>
>
>
> Thanks for getting back to me!
>
>
>
> JFYI, I’m trying to set the ServiceBusConstants.CORRELATION_ID header on
> the exchange before sending it to service bus and it doesn’t do anything
> (no correlationId on the receiving side) as well. Looks like all the
> headers being reset by something.
>
>
>
> Dmitry
>
>
>
> *From:* Andrea Cosentino 
> *Sent:* Wednesday, January 17, 2024 10:18 AM
> *To:* users@camel.apache.org
> *Subject:* Re: How to set custom header(s) on message sent to Azure
> Service Bus
>
>
>
> I'll try to check tomorrow and get back to you. Sorry for the late reply
> Il mer 17 gen 2024, 19: 08 Shultz, Dmitry 
> ha scritto: > Have anybody used/successfully set headers on the message
> sent to Azure >
>
> ZjQcmQRYFpfptBannerStart
>
> *This Message Is From an External Sender *
>
> ZjQcmQRYFpfptBannerEnd
>
> I'll try to check tomorrow and get back to you.
>
>
>
> Sorry for the late reply
>
>
>
> Il mer 17 gen 2024, 19:08 Shultz, Dmitry  ha
>
> scritto:
>
>
>
> > Have anybody used/successfully set headers on the message sent to Azure
>
> > Service Bus before?
>
> >
>
> >
>
> > Dmitry Shultz
>
> > Senior Software Developer
>
> >
>
> > [cid:image001.png@01D051C6.BA585530]
>
> >
>
> > 1540 Kalamalka Lake Rd.
>
> > Vernon, BC V1T 6V2
>
> > t: 1-250-541-5447
>
> > KalTire.com
>
> >
>
> >
>
> > 
>
> > From: Shultz, Dmitry
>
> > Sent: 03 January 2024 19:08
>
> > To: users@camel.apache.org 
>
> > Subject: How to set custom header(s) on message sent to Azure Service Bus
>
> >
>
> >
>
> > Hi,
>
> >
>
> >
>
> >
>
> > I’m following this
>
> > https://urldefense.com/v3/__https://stackoverflow.com/questions/73886170/how-to-add-custom-properties-or-label-subject-for-azure-servicebus-topic-message__;!!LdWlNaMnLCM!fvRT9rucP7nxRYY_uiE0J6DPxhFrtSjgdkqKbHDou8H7hkTvafcdbNFZ5tPRrz-14z6qcJdtX5OqP-tCd5TD$
> >  
> > <https://urldefense.com/v3/__https:/stackoverflow.com/questions/73886170/how-to-add-custom-properties-or-label-subject-for-azure-servicebus-topic-message__;!!LdWlNaMnLCM!fvRT9rucP7nxRYY_uiE0J6DPxhFrtSjgdkqKbHDou8H7hkTvafcdbNFZ5tPRrz-14z6qcJdtX5OqP-tCd5TD$>
>
> > trying to set some custom headers for messages sent to Azure Service Bus,
>
> > but when I read the same message from the service bus it has no custom
>
> > headers and empty CamelAzureServiceBusApplicationProperties map.  Using
>
> > Camel 3.14.10
>
> >
>
> >
>
> >
>
> > Is there a bug or I’m doing/expecting something wrong?
>
> >
>
> >
>
> >
>
> > Thanks,
>
> >
>
> > Dmitry
>
> >
>
>

Re: How does Apache Camel (un)marshal with 'gzipDeflater' work?

[Andrea Cosentino]

I guess it's an error in documentation.

Il mar 6 feb 2024, 15:57 Quirin Ertl  ha
scritto:

> In this code snippet I want to unzip a gzip body using Camel. According to
> the Camel documentation, no other dependencies are needed apart from
> camel-core.
>
> Link:
> https://camel.apache.org/components/4.0.x/dataformats/gzipDeflater-dataformat.html#_dependencies
>
>
> public static void main(final String[] args) throws Exception {
> try (final CamelContext context = new DefaultCamelContext()) {
> context.addRoutes(new RouteBuilder() {
> @Override
> public void configure() {
>
> this.from("direct:test").unmarshal().gzipDeflater().to("seda:test2");
> }
> });
> context.start();
> context.createProducerTemplate().sendBody("direct:test", "this is
> not gzip but it does not matter.");
> Thread.currentThread().join();
> }
> }
>
>
> When I run the code I get this error:
>
> Caused by: java.lang.IllegalArgumentException: Data format 'gzipDeflater'
> could not be created. Ensure that the data format is valid and the
> associated Camel component is present on the classpath
> at
> org.apache.camel.reifier.dataformat.DataFormatReifier.createDataFormat(DataFormatReifier.java:279)
> at
> org.apache.camel.reifier.dataformat.DataFormatReifier.getDataFormat(DataFormatReifier.java:152)
> at
> org.apache.camel.reifier.dataformat.DataFormatReifier.getDataFormat(DataFormatReifier.java:112)
> at
> org.apache.camel.reifier.UnmarshalReifier.createProcessor(UnmarshalReifier.java:35)
> at
> org.apache.camel.reifier.ProcessorReifier.makeProcessor(ProcessorReifier.java:870)
> at
> org.apache.camel.reifier.ProcessorReifier.addRoutes(ProcessorReifier.java:610)
> at
> org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:213)
> ... 11 more
>
> The error message says I need another dependency, but the Camel
> documentation says I don't need one. How is this supposed to work?
>
>
>

Re: Why has timePeriodMillis for the Throttle EIP been removed and how can I account for this

[Andrea Cosentino]

This is how you can unsubscribe. In the way you've done it won't work.

https://camel.apache.org/community/mailing-list/

Il giorno ven 2 feb 2024 alle ore 14:25 George Daswani <
georgedasw...@hotmail.com> ha scritto:

> unsubscribe
>
> On Fri, Feb 2, 2024 at 2:29 AM Jono Morris  wrote:
>
> >
> > The Throttler previously employed a fixed windows algorithm, allowing a
> > fixed number of calls in a particular period. This is susceptible to
> > request bursts, e.g. for a limit of 100 requests/hour, all 100 requests
> > might be made in the first minute.
> >
> > Subsequently the algorithm was changed to a leaky bucket implementation.
> > Callers try to acquire a permit and block if all the available permits
> have
> > already been acquired. Permits are released after a caller completes
> > processing.  So this limits the number of concurrent requests.
> >
> > Will discuss with the team to find the best way forward.
> >
> > Regards
> > Jono
> >
> > On 2024/02/01 16:49:14 Otavio Rodolfo Piske wrote:
> > > Hello,
> > >
> > > Quite frankly, I don't know.
> > >
> > > However, I did raise this question on the PR that introduced the change
> > so
> > > we can discuss how we can improve the documentation for scenarios such
> as
> > > the one you raised.
> > >
> > > Kind regards
> > >
> > > On Wed, Jan 31, 2024 at 4:05 PM Schmeier, Jannik <
> j.schme...@fraport.de>
> > > wrote:
> > >
> > > > Hello,
> > > >
> > > > I'm wondering why the timePeriodMillis option has been removed for
> the
> > > > throttle EIP.
> > > >
> > > > I have an endpoint that can only receive about 5 requests per minute,
> > else
> > > > the request will fail. I accounted for that by using a
> timePeriodMillis
> > > > setting of 6 ms and a throttle value of 4.
> > > > Now with the updated Throttle EIP I can't do that anymore.
> > > >
> > > > The upgrade guide suggests that the default time period is 1000 ms
> now,
> > > > but obviously I can't work with that:
> > > >
> >
> https://camel.apache.org/manual/camel-4x-upgrade-guide-4_3.html#_throttle_eip
> > > >
> > > > Any suggestions?
> > > >
> > > > Best regards
> > > >
> > >
> > >
> > > --
> > > Otavio R. Piske
> > > http://orpiske.net
> > >
> >
>

[RESULT] [VOTE] Release Apache Camel Kamelets 4.0.3

[Andrea Cosentino]

Hello all,

The vote passes with the following result:

7 +1 binding votes: Andrea Cosentino, Claus Ibsen, Babak Vahdat, Andrea
Tarocchi, Otavio Rodolfo Piske, Zineb Bendhiba and Pasquale Congiusti

3 +1 non-binding votes: Gaelle Fournier, Claudio Miranda and Christoph
Deppisch

Thanks to all the voters.

I'll go ahead with the process.

Re: [VOTE] Release Apache Camel Kamelets 4.0.3

[Andrea Cosentino]

Thanks all the vote passed.

I'll go ahead with the release process.

Il giorno mer 17 gen 2024 alle ore 19:39 Christoph Deppisch
 ha scritto:

> +1 (non-binding)
>
> Thank you Andrea!
>
> Andrea Cosentino  schrieb am Mi., 17. Jan. 2024, 09:33:
>
> > Hello all,
> >
> > This is a vote for releasing camel-kamelets 4.0.3
> >
> > This release will support the 4.0.3 release of Apache Camel. The aim of
> the
> > release is to have a catalog to use in generating camel-kafka-connector
> > 4.0.3 release.
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.3
> > Kamelets staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1668
> > Kamelets Tag:
> > https://github.com/apache/camel-kamelets/releases/tag/v4.0.3
> >
> > Please cast your vote.
> >
> > [ ] +1 Release camel-kamelets 4.0.3
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Here's my +1.
> >
> > Thanks,
> > Andrea Cosentino
> >
>

Re: How to set custom header(s) on message sent to Azure Service Bus

[Andrea Cosentino]

I didn't find the time yet, but I'll try to look at that soon.

Il giorno mer 17 gen 2024 alle ore 19:18 Andrea Cosentino 
ha scritto:

> I'll try to check tomorrow and get back to you.
>
> Sorry for the late reply
>
> Il mer 17 gen 2024, 19:08 Shultz, Dmitry  ha
> scritto:
>
>> Have anybody used/successfully set headers on the message sent to Azure
>> Service Bus before?
>>
>>
>> Dmitry Shultz
>> Senior Software Developer
>>
>> [cid:image001.png@01D051C6.BA585530]
>>
>> 1540 Kalamalka Lake Rd.
>> Vernon, BC V1T 6V2
>> t: 1-250-541-5447
>> KalTire.com
>>
>>
>> 
>> From: Shultz, Dmitry
>> Sent: 03 January 2024 19:08
>> To: users@camel.apache.org 
>> Subject: How to set custom header(s) on message sent to Azure Service Bus
>>
>>
>> Hi,
>>
>>
>>
>> I’m following this
>> https://stackoverflow.com/questions/73886170/how-to-add-custom-properties-or-label-subject-for-azure-servicebus-topic-message
>> trying to set some custom headers for messages sent to Azure Service Bus,
>> but when I read the same message from the service bus it has no custom
>> headers and empty CamelAzureServiceBusApplicationProperties map.  Using
>> Camel 3.14.10
>>
>>
>>
>> Is there a bug or I’m doing/expecting something wrong?
>>
>>
>>
>> Thanks,
>>
>> Dmitry
>>
>

Re: How to set custom header(s) on message sent to Azure Service Bus

[Andrea Cosentino]

I'll try to check tomorrow and get back to you.

Sorry for the late reply

Il mer 17 gen 2024, 19:08 Shultz, Dmitry  ha
scritto:

> Have anybody used/successfully set headers on the message sent to Azure
> Service Bus before?
>
>
> Dmitry Shultz
> Senior Software Developer
>
> [cid:image001.png@01D051C6.BA585530]
>
> 1540 Kalamalka Lake Rd.
> Vernon, BC V1T 6V2
> t: 1-250-541-5447
> KalTire.com
>
>
> 
> From: Shultz, Dmitry
> Sent: 03 January 2024 19:08
> To: users@camel.apache.org 
> Subject: How to set custom header(s) on message sent to Azure Service Bus
>
>
> Hi,
>
>
>
> I’m following this
> https://stackoverflow.com/questions/73886170/how-to-add-custom-properties-or-label-subject-for-azure-servicebus-topic-message
> trying to set some custom headers for messages sent to Azure Service Bus,
> but when I read the same message from the service bus it has no custom
> headers and empty CamelAzureServiceBusApplicationProperties map.  Using
> Camel 3.14.10
>
>
>
> Is there a bug or I’m doing/expecting something wrong?
>
>
>
> Thanks,
>
> Dmitry
>

[VOTE] Release Apache Camel Kamelets 4.0.3

[Andrea Cosentino]

Hello all,

This is a vote for releasing camel-kamelets 4.0.3

This release will support the 4.0.3 release of Apache Camel. The aim of the
release is to have a catalog to use in generating camel-kafka-connector
4.0.3 release.

Kamelets release files:
https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.3
Kamelets staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1668
Kamelets Tag:
https://github.com/apache/camel-kamelets/releases/tag/v4.0.3

Please cast your vote.

[ ] +1 Release camel-kamelets 4.0.3
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Here's my +1.

Thanks,
Andrea Cosentino

Re: Functions in Camel

[Andrea Cosentino]

It really seems the Kamelets' mission

Il lun 8 gen 2024, 15:59 Pasquale Congiusti 
ha scritto:

> Hi Raymond,
> Can't be a Kamelet considered for such a feature? I think it's one of its
> purposes as well.
>
> Pasquale.
>
> On Mon, Jan 8, 2024 at 3:21 PM ski n  wrote:
>
> > Question/Discussion:
> >
> > Do you think "functions" in the Camel DSL make sense?
> >
> > Explanation:
> >
> > Say you have to following route:
> >
> > from("direct:a")
> > .setHeader("myHeader", constant("test"))
> > .to("direct:b");
> >
> > And then you have a similar route:
> >
> > from("direct:c")
> > .setHeader("myHeader2", constant("test"))
> > .to("direct:d");
> >
> > As you are setting it more or less the same you could make a
> routeTemplate:
> >
> > routeTemplate("someFunction")
> > // here we define the required input parameters (with a
> default
> > value)
> >  .templateParameter("headerName", "myHeader")
> > .from("direct:a")
> >  .setHeader("{{headerName}}", constant("test"))
> >
> > And then you can:
> >
> > from("direct:a")
> > .to("direct:someFunction")
> > .to("direct:b");
> >
> > And for the second route:
> >
> > from("direct:c")
> > .to("direct:someFunction")
> > .to("direct:d");
> >
> >
> > This however seems a bit cumbersome, because:
> >
> > 1. I must have a from statement in my subroute (which should be just a
> > function).
> > 2. I need to know the component of the from statement and call it with a
> > "to" statement.
> > 3. I need to create the route from routeTemplates before the route starts
> > and I need to do this everytime I use that 'function'.
> > 4. If I want to use the same code then I need to call the same route
> > multiple times,
> >but in certain cases this can become a bottle-neck (think of Seda of
> JMS
> > Queues).
> >Especially when call it from hundreds of places, this maybe
> troublesome
> > (throughput or memory).
> >
> >
> > Would be easier and more direct to have like this:
> >
> > function("someFunction")
> > .parameter("headerName", "myHeader")
> > .setHeader("{{headerName}}", constant("test"))
> >
> > And then call it:
> >
> > from("direct:a")
> > .function("someFunction")
> > .to("direct:b");
> >
> > And:
> >
> > from("direct:c")
> > .function("someFunction")
> > .parameter("myHeader2")
> > .to("direct:d");
> >
> > On install the routes are exactly the same as the first and second route
> > (only reused).
> >
> > What do think?
> >
> > Raymond
> >
>

[RESULT][VOTE] Release Apache Camel Kamelets 4.3.0

[Andrea Cosentino]

Hello all,

The vote passes with the following result:

3 +1 binding votes: Andrea Cosentino, Zineb Bendhiba and Claus Ibsen

3 +1 non-binding votes: Claudio Miranda, Christoph Deppisch and Gaelle
Fournier

I'll go ahead with the release.

Thanks to all the voters.

Re: [VOTE] Release Apache Camel Kamelets 4.3.0

[Andrea Cosentino]

Thanks all, the vote passes.

I'll go ahead with the workflow.

Cheers.

Il giorno mer 20 dic 2023 alle ore 10:16 Gaëlle Fournier <
gaelle.fournier.w...@gmail.com> ha scritto:

> +1 (non-binding)
>
> Thanks!
>
> ---
> Gaëlle
>
>
> Le mar. 19 déc. 2023 à 09:36, Andrea Cosentino  a
> écrit :
>
> > Hello all,
> >
> > This is a vote for releasing camel-kamelets 4.3.0
> >
> > This release will support the 4.3.0 release of Apache Camel.
> >
> > More info at:
> > https://github.com/apache/camel-kamelets/blob/main/CHANGELOG.md
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.3.0
> > Kamelets staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1660
> > Kamelets Tag:
> > https://github.com/apache/camel-kamelets/releases/tag/v4.3.0
> >
> > Please cast your vote.
> >
> > [ ] +1 Release camel-kamelets 4.3.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Here's my +1.
> >
> > Thanks,
> > Andrea Cosentino
> >
>

[VOTE] Release Apache Camel Kamelets 4.3.0

[Andrea Cosentino]

Hello all,

This is a vote for releasing camel-kamelets 4.3.0

This release will support the 4.3.0 release of Apache Camel.

More info at:
https://github.com/apache/camel-kamelets/blob/main/CHANGELOG.md

Kamelets release files:
https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.3.0
Kamelets staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1660
Kamelets Tag:
https://github.com/apache/camel-kamelets/releases/tag/v4.3.0

Please cast your vote.

[ ] +1 Release camel-kamelets 4.3.0
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Here's my +1.

Thanks,
Andrea Cosentino

Re: AWS Kinesis Consumer

[Andrea Cosentino]

Hello,

The PR looks good to me, I just would like to have more feedback from
others (in particular, Otavio, the one writing the Resume API and the
Kinesis adapter.

Il giorno sab 16 dic 2023 alle ore 13:26 Alphonse Bendt <
alphonse.be...@gmail.com> ha scritto:

> Hi folks,
>
> A couple of days ago, I asked about resuming an AWS kinesis stream
> consumer:
>
> https://lists.apache.org/thread/sc6oks5jckcbj19t06chmfpm6dpwt60t
>
> I have experimented a bit more with the camel codebase and think now that
> there is functionality missing to allow implementing a ResumeStrategy for a
> Kinesis consumer:
>
> I think the consumer should make the shardId available, plus I think the
> API of the KinesisResumeAdapter needs to be modified.
> I have created a Branch with both proposed changes (see
> https://github.com/apache/camel/pull/12462/files).
> With these changes, I could sketch a custom ResumeStrategy (see branch).
>
> Is this something you would accept as a PR?
>
> Regards,
> Alphonse
>
>
>
>

Re: camel-jetty component for camel 4.0.3 : issue while starting app

[Andrea Cosentino]

Happy to help!

Il mar 12 dic 2023, 17:23 Ghassen Kahri  ha
scritto:

> That works for me.
> Thanks 
>
> On Tue, Dec 12, 2023, 16:30 Andrea Cosentino  wrote:
>
> > Camel supporting spring boot 3.2.0 will be 4.3.0, you need to use the
> > Spring boot version coming with camel 4.0.3 I think it is 3.1.6.
> >
> >
> >
> > Il mar 12 dic 2023, 16:19 Ghassen Kahri  ha
> > scritto:
> >
> > > Hi community,
> > > I'm trying to create a rest controller for my camel project, for this
> i'm
> > > using jetty component (same version as camel -> 4.0.3).
> > > I'm facing an understandable problem while starting the project :
> > >
> > > java.lang.IllegalAccessError: class
> > > org.apache.camel.component.jetty.JettyHttpComponent tried to access
> > > protected method 'void
> > > org.eclipse.jetty.server.Handler$AbstractContainer.()'
> > > (org.apache.camel.component.jetty.JettyHttpComponent and
> > > org.eclipse.jetty.server.Handler$AbstractContainer are in unnamed
> module
> > of
> > > loader 'app')
> > >
> > > *my environment :*
> > > Camel version: 4.0.3
> > > Spring Boot version: 3.2.0
> > > JDK: open JDK 17
> > > Platform: ubuntu 20.04.6 LTS
> > > IDE: IntelliJ IDEA 2023.1.3 (Ultimate Edition)
> > >
> >
>

Re: camel-jetty component for camel 4.0.3 : issue while starting app

[Andrea Cosentino]

Camel supporting spring boot 3.2.0 will be 4.3.0, you need to use the
Spring boot version coming with camel 4.0.3 I think it is 3.1.6.



Il mar 12 dic 2023, 16:19 Ghassen Kahri  ha
scritto:

> Hi community,
> I'm trying to create a rest controller for my camel project, for this i'm
> using jetty component (same version as camel -> 4.0.3).
> I'm facing an understandable problem while starting the project :
>
> java.lang.IllegalAccessError: class
> org.apache.camel.component.jetty.JettyHttpComponent tried to access
> protected method 'void
> org.eclipse.jetty.server.Handler$AbstractContainer.()'
> (org.apache.camel.component.jetty.JettyHttpComponent and
> org.eclipse.jetty.server.Handler$AbstractContainer are in unnamed module of
> loader 'app')
>
> *my environment :*
> Camel version: 4.0.3
> Spring Boot version: 3.2.0
> JDK: open JDK 17
> Platform: ubuntu 20.04.6 LTS
> IDE: IntelliJ IDEA 2023.1.3 (Ultimate Edition)
>

[RESULT][VOTE] Release Apache Camel Kamelets 4.2.0

[Andrea Cosentino]

Hello all,

The vote passes with the following result:

5 +1 binding votes: Andrea Cosentino, Zineb Bendhiba, Babak Vahdat, Claus
Ibsen and Otavio Rodolfo Piske

Thanks to all the voters.

I'll go ahead with the process.

Cheers.

Re: Question about Lombok use

[Andrea Cosentino]

Last but not least, there are no clear, IMO, advantages is using it,
despite the fact you'll see less boilerplate code. This laziness is
something I don't understand. IDEs will generate setters/getters for you
just with a shortcut on classes with thousands of fields.

Il giorno dom 19 nov 2023 alle ore 14:47 Andrea Cosentino 
ha scritto:

> Hello,
>
> Let me add also add a couple of points:
> 1. It's true that is just a compile dependency but when you decide to use
> lombok, you also decide that everyone else who deals with your code will
> have to use lombok. Lombok is special in that it is a build-time dependency
> and your IDE needs plugins to figure out what is going on. So this is a big
> drawback in my opinion.
> 2. Going back from Lombok to without Lombok, in big projects is not easy.
> Delombok is not an answer, because it's not reliable.
> 3. We are using the javadoc on getter and setter for generating
> documentation, with Lombok we need to find a different way and since the
> code is generated I don't think it would be easy.
> 4. Debugging Lombok is a pain.
>
> and I could go ahead.
>
> Il giorno dom 19 nov 2023 alle ore 14:12 Claus Ibsen <
> claus.ib...@gmail.com> ha scritto:
>
>> Hi
>>
>> No lombok is not allowed - we have as minimal dependency as possible.
>>
>>
>>
>> On Sun, Nov 19, 2023 at 2:06 PM Steve973  wrote:
>>
>> > Hello.  I completely understand the perspective of limiting the
>> addition of
>> > libraries for various reasons, and especially when the library is
>> included
>> > in the distribution.  I know that I have asked about Lombok before, but
>> it
>> > is great for eliminating a lot of boilerplate code, especially when a
>> class
>> > cannot be created as a Java 17 record.  Also, Lombok is a compile-only
>> > dependency that uses annotation processing to generate the
>> aforementioned
>> > boilerplate.  The license also seems compatible.  Is this something that
>> > can be used in the coding of a component?  If not, could somebody please
>> > explain the problem with it?
>> >
>> > Thanks,
>> > Steve
>> >
>>
>>
>> --
>> Claus Ibsen
>> -
>> @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>

Re: Question about Lombok use

[Andrea Cosentino]

Hello,

Let me add also add a couple of points:
1. It's true that is just a compile dependency but when you decide to use
lombok, you also decide that everyone else who deals with your code will
have to use lombok. Lombok is special in that it is a build-time dependency
and your IDE needs plugins to figure out what is going on. So this is a big
drawback in my opinion.
2. Going back from Lombok to without Lombok, in big projects is not easy.
Delombok is not an answer, because it's not reliable.
3. We are using the javadoc on getter and setter for generating
documentation, with Lombok we need to find a different way and since the
code is generated I don't think it would be easy.
4. Debugging Lombok is a pain.

and I could go ahead.

Il giorno dom 19 nov 2023 alle ore 14:12 Claus Ibsen 
ha scritto:

> Hi
>
> No lombok is not allowed - we have as minimal dependency as possible.
>
>
>
> On Sun, Nov 19, 2023 at 2:06 PM Steve973  wrote:
>
> > Hello.  I completely understand the perspective of limiting the addition
> of
> > libraries for various reasons, and especially when the library is
> included
> > in the distribution.  I know that I have asked about Lombok before, but
> it
> > is great for eliminating a lot of boilerplate code, especially when a
> class
> > cannot be created as a Java 17 record.  Also, Lombok is a compile-only
> > dependency that uses annotation processing to generate the aforementioned
> > boilerplate.  The license also seems compatible.  Is this something that
> > can be used in the coding of a component?  If not, could somebody please
> > explain the problem with it?
> >
> > Thanks,
> > Steve
> >
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

[VOTE] Release Apache Camel Kamelets 4.2.0

[Andrea Cosentino]

Hello all,

This is a vote for releasing camel-kamelets 4.2.0

This release will support the 4.2.0 release of Apache Camel.

This release also:
- Removed the kebab-case syntax for YAML DSL in Kamelets, by moving to
camelCase
- Removed some of the datatypes from the utils to the main Camel release
- Introduce some Kamelets for dealing with Kafka Schema Registries from
Azure and Apicurio

More info at:
https://github.com/apache/camel-kamelets/blob/main/CHANGELOG.md

Kamelets release files:
https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.2.0
Kamelets staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1646
Kamelets Tag:
https://github.com/apache/camel-kamelets/releases/tag/v4.2.0

Please cast your vote.

[ ] +1 Release camel-kamelets 4.2.0
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Here's my +1.

Thanks,
Andrea Cosentino

Re: [ANNOUNCE] Apache Camel 4.2.0 Released

[Andrea Cosentino]

This is the first version where you can run your camel route with Java 21.

The release is still built with JDK 17.

We are waiting for feedback!

Thanks

Il mar 14 nov 2023, 21:31 ski n  ha scritto:

> Great!
>
> Is this the first version that fully supports Java 21?
>
> Raymond
>
> On Tue, Nov 14, 2023 at 8:54 PM Gregor Zurowski 
> wrote:
>
> > The Camel PMC is pleased to announce the release of Apache Camel 4.2.0.
> >
> > Apache Camel is an open source integration framework that empowers you
> > to quickly and easily integrate various systems consuming or producing
> > data.
> >
> > This release contains 115 new features and improvements.
> >
> > The release is available for immediate download at:
> >
> > https://camel.apache.org/download/
> >
> > For more details please take a look at the release notes at:
> >
> > https://camel.apache.org/releases/release-4.2.0/
> >
>

Re: [VOTE] Release Apache Camel 4.2.0

[Andrea Cosentino]

+1 (binding)

Thanks Gregor

Il sab 11 nov 2023, 14:01 Gregor Zurowski  ha
scritto:

> Hi Everyone:
>
> This is a vote to release Apache Camel 4.2.0, a new release with 115
> fixes and improvements.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353662=12311211
>
> == Apache Camel 4.2.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1642/
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1642/org/apache/camel/apache-camel/4.2.0/
>
> Tag: https://github.com/apache/camel/releases/tag/camel-4.2.0
>
> == Apache Camel Spring Boot 4.2.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1643/
>
> Tag:
> https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-4.2.0
>
> Please test this release candidate and cast your vote:
> [ ] +1 Release the binary as Apache Camel and Camel Spring Boot 4.2.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor
>

Re: Stream closed while unzipping in a container

[Andrea Cosentino]

Il ven 3 nov 2023, 09:33 ski n  ha scritto:

> Sorry, I forgot to mention. This was tested with Camel 3.20.7 (JDK 11).
>
> btw:  I'm also in the progress to upgrade to 4, but that has some caveats.
> This is not because of Camel, but more of other things like Junit5,
> Jakarta, ActiveMQ, Java17+.etc. that also needs to upgrade.
>
> btw 2: The migration guide of Camel is excellent. Compliments to the team
> for that. The only feedback I can give here is that I missed the removal of
> “context.getExtensions(...)” for example for ManagedCamelContext.
> Otherwise, it was fairly complete. For removed/add/changed methods it may
> be clearer to put them in a table, with one column (add / removed
> /changed), a column with old syntax and a column with the new syntax (if
> applicable). It's OK to know if something was removed/deprecated, but even
> better what to use as an alternative (same counts for Javadoc).
>

Can you open an issue for this? It's important to improve the migration
path and make it complete.


> Raymond
>
>
>
>
>
> On Fri, Nov 3, 2023 at 9:14 AM Claus Ibsen  wrote:
>
> > Hi
> >
> > Which Camel version, and have you tried with latest releases.
> >
> > On Thu, Nov 2, 2023 at 9:00 PM ski n  wrote:
> >
> > > I have a route where I want to unzip zipfile (containing 1 or more
> > files).
> > > This is the route:
> > >
> > > ZipFileDataFormat zipFile = new ZipFileDataFormat();
> > > zipFile.setUsingIterator(true);
> > >
> > >
> > >
> >
> from("file:src/test/resources/org/apache/camel/dataformat/zipfile/?delay=1000=true")
> > > .unmarshal(zipFile)
> > > .split(bodyAs(Iterator.class)).streaming()
> > > .process(new UnZippedMessageProcessor())
> > > .end();
> > >
> > > When I tested this locally on my Windows machine everything goes well,
> > > but when I pack in into a container (Alpine)
> > >
> > > and run it on a server (Ubuntu) I get the following error:
> > >
> > > org.apache.camel.StreamCacheException: Error during type conversion
> > > from type: org.apache.camel.dataformat.zipfile.ZipInputStreamWrapper
> > >  to the required type: org.apache.camel.StreamCache with value
> > > org.apache.camel.dataformat.zipfile.ZipInputStreamWrapper@10538c67
> > > due to org.apache.camel.TypeConversionException: Error during type
> > > conversion from type:
> > > org.apache.camel.dataformat.zipfile.ZipInputStreamWrapper
> > >  to the required type: org.apache.camel.StreamCache with value
> > > org.apache.camel.dataformat.zipfile.ZipInputStreamWrapper@10538c67 due
> > > to java.io.IOException: Stream closed
> > >
> > > Based on the error message I'm unsure, is this really a conversion
> > > error or more a permission problem to the spooldirectory or is this
> > > something else?
> > >
> > > Raymond
> > >
> >
> >
> > --
> > Claus Ibsen
> > -
> > @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
>

Re: Camel SMPP component does not allow to set interface version?

[Andrea Cosentino]

As far as I see in the codebase there is no usage of InterfaceVersion
class.
You can open an issue on JIRA so we could investigate.
Thanks

Il giorno lun 30 ott 2023 alle ore 10:48 Bruno Riemenschneider <
bruno.riemenschnei...@bvu.de> ha scritto:

> Hi,
>
> I have used Camel to implement an SMS service, and the SMSC provider
> wants us to use SMPP interface version v5.0. The underlying library
> jSMPP that is used by the Camel component supports interface versions
> 3.3, 3.4, and 5.0 - however, there is no way to set this in Camel.
>
> Did I overlook something? I read that Camel uses jSMPP and jSMPP
> supports v5.0, so I went ahead and implemented - no restrictions are
> mentioned on the side of Camel. This now turns out to be a problem, as
> it seems Camel just uses v3.4. Does someone have information on this issue?
>
> Best
> Bruno
>
>
>

[RESULT][VOTE] Release Apache Camel Kamelets 4.1.0

[Andrea Cosentino]

Hello all,

The vote passes with the following result:

5 +1 binding votes: Andrea Cosentino, Otavio Rodolfo Piske, Zineb Bendhiba,
Babak Vahdat

2 +1 non-binding votes: Gaelle Fournier and Christoph Deppisch

I'll go ahead with the process.

Thanks to all the voters.

Cheers.

Re: [VOTE] Release Apache Camel Kamelets 4.1.0

[Andrea Cosentino]

Thanks all,

This vote passes.

I'll go ahead with the process.

Il giorno ven 27 ott 2023 alle ore 11:20 Babak Vahdat
 ha scritto:

> +1 (binding)
>
>
> Thanks Andrea!
>
> ---
> Babak
>
> > On 23 Oct 2023, at 10:50, Andrea Cosentino  wrote:
> >
> > Hello all,
> >
> > This is a vote for releasing camel-kamelets 4.1.0
> >
> > This release will support the 4.1.0 release of Apache Camel.
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.1.0
> > Kamelets staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1629
> > Kamelets Tag:
> > https://github.com/apache/camel-kamelets/releases/tag/v4.1.0
> >
> > Please cast your vote.
> >
> > [ ] +1 Release camel-kamelets 4.1.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Here's my +1.
> >
> > Thanks,
> > Andrea Cosentino
>
>

[VOTE] Release Apache Camel Kamelets 4.1.0

[Andrea Cosentino]

Hello all,

This is a vote for releasing camel-kamelets 4.1.0

This release will support the 4.1.0 release of Apache Camel.

Kamelets release files:
https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.1.0
Kamelets staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1629
Kamelets Tag:
https://github.com/apache/camel-kamelets/releases/tag/v4.1.0

Please cast your vote.

[ ] +1 Release camel-kamelets 4.1.0
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Here's my +1.

Thanks,
Andrea Cosentino

Re: Kafka client default values out of sync to the origin one

[Andrea Cosentino]

Yes. We did

Il mar 10 ott 2023, 21:25 Claus Ibsen  ha scritto:

> Hi
>
> Did we change those default settings?
>
> On Tue, Sep 26, 2023 at 5:21 PM Andrea Cosentino 
> wrote:
>
> > Yes, it is possible.
> >
> > Can you raise an issue where you list the out of sync options?
> >
> > https://issues.apache.org/jira/projects/CAMEL/issues
> >
> > Thank you
> >
> > Il mar 26 set 2023, 17:09 Esslinger, Michael (BARMER) <
> > michael.esslin...@barmer.de> ha scritto:
> >
> > > Hi,
> > >
> > > is it possible, that some default values of the Kafka client are set
> from
> > > Camel were out of sync with the origin one?
> > >
> > > For example:
> > >   - session.timeout.ms (
> > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-735%3A+Increase+default+consumer+session+timeout
> > > )
> > >   - request.timeout.ms (
> > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-266%3A+Fix+consumer+indefinite+blocking+behavior
> > > )
> > >
> > > Regards
> > > Michael
> > >
> >
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Re: Camel 4 migration blog post - Feedback welcome

[Andrea Cosentino]

The reason for camel-atlasmap to be removed was the fact Atlasmap was
discontinued.

There were no releases since October.

Il giorno ven 6 ott 2023 alle ore 11:34 Gerald Kallas
 ha scritto:

> Hi folks,
>
> what's the reason that camel-atlasmap has been removed in Camel 4. Is
> there any alternative planned for mapping processors that don't need to be
> coded?
>
> Best
> Gerald
>
> > ski n  hat am 06.10.2023 10:51 CEST
> geschrieben:
> >
> >
> > Sure happy to give feedback. I plan to upgrade from 3.20.x to 4.x.
> >
> > Currently, thus not migrating yet, but planning has started.
> >
> > The things I need to consider:
> >
> > - I first need to finish some stuff to upgrade from 2.x to 3.x (Currently
> > the docs for 2.0 are gone, is the archive to Camel 2.0 documentation
> still
> > available? Like to compare sometimes.
> > - Jakarta stuff in my own code/dependencies.
> > - Jakarta stuff in other libraries (then Camel). For example ActiveMQ
> > Classic (embedded) server doesn't support it yet.
> > - Deprecated components: I use the following components:
> >
> > camel-atlasmap
> > camel-directvm
> > camel-elasticsearch-rest
> > camel-rabbitmq
> > camel-rest-swagger
> > camel-websocket
> > camel-vm
> >
> > So I need to change these dependencies and some code here
> >
> > - I use extendedCamelContext a lot, so need to check the API changes out.
> > For example use the PluginHelper instead of the extendedCamelContext
> > - Update SLFJ to version 2.0
> >
> > Will let you know if I'm running into any issues.
> >
> > I'm planning to use OpenRewrite to update to Spring Boot 3/Jakarta (
> > https://docs.openrewrite.org/recipes/java/spring/boot3). If there was a
> > recipe to move to Camel 4 then it would be probably easier to do the
> > migration.
> >
> > Raymond
> >
> >
> > On Fri, Oct 6, 2023 at 9:49 AM Claus Ibsen 
> wrote:
> >
> > > Hi
> > >
> > > If you have been migrating to Camel 4 already, then any feedback is
> > > welcome.
> > >
> > > You can comment in the PR, or post here in the mailing list
> > > https://github.com/apache/camel-website/pull/1071
> > >
> > >
> > >
> > >
> > > --
> > > Claus Ibsen
> > > -
> > > @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
> > >
>

Re: Behavior of aggregation and file path in Camel Kafka Connector

[Andrea Cosentino]

Hello,

The aggregation works in the following way, if you have the message 1  and
2 and an aggregation size of 2, you'll get a file with 1,2 as content and
an exchange Id as file name if you don't specify the header, otherwise it
should be the last header you sent as file name.

It doesn't distinguish between file name, because it's a general camel
concept and is not related to the specific component.

If you have to do something like that, probably it would be better to use
plain camel, so you should be able to cover your case.

Cheers.

Il giorno ven 6 ott 2023 alle ore 08:57 Satoshi Yamada <
satoshi.yamada@gmail.com> ha scritto:

> Hi community,
>
> I'm using camel-azure-storage-blob-sink-kafka-connector from k8s, and let
> kafkaconnect upload the logs (Kafka messages) to Azure Blob.
> I've used message header to specify the file path, and also use aggregation
> options in Camel as follows
>
> camel.aggregation.size: 2
> camel.aggregation.timeout: 360
>
> I've expected Camel Kafka Connector to aggregate the logs per file
> name, which is specified in the message header. For example, if we
> produce 6 messages with the following messages headers in order
>
> Message 1: CamelHeader.file=A
> Message 2: CamelHeader.file=B
> Message 3: CamelHeader.file=C
> Message 4: CamelHeader.file=A
> Message 5: CamelHeader.file=B
> Message 6: CamelHeader.file=C
>
> Then, I expected files named "A" containing message 1 and 4, "B"
> containing message 2 and 5, and "C" containing message 3 and 6 will be
> uploaded to Azure, but actually it doesn't and it seems a file
> containing message 1 and 2 are there with file name "A" or "B", a file
> with message 3 and 4 with file name "C" or "A", and a file with
> message 5 and 6 with file name "B" or "C" are there.
>
> I want to confirm with the community if this is the expected behavior
> in Camel Kafka Connector.
> I'm using camel-azure-storage-blob-sink-kafka-connector-3.18.2 and use
> `uploadBlockBlob` for `CamelHeader.CamelAzureStorageBlobOperation`.
>
> Thanks in advance,
> Satoshi
>

Re: [VOTE] Release Apache Camel Kamelets 4.0.1

[Andrea Cosentino]

Thanks all,

The vote passes.

I'll go ahead.

Il giorno gio 28 set 2023 alle ore 16:05 Marat Gubaidullin <
marat.gubaidul...@gmail.com> ha scritto:

> +1 (non-binding)
>
> Thanks!
> Marat
>
> On Tue, Sep 26, 2023 at 4:14 AM Andrea Cosentino 
> wrote:
>
> > Hello all,
> >
> > This is a vote for releasing camel-kamelets 4.0.1
> >
> > This release will support the 4.0.1 release of Apache Camel.
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.1
> > Kamelets staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1616
> > Kamelets Tag:
> > https://github.com/apache/camel-kamelets/releases/tag/v4.0.1
> >
> > Please cast your vote.
> >
> > [ ] +1 Release camel-kamelets 4.0.1
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Here's my +1.
> >
> > Thanks,
> > Andrea Cosentino
> >
>

[RESULT][VOTE] Release Apache Camel Kamelets 4.0.1

[Andrea Cosentino]

Thanks to all voters,

This vote passes with the following result:

7 +1 binding votes: Andrea Cosentino, Claus Ibsen, Otavio Rodolfo Piske,
Pasquale Congiusti, Nicolas Filotto, Jean-Baptiste Onofrè, Babak Vahdat

3 +1 non-binding votes: Christoph Deppisch, Gaelle Fournier and Marat
Gubaidullin

Thanks again.

I'll go ahead with the workflow.

Re: Kafka client default values out of sync to the origin one

[Andrea Cosentino]

Yes, it is possible.

Can you raise an issue where you list the out of sync options?

https://issues.apache.org/jira/projects/CAMEL/issues

Thank you

Il mar 26 set 2023, 17:09 Esslinger, Michael (BARMER) <
michael.esslin...@barmer.de> ha scritto:

> Hi,
>
> is it possible, that some default values of the Kafka client are set from
> Camel were out of sync with the origin one?
>
> For example:
>   - session.timeout.ms (
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-735%3A+Increase+default+consumer+session+timeout
> )
>   - request.timeout.ms (
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-266%3A+Fix+consumer+indefinite+blocking+behavior
> )
>
> Regards
> Michael
>

Re: [VOTE] Release Apache Camel Kamelets 4.0.1

[Andrea Cosentino]

Just to avoid confusion, the vote from Christoph is non-binding, since he's
not yet in the PMC.

Thanks.

Il giorno mar 26 set 2023 alle ore 14:55 Christoph Deppisch
 ha scritto:

> +1 (binding)
>
> Andrea Cosentino  schrieb am Di., 26. Sept. 2023,
> 10:14:
>
> > Hello all,
> >
> > This is a vote for releasing camel-kamelets 4.0.1
> >
> > This release will support the 4.0.1 release of Apache Camel.
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.1
> > Kamelets staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1616
> > Kamelets Tag:
> > https://github.com/apache/camel-kamelets/releases/tag/v4.0.1
> >
> > Please cast your vote.
> >
> > [ ] +1 Release camel-kamelets 4.0.1
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Here's my +1.
> >
> > Thanks,
> > Andrea Cosentino
> >
>

[VOTE] Release Apache Camel Kamelets 4.0.1

[Andrea Cosentino]

Hello all,

This is a vote for releasing camel-kamelets 4.0.1

This release will support the 4.0.1 release of Apache Camel.

Kamelets release files:
https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.1
Kamelets staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1616
Kamelets Tag:
https://github.com/apache/camel-kamelets/releases/tag/v4.0.1

Please cast your vote.

[ ] +1 Release camel-kamelets 4.0.1
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Here's my +1.

Thanks,
Andrea Cosentino

Re: NoopHostnameVerifier seems to not working any longer - Camel 3.20.2

[Andrea Cosentino]

Can you open an issue so we won't forget? Thanks

Il mar 12 set 2023, 19:55 Gerald Kallas  ha
scritto:

> Folks,
>
> we had a code (XML DSL) that was already working to skip SSL hostname
> validation like
>
>  class="org.apache.http.conn.ssl.NoopHostnameVerifier"/>
> ...
>  >
>
> It's not working anymore, getting
>
> javax.net.ssl.SSLHandshakeException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target
>
> I tried also
>
>  >
>
> same error.
>
> The underlying Java (within a Docker containe) is
>
> openjdk version "11.0.11" 2021-04-20
> OpenJDK Runtime Environment AdoptOpenJDK-11.0.11+9 (build 11.0.11+9)
> OpenJDK 64-Bit Server VM AdoptOpenJDK-11.0.11+9 (build 11.0.11+9, mixed
> mode)
>
> Any ideas?
>
> Best
> Gerald

[RESULT][VOTE] Release Apache Camel Kamelets 4.0.0

[Andrea Cosentino]

Hello all,

The vote passed with the following result:

5 +1 binding votes: Andrea Cosentino, Pasquale Congiusti, Zineb Bendhiba,
Christoph Deppisch and Otavio Rodolfo Piske

1 +1 non-binding vote: Claudio Miranda

Thanks all for the votes.

Re: [VOTE] Release Apache Camel Kamelets 4.0.0

[Andrea Cosentino]

Thanks all.

The vote passed.

I'll go ahead with the release.

Il giorno mer 6 set 2023 alle ore 16:05 Claudio Miranda <
clau...@claudius.com.br> ha scritto:

> +1 non binding
>
>
>
> --
>   Claudio Miranda
>
> clau...@claudius.com.br
> http://www.claudius.com.br
>

[VOTE] Release Apache Camel Kamelets 4.0.0

[Andrea Cosentino]

Hello all,

This is a vote for releasing camel-kamelets 4.0.0

This release will support the first 4.0.0 stable release of Apache Camel.

Kamelets release files:
https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.0
Kamelets staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1607
Kamelets Tag:
https://github.com/apache/camel-kamelets/releases/tag/v4.0.0

Please cast your vote.

[ ] +1 Release camel-kamelets 4.0.0
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Here's my +1.

Thanks,
Andrea Cosentino

Re: AWS S3 Storage Service gets 403 Forbidden

[Andrea Cosentino]

Have a look at
https://github.com/apache/camel-examples/tree/main/examples/main

Il giorno gio 24 ago 2023 alle ore 22:38 Ross Woolf  ha
scritto:

> I've never used an external file for the properties.  Can you point me
> in the right direction?
>
> On Thu, Aug 24, 2023 at 2:28 PM Andrea Cosentino 
> wrote:
> >
> > When this happen I usually externalize the properties in a file or I use
> > the camel main properties to inject parameters..
> >
> > Il gio 24 ago 2023, 22:23 Ross Woolf  ha scritto:
> >
> > > 
> > >   > >
> uri="aws2-s3://bucket-ses-s3-receiving/?region=us-east-1accessKey=RAW(MY_ACCESS_KEY)secretKey=RAW(MY_SECRET_KEY_WITH+)"
> > > />
> > >  
> > > 
> > >
> > > On Thu, Aug 24, 2023 at 2:15 PM Andrea Cosentino 
> > > wrote:
> > > >
> > > > Can you show the route now that you're using RAW?
> > > >
> > > > Il gio 24 ago 2023, 22:00 Ross Woolf  ha
> scritto:
> > > >
> > > > > My secret key has a +.  I used RAW( ) on both the access and secret
> > > > > keys, but the result is the same.  I can set a breakpoint and view
> the
> > > > > aws configuration object and both keys make it to the configuration
> > > > > object as they should be.  But it fails when creating the
> > > > > HeadBucketRequet object.
> > > > >
> > > > >
> > > > > On Thu, Aug 24, 2023 at 1:23 PM Andrea Cosentino <
> anco...@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > > Do you have particular characters in your key? Prefix the access
> key
> > > > > value
> > > > > > with RAW() and the secret in the same way.
> > > > > >
> > > > > > Il gio 24 ago 2023, 21:13 Ross Woolf  ha
> > > scritto:
> > > > > >
> > > > > > > I am trying to use the AWS S3 Storage Service component.  I
> have
> > > been
> > > > > > > unsuccessful at getting access to the S3 bucket via the
> > > component.  I
> > > > > > > always get a 403 Forbidden error.  I am using Camel 3.21.0,
> and I
> > > have
> > > > > > > tried both Java 11 and 17 with the same results.   I can
> > > successfully
> > > > > use
> > > > > > > the AWS CLI to get files from the S3 bucket using the API and
> the
> > > > > > > access/secret keys, but using the same keys with the camel S3
> > > component
> > > > > > > always fails.
> > > > > > >
> > > > > > > The following is my camel route I am trying:
> > > > > > > 
> > > > > > > > > > > > >
> > > > > > >
> > > > >
> > >
> uri="aws2-s3://bucket-ses-s3-receiving/?region=us-east-1accessKey=MY_ACCESS_KEYsecretKey=MY_SECRET_KEY"
> > > > > > > />
> > > > > > >
> > > > > > > 
> > > > > > >
> > > > > > > The following is the relevant portion of the exception:
> > > > > > > Caused by:
> software.amazon.awssdk.services.s3.model.S3Exception:
> > > null
> > > > > > > (Service: S3, Status Code: 403, Request ID: TA07HFNJRF6D1FGW,
> > > Extended
> > > > > > > Request ID:
> > > > > > >
> > > > > > >
> > > > >
> > >
> Oxv5vee3vzHsWe5LAvbPuu+/kzI/OKf+5pDilV4hxwFas0M8XgYR0EeuZQwrU0KRT9CN/OUlPrA=)
> > > > > > > at
> > > > > > >
> > > > > > >
> > > > >
> > >
> software.amazon.awssdk.protocols.xml.internal.unmarshall.AwsXmlPredicatedResponseHandler.handleErrorResponse(AwsXmlPredicatedResponseHandler.java:156)
> > > > > > > at
> > > > > > >
> > > > > > >
> > > > >
> > >
> software.amazon.awssdk.protocols.xml.internal.unmarshall.AwsXmlPredicatedResponseHandler.handleResponse(AwsXmlPredicatedResponseHandler.java:108)
> > > > > > > ...
> > > > > > >  at
> > > > > > >
> > > > > > >
> > > > >
> > >
> software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.execute(BaseSyncClientHandler.java:76)
> > > > > > > at
> > > > > > >
> > > > > > >
> > > > >
> > >
> software.amazon.awssdk.core.client.handler.SdkSyncClientHandler.execute(SdkSyncClientHandler.java:45)
> > > > > > > at
> > > > > > >
> > > > > > >
> > > > >
> > >
> software.amazon.awssdk.awscore.client.handler.AwsSyncClientHandler.execute(AwsSyncClientHandler.java:56)
> > > > > > > at
> > > > > > >
> > > > > > >
> > > > >
> > >
> software.amazon.awssdk.services.s3.DefaultS3Client.headBucket(DefaultS3Client.java:5249)
> > > > > > > at
> > > > > > >
> > > > > > >
> > > > >
> > >
> org.apache.camel.component.aws2.s3.AWS2S3Endpoint.doStart(AWS2S3Endpoint.java:102)
> > > > > > > at
> > > > >
> > >
> org.apache.camel.support.service.BaseService.start(BaseService.java:119)
> > > > > > > at
> > > > > > >
> > > > > > >
> > > > >
> > >
> org.apache.camel.support.service.ServiceHelper.startService(ServiceHelper.java:113)
> > > > > > > at
> > > > > > >
> > > > >
> > >
> org.apache.camel.impl.engine.RouteService.doWarmUp(RouteService.java:184)
> > > > > > > at
> > > > >
> org.apache.camel.impl.engine.RouteService.warmUp(RouteService.java:121)
> > > > > > > ... 53 more
> > > > > > >
> > > > > > > Is there more I need to provide in the aws2-s3 configuration?
> Or
> > > is
> > > > > there
> > > > > > > a bug with the way Camel implements the API, or an issue with
> the
> > > > > awssdk
> > > > > > > API itself?  I'm stuck and don't know how to figure this out.
> > > > > > > Any help is appreciated.
> > > > > > >
> > > > >
> > >
>

Re: AWS S3 Storage Service gets 403 Forbidden

[Andrea Cosentino]

When this happen I usually externalize the properties in a file or I use
the camel main properties to inject parameters..

Il gio 24 ago 2023, 22:23 Ross Woolf  ha scritto:

> 
>   uri="aws2-s3://bucket-ses-s3-receiving/?region=us-east-1accessKey=RAW(MY_ACCESS_KEY)secretKey=RAW(MY_SECRET_KEY_WITH+)"
> />
>  
> 
>
> On Thu, Aug 24, 2023 at 2:15 PM Andrea Cosentino 
> wrote:
> >
> > Can you show the route now that you're using RAW?
> >
> > Il gio 24 ago 2023, 22:00 Ross Woolf  ha scritto:
> >
> > > My secret key has a +.  I used RAW( ) on both the access and secret
> > > keys, but the result is the same.  I can set a breakpoint and view the
> > > aws configuration object and both keys make it to the configuration
> > > object as they should be.  But it fails when creating the
> > > HeadBucketRequet object.
> > >
> > >
> > > On Thu, Aug 24, 2023 at 1:23 PM Andrea Cosentino 
> > > wrote:
> > > >
> > > > Do you have particular characters in your key? Prefix the access key
> > > value
> > > > with RAW() and the secret in the same way.
> > > >
> > > > Il gio 24 ago 2023, 21:13 Ross Woolf  ha
> scritto:
> > > >
> > > > > I am trying to use the AWS S3 Storage Service component.  I have
> been
> > > > > unsuccessful at getting access to the S3 bucket via the
> component.  I
> > > > > always get a 403 Forbidden error.  I am using Camel 3.21.0, and I
> have
> > > > > tried both Java 11 and 17 with the same results.   I can
> successfully
> > > use
> > > > > the AWS CLI to get files from the S3 bucket using the API and the
> > > > > access/secret keys, but using the same keys with the camel S3
> component
> > > > > always fails.
> > > > >
> > > > > The following is my camel route I am trying:
> > > > > 
> > > > > > > > >
> > > > >
> > >
> uri="aws2-s3://bucket-ses-s3-receiving/?region=us-east-1accessKey=MY_ACCESS_KEYsecretKey=MY_SECRET_KEY"
> > > > > />
> > > > >
> > > > > 
> > > > >
> > > > > The following is the relevant portion of the exception:
> > > > > Caused by: software.amazon.awssdk.services.s3.model.S3Exception:
> null
> > > > > (Service: S3, Status Code: 403, Request ID: TA07HFNJRF6D1FGW,
> Extended
> > > > > Request ID:
> > > > >
> > > > >
> > >
> Oxv5vee3vzHsWe5LAvbPuu+/kzI/OKf+5pDilV4hxwFas0M8XgYR0EeuZQwrU0KRT9CN/OUlPrA=)
> > > > > at
> > > > >
> > > > >
> > >
> software.amazon.awssdk.protocols.xml.internal.unmarshall.AwsXmlPredicatedResponseHandler.handleErrorResponse(AwsXmlPredicatedResponseHandler.java:156)
> > > > > at
> > > > >
> > > > >
> > >
> software.amazon.awssdk.protocols.xml.internal.unmarshall.AwsXmlPredicatedResponseHandler.handleResponse(AwsXmlPredicatedResponseHandler.java:108)
> > > > > ...
> > > > >  at
> > > > >
> > > > >
> > >
> software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.execute(BaseSyncClientHandler.java:76)
> > > > > at
> > > > >
> > > > >
> > >
> software.amazon.awssdk.core.client.handler.SdkSyncClientHandler.execute(SdkSyncClientHandler.java:45)
> > > > > at
> > > > >
> > > > >
> > >
> software.amazon.awssdk.awscore.client.handler.AwsSyncClientHandler.execute(AwsSyncClientHandler.java:56)
> > > > > at
> > > > >
> > > > >
> > >
> software.amazon.awssdk.services.s3.DefaultS3Client.headBucket(DefaultS3Client.java:5249)
> > > > > at
> > > > >
> > > > >
> > >
> org.apache.camel.component.aws2.s3.AWS2S3Endpoint.doStart(AWS2S3Endpoint.java:102)
> > > > > at
> > >
> org.apache.camel.support.service.BaseService.start(BaseService.java:119)
> > > > > at
> > > > >
> > > > >
> > >
> org.apache.camel.support.service.ServiceHelper.startService(ServiceHelper.java:113)
> > > > > at
> > > > >
> > >
> org.apache.camel.impl.engine.RouteService.doWarmUp(RouteService.java:184)
> > > > > at
> > > org.apache.camel.impl.engine.RouteService.warmUp(RouteService.java:121)
> > > > > ... 53 more
> > > > >
> > > > > Is there more I need to provide in the aws2-s3 configuration?  Or
> is
> > > there
> > > > > a bug with the way Camel implements the API, or an issue with the
> > > awssdk
> > > > > API itself?  I'm stuck and don't know how to figure this out.
> > > > > Any help is appreciated.
> > > > >
> > >
>

Re: AWS S3 Storage Service gets 403 Forbidden

[Andrea Cosentino]

Can you show the route now that you're using RAW?

Il gio 24 ago 2023, 22:00 Ross Woolf  ha scritto:

> My secret key has a +.  I used RAW( ) on both the access and secret
> keys, but the result is the same.  I can set a breakpoint and view the
> aws configuration object and both keys make it to the configuration
> object as they should be.  But it fails when creating the
> HeadBucketRequet object.
>
>
> On Thu, Aug 24, 2023 at 1:23 PM Andrea Cosentino 
> wrote:
> >
> > Do you have particular characters in your key? Prefix the access key
> value
> > with RAW() and the secret in the same way.
> >
> > Il gio 24 ago 2023, 21:13 Ross Woolf  ha scritto:
> >
> > > I am trying to use the AWS S3 Storage Service component.  I have been
> > > unsuccessful at getting access to the S3 bucket via the component.  I
> > > always get a 403 Forbidden error.  I am using Camel 3.21.0, and I have
> > > tried both Java 11 and 17 with the same results.   I can successfully
> use
> > > the AWS CLI to get files from the S3 bucket using the API and the
> > > access/secret keys, but using the same keys with the camel S3 component
> > > always fails.
> > >
> > > The following is my camel route I am trying:
> > > 
> > > > >
> > >
> uri="aws2-s3://bucket-ses-s3-receiving/?region=us-east-1accessKey=MY_ACCESS_KEYsecretKey=MY_SECRET_KEY"
> > > />
> > >
> > > 
> > >
> > > The following is the relevant portion of the exception:
> > > Caused by: software.amazon.awssdk.services.s3.model.S3Exception: null
> > > (Service: S3, Status Code: 403, Request ID: TA07HFNJRF6D1FGW, Extended
> > > Request ID:
> > >
> > >
> Oxv5vee3vzHsWe5LAvbPuu+/kzI/OKf+5pDilV4hxwFas0M8XgYR0EeuZQwrU0KRT9CN/OUlPrA=)
> > > at
> > >
> > >
> software.amazon.awssdk.protocols.xml.internal.unmarshall.AwsXmlPredicatedResponseHandler.handleErrorResponse(AwsXmlPredicatedResponseHandler.java:156)
> > > at
> > >
> > >
> software.amazon.awssdk.protocols.xml.internal.unmarshall.AwsXmlPredicatedResponseHandler.handleResponse(AwsXmlPredicatedResponseHandler.java:108)
> > > ...
> > >  at
> > >
> > >
> software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.execute(BaseSyncClientHandler.java:76)
> > > at
> > >
> > >
> software.amazon.awssdk.core.client.handler.SdkSyncClientHandler.execute(SdkSyncClientHandler.java:45)
> > > at
> > >
> > >
> software.amazon.awssdk.awscore.client.handler.AwsSyncClientHandler.execute(AwsSyncClientHandler.java:56)
> > > at
> > >
> > >
> software.amazon.awssdk.services.s3.DefaultS3Client.headBucket(DefaultS3Client.java:5249)
> > > at
> > >
> > >
> org.apache.camel.component.aws2.s3.AWS2S3Endpoint.doStart(AWS2S3Endpoint.java:102)
> > > at
> org.apache.camel.support.service.BaseService.start(BaseService.java:119)
> > > at
> > >
> > >
> org.apache.camel.support.service.ServiceHelper.startService(ServiceHelper.java:113)
> > > at
> > >
> org.apache.camel.impl.engine.RouteService.doWarmUp(RouteService.java:184)
> > > at
> org.apache.camel.impl.engine.RouteService.warmUp(RouteService.java:121)
> > > ... 53 more
> > >
> > > Is there more I need to provide in the aws2-s3 configuration?  Or is
> there
> > > a bug with the way Camel implements the API, or an issue with the
> awssdk
> > > API itself?  I'm stuck and don't know how to figure this out.
> > > Any help is appreciated.
> > >
>

Re: AWS S3 Storage Service gets 403 Forbidden

[Andrea Cosentino]

Do you have particular characters in your key? Prefix the access key value
with RAW() and the secret in the same way.

Il gio 24 ago 2023, 21:13 Ross Woolf  ha scritto:

> I am trying to use the AWS S3 Storage Service component.  I have been
> unsuccessful at getting access to the S3 bucket via the component.  I
> always get a 403 Forbidden error.  I am using Camel 3.21.0, and I have
> tried both Java 11 and 17 with the same results.   I can successfully use
> the AWS CLI to get files from the S3 bucket using the API and the
> access/secret keys, but using the same keys with the camel S3 component
> always fails.
>
> The following is my camel route I am trying:
> 
>
> uri="aws2-s3://bucket-ses-s3-receiving/?region=us-east-1accessKey=MY_ACCESS_KEYsecretKey=MY_SECRET_KEY"
> />
>
> 
>
> The following is the relevant portion of the exception:
> Caused by: software.amazon.awssdk.services.s3.model.S3Exception: null
> (Service: S3, Status Code: 403, Request ID: TA07HFNJRF6D1FGW, Extended
> Request ID:
>
> Oxv5vee3vzHsWe5LAvbPuu+/kzI/OKf+5pDilV4hxwFas0M8XgYR0EeuZQwrU0KRT9CN/OUlPrA=)
> at
>
> software.amazon.awssdk.protocols.xml.internal.unmarshall.AwsXmlPredicatedResponseHandler.handleErrorResponse(AwsXmlPredicatedResponseHandler.java:156)
> at
>
> software.amazon.awssdk.protocols.xml.internal.unmarshall.AwsXmlPredicatedResponseHandler.handleResponse(AwsXmlPredicatedResponseHandler.java:108)
> ...
>  at
>
> software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.execute(BaseSyncClientHandler.java:76)
> at
>
> software.amazon.awssdk.core.client.handler.SdkSyncClientHandler.execute(SdkSyncClientHandler.java:45)
> at
>
> software.amazon.awssdk.awscore.client.handler.AwsSyncClientHandler.execute(AwsSyncClientHandler.java:56)
> at
>
> software.amazon.awssdk.services.s3.DefaultS3Client.headBucket(DefaultS3Client.java:5249)
> at
>
> org.apache.camel.component.aws2.s3.AWS2S3Endpoint.doStart(AWS2S3Endpoint.java:102)
> at org.apache.camel.support.service.BaseService.start(BaseService.java:119)
> at
>
> org.apache.camel.support.service.ServiceHelper.startService(ServiceHelper.java:113)
> at
> org.apache.camel.impl.engine.RouteService.doWarmUp(RouteService.java:184)
> at org.apache.camel.impl.engine.RouteService.warmUp(RouteService.java:121)
> ... 53 more
>
> Is there more I need to provide in the aws2-s3 configuration?  Or is there
> a bug with the way Camel implements the API, or an issue with the awssdk
> API itself?  I'm stuck and don't know how to figure this out.
> Any help is appreciated.
>

Re: ZeroMQ component

[Andrea Cosentino]

Until the license is not compatible with ASF license, we can't take into
account to move it in the Apache Camel repository.

Il mar 1 ago 2023, 17:40 Nicolas Filotto  ha scritto:

> Hi,
>
> AFAIK the components in camel-extra have been moved there because their
> license is not compatible with an Apache License which is a requirement to
> be in the camel repository.
>
> In the case of ZeroMQ, it seems that the license is a Mozilla Public
> License version 2.0 which is more restrictive than an Apache License which
> is why it is not part of the Camel repository.
>
> Regards,
> Nicolas
> 
> From: Mark Webb 
> Sent: Tuesday, August 1, 2023 17:20
> To: users@camel.apache.org 
> Subject: ZeroMQ component
>
> I know that the camel-zeromq component exists in the camel-extra repo, is
> there any chance it could once again find its way into the current
> "official" trunk?  I'd even be willing to lead and support the effort.
>
> I'd prefer to make it based off of JeroMQ and not the Akka version.
>
> Would this be possible?
>
> - Mark
>
> As a recipient of an email from the Talend Group, your personal data will
> be processed by our systems. Please see our Privacy Notice <
> https://www.talend.com/privacy-policy/> for more information about our
> collection and use of your personal information, our security practices,
> and your data protection rights, including any rights you may have to
> object to automated-decision making or profiling we use to analyze support
> or marketing related communications. To manage or discontinue promotional
> communications, use the communication preferences portal<
> https://info.talend.com/emailpreferencesen.html>. To exercise your data
> protection rights, use the privacy request form<
> https://talend.my.onetrust.com/webform/ef906c5a-de41-4ea0-ba73-96c079cdd15a/b191c71d-f3cb-4a42-9815-0c3ca021704cl>.
> Contact us here  or by mail to either of
> our co-headquarters: Talend, Inc.: 400 South El Camino Real, Ste 1400, San
> Mateo, CA 94402; Talend SAS: 5/7 rue Salomon De Rothschild, 92150 Suresnes,
> France
>

Re: Counterintuitive behavior in S3 producer and consumer

[Andrea Cosentino]

By the way I'll have another look. I don't remember this behavior, at least
not with bucket2 explicit in the URI

Il ven 14 lug 2023, 23:42 Andrea Cosentino  ha scritto:

> This is a known behavior.
>
> You need to override the header explicitly.
>
> Il ven 14 lug 2023, 23:05 Anthony Wu  ha scritto:
>
>> Hi folks,
>>
>> I noticed something odd in Camel 3.14.x where, if you have a
>> from("aws2-s3://bucket1") and a to("aws2-s3://bucket2") - basically a
>> download, some processing in the middle, and an upload of a different file
>> and a different bucket (where the KEY header is set to tell Camel which
>> file to use), bucket1 is apparently sticky and only overriding the
>> BUCKET_NAME header before processing the upload works.
>>
>> Is this known behavior with the way Camel processes message bodies/headers
>> for the S3 component in particular? I would have expected the explicit
>> bucket name in the Camel URI to override the settings, but apparently it
>> doesn't take. I'm wondering if this qualifies as a bug or perhaps
>> something
>> to point out in documentation.
>>
>> Happy to attach a test if folks are having trouble reproducing.
>>
>> Anthony
>>
>

Re: Counterintuitive behavior in S3 producer and consumer

[Andrea Cosentino]

This is a known behavior.

You need to override the header explicitly.

Il ven 14 lug 2023, 23:05 Anthony Wu  ha scritto:

> Hi folks,
>
> I noticed something odd in Camel 3.14.x where, if you have a
> from("aws2-s3://bucket1") and a to("aws2-s3://bucket2") - basically a
> download, some processing in the middle, and an upload of a different file
> and a different bucket (where the KEY header is set to tell Camel which
> file to use), bucket1 is apparently sticky and only overriding the
> BUCKET_NAME header before processing the upload works.
>
> Is this known behavior with the way Camel processes message bodies/headers
> for the S3 component in particular? I would have expected the explicit
> bucket name in the Camel URI to override the settings, but apparently it
> doesn't take. I'm wondering if this qualifies as a bug or perhaps something
> to point out in documentation.
>
> Happy to attach a test if folks are having trouble reproducing.
>
> Anthony
>

Re: [VOTE] Release Apache Camel Kamelets 4.0.0-RC1

[Andrea Cosentino]

Hello,

This vote passes.

I'll go ahead with the process.

Thanks

Il giorno ven 7 lug 2023 alle ore 06:04 Jean-Baptiste Onofré <
j...@nanthrax.net> ha scritto:

> +1 (binding)
>
> Regards
> JB
>
> On Wed, Jul 5, 2023 at 12:23 PM Andrea Cosentino 
> wrote:
> >
> > Hello all,
> >
> > This is a vote for releasing camel-kamelets 4.0.0-RC1
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.0-RC1
> > Kamelets staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1589
> > Kamelets Tag:
> > https://github.com/apache/camel-kamelets/releases/tag/v4.0.0-RC1
> >
> > Please cast your vote.
> >
> > [ ] +1 Release camel-kamelets 4.0.0-RC1
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Here's my +1.
> >
> > Thanks,
> > Andrea Cosentino
>

[RESULT][VOTE] Release Apache Camel Kamelets 4.0.0-RC1

[Andrea Cosentino]

Hello all,

The vote passed with the following result:

5 +1 binding votes: Andrea Cosentino, Claus Ibsen, Pasquale Congiusti,
Zineb Bendhiba and Jean-Baptiste Onofrè

I'll go ahead with the process.

Thanks.

CVE-2023-34442: Apache Camel JIRA: Temporary file information disclosure in Camel-Jira

[Andrea Cosentino]

Severity: low

Affected versions:

- Apache Camel JIRA 3.x through <=3.14.8
- Apache Camel JIRA 3.18.x through <=3.18.7
- Apache Camel JIRA 3.20.x through <= 3.20.5
- Apache Camel JIRA 4.x through <= 4.0.0-M3

Description:

Exposure of Sensitive Information to an Unauthorized Actor vulnerability in
Apache Software Foundation Apache Camel.This issue affects Apache Camel:
from 3.X through <=3.14.8, from 3.18.X through <=3.18.7, from 3.20.X
through <= 3.20.5, from 4.X through <= 4.0.0-M3.

Users should upgrade to 3.14.9, 3.18.8, 3.20.6 or 3.21.0 and for users on
Camel 4.x update to 4.0.0-M1

This issue is being tracked as CAMEL-19421

Credit:

This issue was discovered by Jonathan Leitschuh of the Open Source Security
Foundation: Project Alpha-Omega (reporter)

References:

https://camel.apache.org/
https://www.cve.org/CVERecord?id=CVE-2023-34442
https://issues.apache.org/jira/browse/CAMEL-19421
https://camel.apache.org/security/CVE-2023-34442.html

[VOTE] Release Apache Camel Kamelets 4.0.0-RC1

[Andrea Cosentino]

Hello all,

This is a vote for releasing camel-kamelets 4.0.0-RC1

Kamelets release files:
https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.0-RC1
Kamelets staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1589
Kamelets Tag:
https://github.com/apache/camel-kamelets/releases/tag/v4.0.0-RC1

Please cast your vote.

[ ] +1 Release camel-kamelets 4.0.0-RC1
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Here's my +1.

Thanks,
Andrea Cosentino

[RESULT][VOTE] Release Apache Camel Kamelets 3.21.0

[Andrea Cosentino]

Hello all,

The vote passed with the following results:

4 +1 binding votes: Andrea Cosentino, Zineb Bendhiba, Otavio Rodolfo Piske
and Claus Ibsen

1 +1 non-binding vote: Marat Gubaidullin

Thanks to all the voters.

I'll go ahead with the release.

Re: [VOTE] Release Apache Camel Kamelets 3.21.0

[Andrea Cosentino]

Thanks all,

The vote passed and I'll go ahead with the release.

Il giorno lun 3 lug 2023 alle ore 09:20 Claus Ibsen 
ha scritto:

> +1 (binding)
>
>
> On Mon, 3 Jul 2023 at 09.13, Andrea Cosentino  wrote:
>
> > Hello, just a reminder we need another binding vote.
> >
> > Thanks.
> >
> > Il giorno sab 1 lug 2023 alle ore 07:47 Otavio Rodolfo Piske <
> > angusyo...@gmail.com> ha scritto:
> >
> > > +1 (binding)
> > >
> > > Thanks Andrea!
> > >
> > > On Fri, Jun 30, 2023 at 4:01 PM Marat Gubaidullin <
> > > marat.gubaidul...@gmail.com> wrote:
> > >
> > > > +1 (non-binding)
> > > >
> > > > Thanks Andrea
> > > >
> > > > On Fri, Jun 30, 2023 at 9:39 AM Zineb Bendhiba <
> > bendhiba.zi...@gmail.com
> > > >
> > > > wrote:
> > > >
> > > > > +1 (binding)
> > > > >
> > > > > Thanks Andrea
> > > > >
> > > > > Le ven. 30 juin 2023 à 14:40, Andrea Cosentino 
> a
> > > > > écrit :
> > > > >
> > > > > > Hello all,
> > > > > >
> > > > > > This is a vote for releasing camel-kamelets 3.21.0
> > > > > >
> > > > > > Kamelets release files:
> > > > > >
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/3.21.0
> > > > > > Kamelets staging repository:
> > > > > >
> > > https://repository.apache.org/content/repositories/orgapachecamel-1585
> > > > > > Kamelets Tag:
> > > > > > https://github.com/apache/camel-kamelets/releases/tag/v3.21.0
> > > > > >
> > > > > > Please cast your vote.
> > > > > >
> > > > > > [ ] +1 Release camel-kamelets 3.21.0
> > > > > > [ ] -1 Veto the release (provide specific comments)
> > > > > >
> > > > > > The vote is open for at least 72 hours.
> > > > > >
> > > > > > Here's my +1.
> > > > > >
> > > > > > Thanks,
> > > > > > Andrea Cosentino
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Zineb Bendhiba
> > > > >
> > > >
> > >
> > >
> > > --
> > > Otavio R. Piske
> > > http://orpiske.net
> > >
> >
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Re: [VOTE] Release Apache Camel Kamelets 3.21.0

[Andrea Cosentino]

Hello, just a reminder we need another binding vote.

Thanks.

Il giorno sab 1 lug 2023 alle ore 07:47 Otavio Rodolfo Piske <
angusyo...@gmail.com> ha scritto:

> +1 (binding)
>
> Thanks Andrea!
>
> On Fri, Jun 30, 2023 at 4:01 PM Marat Gubaidullin <
> marat.gubaidul...@gmail.com> wrote:
>
> > +1 (non-binding)
> >
> > Thanks Andrea
> >
> > On Fri, Jun 30, 2023 at 9:39 AM Zineb Bendhiba  >
> > wrote:
> >
> > > +1 (binding)
> > >
> > > Thanks Andrea
> > >
> > > Le ven. 30 juin 2023 à 14:40, Andrea Cosentino  a
> > > écrit :
> > >
> > > > Hello all,
> > > >
> > > > This is a vote for releasing camel-kamelets 3.21.0
> > > >
> > > > Kamelets release files:
> > > > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/3.21.0
> > > > Kamelets staging repository:
> > > >
> https://repository.apache.org/content/repositories/orgapachecamel-1585
> > > > Kamelets Tag:
> > > > https://github.com/apache/camel-kamelets/releases/tag/v3.21.0
> > > >
> > > > Please cast your vote.
> > > >
> > > > [ ] +1 Release camel-kamelets 3.21.0
> > > > [ ] -1 Veto the release (provide specific comments)
> > > >
> > > > The vote is open for at least 72 hours.
> > > >
> > > > Here's my +1.
> > > >
> > > > Thanks,
> > > > Andrea Cosentino
> > > >
> > >
> > >
> > > --
> > > Zineb Bendhiba
> > >
> >
>
>
> --
> Otavio R. Piske
> http://orpiske.net
>

[VOTE] Release Apache Camel Kamelets 3.21.0

[Andrea Cosentino]

Hello all,

This is a vote for releasing camel-kamelets 3.21.0

Kamelets release files:
https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/3.21.0
Kamelets staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1585
Kamelets Tag:
https://github.com/apache/camel-kamelets/releases/tag/v3.21.0

Please cast your vote.

[ ] +1 Release camel-kamelets 3.21.0
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Here's my +1.

Thanks,
Andrea Cosentino

[RESULT][VOTE] Release Apache Camel Kamelets 3.20.6

[Andrea Cosentino]

Hello all,

The vote passed with the following result:

4 +1 binding votes: Andrea Cosentino, Otavio Rodolfo Piske, Claus Ibsen and
Jean-Baptiste Onofrè

Thanks all.

I'll go ahead with the release.

Re: [VOTE] Release Apache Camel Kamelets 3.20.6

[Andrea Cosentino]

Thanks

The vote passed.

I'll go ahead

Il giorno mar 27 giu 2023 alle ore 07:01 Jean-Baptiste Onofré <
j...@nanthrax.net> ha scritto:

> +1 (binding)
>
> Regards
> JB
>
> On Mon, Jun 26, 2023 at 11:41 AM Andrea Cosentino 
> wrote:
> >
> > Hello all:
> >
> > This is a vote for releasing camel-kamelets 3.20.6
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/3.20.6
> > Kamelets staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1580
> > Kamelets Tag:
> > https://github.com/apache/camel-kamelets/releases/tag/v3.20.6
> >
> > Please cast your vote.
> >
> > [ ] +1 Release camel-kamelets 3.20.6
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Here's my +1.
> >
> > Thanks,
> > Andrea Cosentino
>

[VOTE] Release Apache Camel Kamelets 3.20.6

[Andrea Cosentino]

Hello all:

This is a vote for releasing camel-kamelets 3.20.6

Kamelets release files:
https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/3.20.6
Kamelets staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1580
Kamelets Tag:
https://github.com/apache/camel-kamelets/releases/tag/v3.20.6

Please cast your vote.

[ ] +1 Release camel-kamelets 3.20.6
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Here's my +1.

Thanks,
Andrea Cosentino

Re: Elasticsearch migration problem from 7.6.1 to 7.17.6

[Andrea Cosentino]

The elasticsearch rest client in version 3.14.7 is 7.10.2

For reason out of our control we cannot move on a different version because
they changed the license type with something non ASF compliant:

https://github.com/elastic/elasticsearch/blob/v7.10.2/LICENSE.txt
https://github.com/elastic/elasticsearch/blob/v7.11.0/LICENSE.txt

So we moved to Elasticsearch java API since the client is ASF compliant in
terms of license.

There is not so much we could do.



Il giorno ven 23 giu 2023 alle ore 14:57 Thomas COUSIN 
ha scritto:

> I am using Elasticsearch Rest Starter.
>
> I would stay in 3.14 for now because there is breaking complatibility
> changes in GooglePubSub component since 3.18.
>
>
> De : Andrea Cosentino 
> Envoyé : vendredi 23 juin 2023 12:46
> À : users@camel.apache.org 
> Objet : Re: Elasticsearch migration problem from 7.6.1 to 7.17.6
>
> [Vous ne recevez pas souvent de courriers de anco...@gmail.com. Découvrez
> pourquoi ceci est important à
> https://aka.ms/LearnAboutSenderIdentification ]
>
> Hello,
>
> Are you using the Elasticsearch Starter or the Elasticsearch Rest Starter?
>
> Because starting from 3.19.0 there is already a component using the java
> API:
> https://camel.apache.org/components/3.20.x/elasticsearch-component.html
>
> Il giorno ven 23 giu 2023 alle ore 12:42 Thomas COUSIN <
> tcou...@solocal.com>
> ha scritto:
>
> > Hello,
> >
> > I am facing an execution error after migrate from Elasticsearch 7.6.1 to
> > 7.17.6 on my Spring Boot application (2.6.6) using Camel 3.14.7.
> > I am using the Elasticsearch High Level Rest Client.
> >
> > Stacktrace
> >
> >
> ---
> >
> > java.lang.NoClassDefFoundError: org/elasticsearch/common/CheckedConsumer
> > at
> >
> org.apache.camel.component.elasticsearch.ElasticsearchProducer$HighLevelClient.(ElasticsearchProducer.java:347)
> > ~[camel-elasticsearch-rest-3.14.7.jar:3.14.7]
> > at
> >
> org.apache.camel.component.elasticsearch.ElasticsearchProducer$HighLevelClient.(ElasticsearchProducer.java:345)
> > ~[camel-elasticsearch-rest-3.14.7.jar:3.14.7]
> > at
> >
> org.apache.camel.component.elasticsearch.ElasticsearchProducer.process(ElasticsearchProducer.java:124)
> > ~[camel-elasticsearch-rest-3.14.7.jar:3.14.7]
> > at
> >
> org.apache.camel.support.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:66)
> > ~[camel-support-3.14.7.jar:3.14.7]
> > ... 9 more
> > Wrapped by: org.apache.camel.CamelExecutionException: Exception occurred
> > during execution on the exchange:
> Exchange[88DD3EC7DD8FD02-028B]
> > at
> >
> org.apache.camel.CamelExecutionException.wrapCamelExecutionException(CamelExecutionException.java:45)
> > ~[camel-api-3.14.7.jar:3.14.7]
> > at
> >
> org.apache.camel.support.AbstractExchange.setException(AbstractExchange.java:591)
> > ~[camel-support-3.14.7.jar:3.14.7]
> > at
> >
> org.apache.camel.support.DefaultExchange.setException(DefaultExchange.java:27)
> > ~[camel-support-3.14.7.jar:3.14.7]
> > at
> >
> org.apache.camel.support.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:69)
> > ~[camel-support-3.14.7.jar:3.14.7]
> > at
> > org.apache.camel.processor.SendProcessor.process(SendProcessor.java:172)
> > ~[camel-core-processor-3.14.7.jar:3.14.7]
> > at
> >
> org.apache.camel.management.DefaultInstrumentationProcessor.process(DefaultInstrumentationProcessor.java:90)
> > ~[camel-management-3.14.7.jar:3.14.7]
> > at
> >
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.redeliver(RedeliveryErrorHandler.java:884)
> > ~[camel-core-processor-3.14.7.jar:3.14.7]
> > at
> >
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:193)
> > ~[camel-base-engine-3.14.7.jar:3.14.7]
> > at
> >
> org.apache.camel.impl.engine.DefaultReactiveExecutor.schedule(DefaultReactiveExecutor.java:59)
> > ~[camel-base-engine-3.14.7.jar:3.14.7]
> > at
> >
> org.apache.camel.processor.aggregate.AggregateProcessor.lambda$onSubmitCompletion$4(AggregateProcessor.java:893)
> > ~[camel-core-processor-3.14.7.jar:3.14.7]
> > at
> >
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> > ~[?:?]
> 

Re: Elasticsearch migration problem from 7.6.1 to 7.17.6

[Andrea Cosentino]

Hello,

Are you using the Elasticsearch Starter or the Elasticsearch Rest Starter?

Because starting from 3.19.0 there is already a component using the java
API: https://camel.apache.org/components/3.20.x/elasticsearch-component.html

Il giorno ven 23 giu 2023 alle ore 12:42 Thomas COUSIN 
ha scritto:

> Hello,
>
> I am facing an execution error after migrate from Elasticsearch 7.6.1 to
> 7.17.6 on my Spring Boot application (2.6.6) using Camel 3.14.7.
> I am using the Elasticsearch High Level Rest Client.
>
> Stacktrace
>
> ---
>
> java.lang.NoClassDefFoundError: org/elasticsearch/common/CheckedConsumer
> at
> org.apache.camel.component.elasticsearch.ElasticsearchProducer$HighLevelClient.(ElasticsearchProducer.java:347)
> ~[camel-elasticsearch-rest-3.14.7.jar:3.14.7]
> at
> org.apache.camel.component.elasticsearch.ElasticsearchProducer$HighLevelClient.(ElasticsearchProducer.java:345)
> ~[camel-elasticsearch-rest-3.14.7.jar:3.14.7]
> at
> org.apache.camel.component.elasticsearch.ElasticsearchProducer.process(ElasticsearchProducer.java:124)
> ~[camel-elasticsearch-rest-3.14.7.jar:3.14.7]
> at
> org.apache.camel.support.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:66)
> ~[camel-support-3.14.7.jar:3.14.7]
> ... 9 more
> Wrapped by: org.apache.camel.CamelExecutionException: Exception occurred
> during execution on the exchange: Exchange[88DD3EC7DD8FD02-028B]
> at
> org.apache.camel.CamelExecutionException.wrapCamelExecutionException(CamelExecutionException.java:45)
> ~[camel-api-3.14.7.jar:3.14.7]
> at
> org.apache.camel.support.AbstractExchange.setException(AbstractExchange.java:591)
> ~[camel-support-3.14.7.jar:3.14.7]
> at
> org.apache.camel.support.DefaultExchange.setException(DefaultExchange.java:27)
> ~[camel-support-3.14.7.jar:3.14.7]
> at
> org.apache.camel.support.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:69)
> ~[camel-support-3.14.7.jar:3.14.7]
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:172)
> ~[camel-core-processor-3.14.7.jar:3.14.7]
> at
> org.apache.camel.management.DefaultInstrumentationProcessor.process(DefaultInstrumentationProcessor.java:90)
> ~[camel-management-3.14.7.jar:3.14.7]
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.redeliver(RedeliveryErrorHandler.java:884)
> ~[camel-core-processor-3.14.7.jar:3.14.7]
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:193)
> ~[camel-base-engine-3.14.7.jar:3.14.7]
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor.schedule(DefaultReactiveExecutor.java:59)
> ~[camel-base-engine-3.14.7.jar:3.14.7]
> at
> org.apache.camel.processor.aggregate.AggregateProcessor.lambda$onSubmitCompletion$4(AggregateProcessor.java:893)
> ~[camel-core-processor-3.14.7.jar:3.14.7]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> ~[?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> ~[?:?]
> at java.lang.Thread.run(Thread.java:834) ~[?:?]
>
>
> ---
>
>
> Same problem was described on Stackoverflow but nobody found a solution :
> https://stackoverflow.com/questions/70666910/apache-camel-elasticsearch-endpoint-failing-with-classnotfoundexception-org-ela
>
> I tried to upgrade to Camel 3.20.3 but the error is still there.
>
> Could the solution be to migrate to Elasticsearch Java Api Client ?
>
>
> Thanks in advance for your help
>
> Thomas Cousin
>
> [bandeau_pagesjaunes3]<
> https://www.youtube.com/playlist?list=PLlp-0-iXtsZMOsEKlmySbkrj7VNjqUOfH>
>
> [bandeau_partenaires]
>
> Les informations contenues dans le présent message sont strictement
> confidentielles et ne sont destinées qu'à l'usage de la ou des personne(s)
> dont le nom apparaît en qualité de destinataire(s) et de tout autre
> personne spécifiquement autorisée à les recevoir. Si vous n'êtes pas la
> personne à qui ce message est destiné, nous vous informons qu'il est
> strictement interdit de le lire, diffuser, de le distribuer ou d'en faire
> des copies, totalement ou partiellement, sur tout support, notamment un
> support électronique, ou autre. La présente interdiction s'applique tant au
> message lui-même qu'aux documents qui peuvent être joints audit message. Si
> vous recevez ce message par erreur, nous vous remercions de bien vouloir le
> détruire ainsi que toute copie et de signaler l'erreur à l'envoyeur par
> retour d’e-mail.
>

Re: [VOTE] Release Apache Camel K 1.12.1 and Camel K runtime 1.17.1 - second attempt

[Andrea Cosentino]

+1 (binding)

Thanks Pasquale

Il giorno mer 7 giu 2023 alle ore 16:54 Zineb Bendhiba <
bendhiba.zi...@gmail.com> ha scritto:

> +1 (binding)
>
> Thanks Pasquale
>
> Le mer. 7 juin 2023 à 14:56, Pasquale Congiusti <
> pasquale.congiu...@gmail.com> a écrit :
>
> > Hello,
> >
> > This is a combined vote to release Apache Camel K 1.12.1 and Camel K
> > Runtime1.17.1. The release also contains the Camel K CRD 1.12.1, a Java
> > client for Kubernetes Camel K CRDs. The release is based on Camel 3.20.x
> > and Camel Quarkus 2.16.x. It contains mostly bug fixes. A first attempt
> to
> > release this version was canceled last week due to a bug found while
> > testing the staging version.
> >
> > Camel K Runtime source files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/1.17.1/
> >
> > Camel K Runtime staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1565
> >
> > Camel K Runtime Tag:
> >
> >
> https://github.com/apache/camel-k-runtime/releases/tag/camel-k-runtime-project-1.17.1
> >
> > Camel K release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k/1.12.1/
> >
> > Camel K Tag:
> > https://github.com/apache/camel-k/releases/tag/v1.12.1
> >
> > Camel K CRD Java dependency staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1566
> >
> > Staging container image repository:
> >
> >
> https://hub.docker.com/layers/camelk/camel-k/1.12.1/images/sha256-34b0ea1de619b1790fce1031dcd332f4be1429c045fab30dfe60d589554f842c?context=repo
> >
> > It's possible to install all staging artifacts with a single command
> > (preferably using the kamel CLI you find in Camel K release files):
> >
> > kamel install --operator-image=camelk/camel-k:1.12.1 --maven-repository=
> > https://repository.apache.org/content/repositories/orgapachecamel-1565
> >  --olm=false
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binary as Apache Camel K 1.12.1 and Apache Camel K
> > Runtime 1.17.1
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > I start the vote with my +1.
> >
> > Thanks and regards,
> > Pasquale Congiusti
> >
>
>
> --
> Zineb
>

[RESULT][VOTE] Release Apache Camel Kamelets 3.20.5

[Andrea Cosentino]

Hello all,

The vote passed with the following result:

4 +1 binding votes: Andrea Cosentino, Claus Ibsen, Pasquale Congiusti and
Zineb Bendhiba

1 +1 non-binding vote: Gaelle Fournier

I'll go ahead with the process.

Thanks all.

Re: [VOTE] Release Apache Camel Kamelets 3.20.5

[Andrea Cosentino]

Thanks all,

The vote passes.

Il giorno mar 30 mag 2023 alle ore 13:03 zineb bendhiba <
bendhiba.zi...@gmail.com> ha scritto:

> +1 (binding)
>
> Thanks
>
> Zineb Bendhiba
>
> >
> > Le 29 mai 2023 à 18:45, Andrea Cosentino  a écrit :
> >
> > Hello all:
> >
> > This is a vote for releasing camel-kamelets 3.20.5
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/3.20.5
> > Kamelets staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1567
> > Kamelets Tag:
> > https://github.com/apache/camel/releases/tag/camel-3.20.5
> >
> > Please cast your vote.
> >
> > [ ] +1 Release camel-kamelets 3.20.5
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Here's my +1.
> >
> > Thanks,
> > Andrea Cosentino
>

Re: Camel 4.0.0-M3 with Velocity - Deprecation warning

[Andrea Cosentino]

Please open an issue on camel Jira and we'll check.

It's just a deprecation, nothing problematic
Il ven 2 giu 2023, 14:44 Ramesh Venk  ha scritto:

> Hello
> I'm using Apache Camel 4.0.0-M3 with Quarkus 3.1.0.Final and using the
> "camel-quarkus-velocity" to render a template. The template works
> correctly, however, I see this message printed in the logs
>
> 2023-06-02 07:33:34,879 WARN  [org.apa.vel.deprecation] (Camel
> (camel-1) thread #1 - timer://twoTimes) configuration key
> 'resource.loader' has been deprecated in favor of 'resource.loaders'
>
> It looks like it has been fixed in 3.5.0 per this JIRA
> (https://issues.apache.org/jira/browse/CAMEL-15240), however, in
> 4.0.0-M3 it seems to still have this issue.
>
> What would need to be done in order to fix this? Thanks.
>
> --
> Ramesh
>

Re: 3.20.4 Bug(?): Route's ErrorHandler not working if exception happens on Kamelet

[Andrea Cosentino]

But it's not with kamelets it's a plain route

Il ven 2 giu 2023, 10:08 Andrea Cosentino  ha scritto:

> There is one example in the camel-kamelets-example repo:
>
>
> https://github.com/apache/camel-kamelets-examples/tree/main/jbang/error-handler
>
> Il ven 2 giu 2023, 10:03 Pasquale Congiusti 
> ha scritto:
>
>> Hello,
>> Error handler should be managed differently in Kamelets. Basically the
>> problem is that a Kamelet is a RouteTemplate, so it is like a new Route
>> and
>> won't "inherit" the configuration you've defined in the original route. I
>> think you need to define your error inside the Kamelet specification
>> (which
>> it's not a very nice design). In Camel K, we've created a layer on top of
>> it inside the runtime, in order to let the user define the error handling
>> in the Binding [1].
>>
>> We had some draft work [2] to enhance that, expecting a similar global
>> mechanism in Camel. However, I haven't followed by near the recent
>> developments in Camel 4 to tell you if this is going to be included in the
>> new version or not.
>>
>> Regards,
>> Pasquale.
>>
>> [1]
>>
>> https://camel.apache.org/camel-k/1.12.x/kamelets/kameletbindings-error-handler.html
>> [2] https://github.com/apache/camel-k-runtime/pull/868
>>
>> On Fri, Jun 2, 2023 at 7:35 AM Mikael Koskinen 
>> wrote:
>>
>> > Hey,
>> >
>> > I wonder if anyone has any info regarding this issue? It's possible
>> > (and maybe quite likely!) that I'm using the
>> > routeConfiguration/errorHandler incorrectly.
>> >
>> > Thanks in advance.
>> >
>> > Best regards,
>> > Mikael
>> >
>> > pe 19. toukok. 2023 klo 15.24 Mikael Koskinen (mijap...@gmail.com)
>> > kirjoitti:
>> > >
>> > > Hi,
>> > >
>> > > I'm encountering a problem where route configuration's error handler
>> > > isn't run if the exception happens on a Kamelet. Here's the gist with
>> > > tries to show the issue:
>> > >
>> >
>> https://gist.githubusercontent.com/mikoskinen/4e3e3a8efdf891890a2a46dfddae1d48/raw/09055bcdc1c2252a77a069fcebd07d6f727db555/camel-yaml-kamelet-errorhandling.yaml
>> > >
>> > > More details:
>> > >
>> > >
>> > > First, here's a (working) version with no Kamelets:
>> > >
>> > > - routeConfiguration:
>> > > errorHandler:
>> > >   deadLetterChannel:
>> > > deadLetterUri: direct:errorHandler
>> > > redeliveryPolicy:
>> > >   maximumRedeliveries: 0
>> > > - route:
>> > > from:
>> > >   uri: timer:timer
>> > >   steps:
>> > > - setBody:
>> > > expression:
>> > >   constant:
>> > > expression: Hello World
>> > > - marshal:
>> > > json:
>> > >   library: jackson
>> > >   prettyPrint: true
>> > > - to:
>> > > uri:
>> > https://webhook.site/b7562774-4939-4e90-9337-5b9dd4d2ff1d
>> > > - route:
>> > > from:
>> > >   uri: direct:errorHandler
>> > >   steps:
>> > > - log:
>> > > message: Handling error
>> > > loggingLevel: WARN
>> > > description: Handle Error
>> > >
>> > > When run, this is what I see in the logs:
>> > >
>> > > 2023-05-19 15:14:13.783 WARN 20268 --- [- timer://timer]
>> > > testing.camel.yaml:25 : Handling error
>> > > 2023-05-19 15:14:14.626 WARN 20268 --- [- timer://timer]
>> > > testing.camel.yaml:25 : Handling error
>> > >
>> > > It is working as I expected.
>> > >
>> > > Now, with a just one change where HTTP component is changed to Kamelet
>> > > HTTP Sink and I'm getting completely different result.
>> > >
>> > > - routeConfiguration:
>> > > errorHandler:
>> > >   deadLetterChannel:
>> > > deadLetterUri: direct:errorHandler
>> > > redeliveryPolicy:
>> > >   maximumRedeliveries: 0
>> > > - route:
>> > > from:
>> > >   uri: timer:timer
>> > >   steps:
>> > > - setBody:
>> >

Re: 3.20.4 Bug(?): Route's ErrorHandler not working if exception happens on Kamelet

[Andrea Cosentino]

There is one example in the camel-kamelets-example repo:

https://github.com/apache/camel-kamelets-examples/tree/main/jbang/error-handler

Il ven 2 giu 2023, 10:03 Pasquale Congiusti 
ha scritto:

> Hello,
> Error handler should be managed differently in Kamelets. Basically the
> problem is that a Kamelet is a RouteTemplate, so it is like a new Route and
> won't "inherit" the configuration you've defined in the original route. I
> think you need to define your error inside the Kamelet specification (which
> it's not a very nice design). In Camel K, we've created a layer on top of
> it inside the runtime, in order to let the user define the error handling
> in the Binding [1].
>
> We had some draft work [2] to enhance that, expecting a similar global
> mechanism in Camel. However, I haven't followed by near the recent
> developments in Camel 4 to tell you if this is going to be included in the
> new version or not.
>
> Regards,
> Pasquale.
>
> [1]
>
> https://camel.apache.org/camel-k/1.12.x/kamelets/kameletbindings-error-handler.html
> [2] https://github.com/apache/camel-k-runtime/pull/868
>
> On Fri, Jun 2, 2023 at 7:35 AM Mikael Koskinen  wrote:
>
> > Hey,
> >
> > I wonder if anyone has any info regarding this issue? It's possible
> > (and maybe quite likely!) that I'm using the
> > routeConfiguration/errorHandler incorrectly.
> >
> > Thanks in advance.
> >
> > Best regards,
> > Mikael
> >
> > pe 19. toukok. 2023 klo 15.24 Mikael Koskinen (mijap...@gmail.com)
> > kirjoitti:
> > >
> > > Hi,
> > >
> > > I'm encountering a problem where route configuration's error handler
> > > isn't run if the exception happens on a Kamelet. Here's the gist with
> > > tries to show the issue:
> > >
> >
> https://gist.githubusercontent.com/mikoskinen/4e3e3a8efdf891890a2a46dfddae1d48/raw/09055bcdc1c2252a77a069fcebd07d6f727db555/camel-yaml-kamelet-errorhandling.yaml
> > >
> > > More details:
> > >
> > >
> > > First, here's a (working) version with no Kamelets:
> > >
> > > - routeConfiguration:
> > > errorHandler:
> > >   deadLetterChannel:
> > > deadLetterUri: direct:errorHandler
> > > redeliveryPolicy:
> > >   maximumRedeliveries: 0
> > > - route:
> > > from:
> > >   uri: timer:timer
> > >   steps:
> > > - setBody:
> > > expression:
> > >   constant:
> > > expression: Hello World
> > > - marshal:
> > > json:
> > >   library: jackson
> > >   prettyPrint: true
> > > - to:
> > > uri:
> > https://webhook.site/b7562774-4939-4e90-9337-5b9dd4d2ff1d
> > > - route:
> > > from:
> > >   uri: direct:errorHandler
> > >   steps:
> > > - log:
> > > message: Handling error
> > > loggingLevel: WARN
> > > description: Handle Error
> > >
> > > When run, this is what I see in the logs:
> > >
> > > 2023-05-19 15:14:13.783 WARN 20268 --- [- timer://timer]
> > > testing.camel.yaml:25 : Handling error
> > > 2023-05-19 15:14:14.626 WARN 20268 --- [- timer://timer]
> > > testing.camel.yaml:25 : Handling error
> > >
> > > It is working as I expected.
> > >
> > > Now, with a just one change where HTTP component is changed to Kamelet
> > > HTTP Sink and I'm getting completely different result.
> > >
> > > - routeConfiguration:
> > > errorHandler:
> > >   deadLetterChannel:
> > > deadLetterUri: direct:errorHandler
> > > redeliveryPolicy:
> > >   maximumRedeliveries: 0
> > > - route:
> > > from:
> > >   uri: timer:timer
> > >   steps:
> > > - setBody:
> > > expression:
> > >   constant:
> > > expression: Hello World
> > > - marshal:
> > > json:
> > >   library: jackson
> > >   prettyPrint: true
> > > - to:
> > > uri: kamelet:http-sink
> > > parameters:
> > >   url:
> > https://webhook.site/b7562774-4939-4e90-9337-5b9dd4d2ff1d
> > > - route:
> > > from:
> > >   uri: direct:errorHandler
> > >   steps:
> > > - log:
> > > message: Handling error
> > > loggingLevel: WARN
> > > description: Handle Error
> > >
> > > Now when run I'm getting the stacktrace and there's no "Handling
> > > error" to be found:
> > >
> > > 2023-05-19 15:20:22.084 INFO 17192 --- [ main]
> > > el.impl.engine.AbstractCamelContext : Apache Camel 3.20.4 (tes
> > > ting) started in 4s854ms (build:196ms init:3s906ms start:752ms
> > JVM-uptime:8s)
> > > 2023-05-19 15:20:23.165 ERROR 17192 --- [- timer://timer]
> > > or.errorhandler.DefaultErrorHandler : Failed delivery for (Mes
> > > sageId: B24BA7702CBB985- on ExchangeId:
> > > B24BA7702CBB985-). Exhausted after delivery atte
> > > mpt: 1 caught: java.net.UnknownHostException: No such host is known
> > > (webhook.site)
> > >
> > > Message History
> > >
> >
> 

Re: [VOTE] Release Apache Camel K 1.12.1 and Camel K runtime 1.17.1

[Andrea Cosentino]

+1 (binding)

Thanks Pasquale

Il giorno lun 29 mag 2023 alle ore 17:27 Pasquale Congiusti <
pasquale.congiu...@gmail.com> ha scritto:

> Hello,
>
> This is a combined vote to release Apache Camel K 1.12.1 and Camel K
> Runtime1.17.1. The release also contains the Camel K CRD 1.12.1, a Java
> client for Kubernetes Camel K CRDs. The release is based on Camel 3.20.x
> and Camel Quarkus 2.16.x. It contains mostly bug fixes.
>
> Camel K Runtime source files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/1.17.1/
>
> Camel K Runtime staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1565
>
> Camel K Runtime Tag:
>
> https://github.com/apache/camel-k-runtime/releases/tag/camel-k-runtime-project-1.17.1
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/1.12.1/
>
> Camel K Tag:
> https://github.com/apache/camel-k/releases/tag/v1.12.1
>
> Camel K CRD Java dependency staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1566
>
> Staging container image repository:
>
> https://hub.docker.com/layers/camelk/camel-k/1.12.1/images/sha256-34b0ea1de619b1790fce1031dcd332f4be1429c045fab30dfe60d589554f842c?context=repo
>
> It's possible to install all staging artifacts with a single command:
>
> kamel install --operator-image=camelk/camel-k:1.12.1 --maven-repository=
> https://repository.apache.org/content/repositories/orgapachecamel-1565
>  --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release the binary as Apache Camel K 1.12.1 and Apache Camel K
> Runtime 1.17.1
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> I start the vote with my +1.
>
> Thanks and regards,
> Pasquale Congiusti
>

[VOTE] Release Apache Camel Kamelets 3.20.5

[Andrea Cosentino]

Hello all:

This is a vote for releasing camel-kamelets 3.20.5

Kamelets release files:
https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/3.20.5
Kamelets staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1567
Kamelets Tag:
https://github.com/apache/camel/releases/tag/camel-3.20.5

Please cast your vote.

[ ] +1 Release camel-kamelets 3.20.5
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Here's my +1.

Thanks,
Andrea Cosentino

[RESULT][VOTE] Release Apache Camel Kamelets 3.20.4

[Andrea Cosentino]

Hello all,

The vote passes with the following results:

4 +1 binding votes: Andrea Cosentino, Claus Ibsen, Babak Vahdat and
Jean-Baptiste Onofrè

I'll go ahead with the process.

Thanks all.

Re: [VOTE] Release Apache Camel Kamelets 3.20.4

[Andrea Cosentino]

Thanks the vote passes.

I'll go ahead with the flow.

Il giorno gio 18 mag 2023 alle ore 07:19 Jean-Baptiste Onofré <
j...@nanthrax.net> ha scritto:

> +1 (binding)
>
> Regards
> JB
>
> On Tue, May 16, 2023 at 12:15 PM Andrea Cosentino 
> wrote:
> >
> > Hello all:
> >
> > This is a vote for releasing camel-kamelets 3.20.4
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/3.20.4
> > Kamelets staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1554
> > Kamelets Tag:
> > https://github.com/apache/camel/releases/tag/camel-3.20.4
> >
> > Please cast your vote.
> >
> > [ ] +1 Release camel-kamelets 3.20.4
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Here's my +1.
> >
> > Thanks,
> > Andrea Cosentino
>

Re: [VOTE] Release Apache Camel Kamelets 3.20.4

[Andrea Cosentino]

Gently reminder. Please vote.

Il mar 16 mag 2023, 12:33 Babak Vahdat 
ha scritto:

> +1 (binding)
>
> Thanks Andrea!
>
> --
> Babak
>
> > On 16 May 2023, at 12:15, Andrea Cosentino  wrote:
> >
> > Hello all:
> >
> > This is a vote for releasing camel-kamelets 3.20.4
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/3.20.4
> > Kamelets staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1554
> > Kamelets Tag:
> > https://github.com/apache/camel/releases/tag/camel-3.20.4
> >
> > Please cast your vote.
> >
> > [ ] +1 Release camel-kamelets 3.20.4
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Here's my +1.
> >
> > Thanks,
> > Andrea Cosentino
>
>

Re: ZeroMQ Support

[Andrea Cosentino]

The component is still available as camel-extra

https://github.com/camel-extra/camel-extra/blob/master/components/camel-zeromq/pom.xml

They are releasing just camel-wmq as far as I see, supporting camel 3

You could ask them to align and release the zeromq one.

Il giorno mar 16 mag 2023 alle ore 17:29 Mark Webb 
ha scritto:

> I've been trying to find information on Apache Camel's support of a ZeroMQ
> component.  I see that there was a component back in the 2.x days but I
> cannot find anything compatible with the current version of Camel 3.x.
>
> Does the component exist somewhere?  Did support stop for a particular
> reason?  I'm very interested in using Apache Camel with ZeroMQ so if
> someone could help to get me up to speed on what's going on, it would be
> much appreciated.
>
> Mark
>

[VOTE] Release Apache Camel Kamelets 3.20.4

[Andrea Cosentino]

Hello all:

This is a vote for releasing camel-kamelets 3.20.4

Kamelets release files:
https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/3.20.4
Kamelets staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1554
Kamelets Tag:
https://github.com/apache/camel/releases/tag/camel-3.20.4

Please cast your vote.

[ ] +1 Release camel-kamelets 3.20.4
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Here's my +1.

Thanks,
Andrea Cosentino

[RESULT][VOTE] Release Apache Camel Kamelets 4.0.0-M3

[Andrea Cosentino]

Hello all

The vote passes with the following result:

4 +1 binding votes:

Andrea Cosentino
Zineb Bendhiba
Claus Ibsen
Pasquale Congiusti

Thanks.

Re: [VOTE] Release Apache Camel Kamelets 4.0.0-M3

[Andrea Cosentino]

Thanks all the vote passes.

I'll go ahead.

Il giorno gio 11 mag 2023 alle ore 15:18 Pasquale Congiusti <
pasquale.congiu...@gmail.com> ha scritto:

> +1 (binding)
>
> Thanks!
>
> On Thu, May 11, 2023 at 2:56 PM Claus Ibsen  wrote:
>
> > +1 (binding)
> >
> > On Thu, May 11, 2023 at 2:30 PM Andrea Cosentino 
> > wrote:
> >
> > > Hello all:
> > >
> > > This is a vote for releasing camel-kamelets 4.0.0-M3
> > >
> > > Kamelets release files:
> > > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.0-M3
> > > Kamelets staging repository:
> > > https://repository.apache.org/content/repositories/orgapachecamel-1553
> > > Kamelets Tag:
> > > https://github.com/apache/camel/releases/tag/camel-4.0.0-M3
> > >
> > > Please cast your vote.
> > >
> > > [ ] +1 Release camel-kamelets 4.0.0-M3
> > > [ ] -1 Veto the release (provide specific comments)
> > >
> > > The vote is open for at least 72 hours.
> > >
> > > Here's my +1.
> > >
> > > Thanks,
> > > Andrea Cosentino
> > >
> >
> >
> > --
> > Claus Ibsen
> > -
> > @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
>

Re: [VOTE] Release Apache Camel Kamelets 4.0.0-M3

[Andrea Cosentino]

The Kamelets tag for 4.0.0-M3 is here:

https://github.com/apache/camel-kamelets/releases/tag/v4.0.0-M3

Sorry for the wrong link.

Il giorno gio 11 mag 2023 alle ore 14:30 Andrea Cosentino 
ha scritto:

> Hello all:
>
> This is a vote for releasing camel-kamelets 4.0.0-M3
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.0-M3
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1553
> Kamelets Tag:
> https://github.com/apache/camel/releases/tag/camel-4.0.0-M3
>
> Please cast your vote.
>
> [ ] +1 Release camel-kamelets 4.0.0-M3
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino
>

[VOTE] Release Apache Camel Kamelets 4.0.0-M3

[Andrea Cosentino]

Hello all:

This is a vote for releasing camel-kamelets 4.0.0-M3

Kamelets release files:
https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.0-M3
Kamelets staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1553
Kamelets Tag:
https://github.com/apache/camel/releases/tag/camel-4.0.0-M3

Please cast your vote.

[ ] +1 Release camel-kamelets 4.0.0-M3
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Here's my +1.

Thanks,
Andrea Cosentino

Re: Camel in Action: Microsoft Azure Files over public Internet

[Andrea Cosentino]

Hello,

To me it makes sense to have a component supporting the SDK.

Open an issue for that, if you have time you could contribute it, otherwise
someone could take a look.

Il giorno mar 18 apr 2023 alle ore 09:18 Petr Kuzel
 ha scritto:

> Hi Chirag,
>
> well, it is not the first time I hear, apparently
> it is a common confusion in the community.
>
> Azure Blob Storage
>   Massively scalable and secure object storage for cloud-native workloads,
>   archives, data lakes, high-performance computing, and machine learning.
>   
>
> Azure Files
>   Simple, secure, and serverless enterprise-grade cloud file shares.
>   
>
> My question is about Azure Files.
>
>   Best regards
>   Cc.
>
> -Original Message-
> From: Chirag 
> Sent: Monday, April 17, 2023 17:30
> To: users@camel.apache.org
> Subject: Re: Camel in Action: Microsoft Azure Files over public Internet
>
>
> Shouldn't you be lookin at
>
> https://camel.apache.org/components/3.20.x/azure-storage-blob-component.html
> ?
>
> Or a variation of it? The APIs are similar.
>
>
> ચિરાગ/चिराग/Chirag
> --
> Sent from My Gmail Account
>
> On Mon, Apr 17, 2023 at 11:18 AM Petr Kuzel
>  wrote:
> >
> > I have a new RFE which includes integrating
> > Microsoft Azure Files over public Internet.
> >
> > Initial findings and constraints:
> >
> >   - Azure Files do not implement the FTP standard.
> >   - Azure Files could expose SMB protocol but SMB over
> > public Internet is blacklisted by the security policy.
> >   - Azure Files could expose NFS but its pricing is prohibitive.
> >   - Azure Files have REST API <
> https://github.com/Azure/azure-rest-api-specs>
> > and Java SDK .
> >   - My team is used to Camel 3.x components.
> >
> > Given that I see the two options:
> >
> >   A: use Camel REST component.
> >   B: use Azure Files remote file component.
> >
> > Neither seems easy. For the Camel REST component,
> > I'd need to implement a polling consumer via REST and
> > match the FTPS component-like capabilities. For Azure Files,
> > I have not found a developed Camel remote file component
> > so its development would be required, i.e. likely a continuation
> > at the Camel dev list...
> >
> > First, have I overlooked any recommendable option that
> > could address the problem, please?
> >
> > Second, if left only with above two options, which approach
> > would look more promising from a Camel veteran perspective
> > and why, please?
> >
> >   Best regards
> >   Cc.
> >
> > --
> >   Mr. Petr Kužel, Software Engineer
> >   Eurofins International Support Services s.à r.l.
> >   Val Fleuri 23
> >   L-1526 LUXEMBOURG
> >
>

[RESULT][VOTE] Release Apache Camel Kamelets 4.0.0-M2

[Andrea Cosentino]

Hello all,

This vote passes with the following result:

5 +1 binding votes: Andrea Cosentino, Jean-Baptiste Onofrè, Otavio Rodolfo
Piske, Claus Ibsen and Pasquale Congiusti

I'll go ahead with the process.

Thanks all.

Re: [VOTE] Release Apache Camel Kamelets 4.0.0-M2

[Andrea Cosentino]

Thanks all,

This vote passes.

I'll go ahead.

Il giorno ven 14 apr 2023 alle ore 09:28 Pasquale Congiusti <
pasquale.congiu...@gmail.com> ha scritto:

> +1 (binding)
>
> Thanks,
> Pasquale.
>
> On Thu, Apr 13, 2023 at 2:41 PM Andrea Cosentino 
> wrote:
>
> > Hello all:
> >
> > This is a vote for releasing camel-kamelets 4.0.0-M2
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.0.0-M2
> > Kamelets staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1544
> > Kamelets Tag:
> >
> >
> https://gitbox.apache.org/repos/asf?p=camel-kamelets.git;a=shortlog;h=refs/tags/v4.0.0-M2
> >
> > Please cast your vote.
> >
> > [ ] +1 Release camel-kamelets 4.0.0-M2
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Here's my +1.
> >
> > Thanks,
> > Andrea Cosentino
> >
>

Re: [VOTE] Release Apache Camel Kamelets 3.20.3

[Andrea Cosentino]

Thanks all.

The vote passes.

Il giorno ven 14 apr 2023 alle ore 09:28 Pasquale Congiusti <
pasquale.congiu...@gmail.com> ha scritto:

> +1 (binding)
>
> Thanks,
> Pasquale.
>
> On Thu, Apr 13, 2023 at 2:42 PM Andrea Cosentino 
> wrote:
>
> > Hello all:
> >
> > This is a vote for releasing camel-kamelets 3.20.3
> >
> > This release contains bug fixes and upgrade to latest camel 3.20.3
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/3.20.3
> > Kamelets staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1545
> > Kamelets Tag:
> >
> >
> https://gitbox.apache.org/repos/asf?p=camel-kamelets.git;a=shortlog;h=refs/tags/v3.20.3
> >
> > Please cast your vote.
> >
> > [ ] +1 Release camel-kamelets 3.20.3
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Here's my +1.
> >
> > Thanks,
> > Andrea Cosentino
> >
>

[RESULT][VOTE] Release Apache Camel Kamelets 3.20.3

[Andrea Cosentino]

Hello all,

This vote passes with the following result:

5 +1 binding votes: Andrea Cosentino, Jean-Baptiste Onofrè, Otavio Rodolfo
Piske, Claus Ibsne and Pasquale Congiusti

1 +1 non-binding vote: Claudio Miranda

I'll go ahead with the process.

Thanks all.