date:20240301

Re: Reconfigure incoming file endpoint to follow current date

2024-03-01 Thread Claus Ibsen

Hi

If they all have the same root folder (starting directory)

from file:files?filter=xxx

Then you can use filter to select which dir/files to accept. You can use
simple pattern with now as a date to make it match current day. Or write a
bit of code in a custom file filter class.
See the file component docs for more details.




On Fri, Mar 1, 2024 at 2:04 PM Jan Bares, WOOD & Co. 
wrote:

> Hi,
>
> We need to read files from a folder,that contains current date. During
> quiet period after midnight we need to "switch" to the new folder. What are
> possible solutions? Essentially we need to change endpoint configuration on
> runtime at specific time. Our routes are configured using Java DSL.
>
> On March 1 the folder name is FILES/2024_03_01
> On March 2 the folder name will be FILES/2024_03_02
> ...
>
> Kind regards, Jan
>
> Jan Bares
> Head of Calypso development | IT Development
>
> Phone: +420 222 096 457
> Mobile: +420 776 333 676
> Email: jan.ba...@wood.cz
>
> WOOD & Company
> Palladium, n?m. Republiky 1079/1a, 110 00 Prague 1, Czech Republic |
> wood.cz
>
>
>
>
>
> 
> DISCLAIMER
> WOOD & Company Financial Services, a.s. and its branches are authorized
> and regulated by the CNB as Home State regulator and in Poland by the KNF,
> in Slovakia by the NBS, in Italy by the CONSOB and in the UK by the FCA as
> Host State regulators. For further information about WOOD & Co., its
> investment services, financial instruments and associated risks, safeguard
> client assets (incl. compensation schemes) and contractual relationship
> please see our website at www.wood.com under
> section Corporate Governance. Unless otherwise stated, this transmission is
> neither an offer nor the solicitation of an offer to sell or purchase any
> investment. All estimates, opinions and other information contained herein
> are subject to change without notice and are provided in good faith but
> without legal responsibility or liability. Opinion may be personal to the
> author and may not reflect the opinions of WOOD & Co. Communications from
> sales persons, sales traders or traders should not be regarded as
> investment research and may contain opinions or trading ideas which are
> different from WOOD & Co. investment research opinions. This e-mail and any
> attachments are confidential and may be privileged or otherwise protected
> from disclosure. If you are not a named addressee you must not use,
> disclose, distribute, copy, print or rely on this e-mail and any of its
> attachments. Please notify the sender that you have received this email by
> mistake by replying to the email, and then delete the email and any copies
> of it. Although WOOD & Co. routinely screens e-mails for viruses,
> addressees should scan this e-mail and any attachments for viruses. WOOD &
> Co. makes no representation or warranty as to the absence of viruses in
> this e-mail or any attachments. Please note that to ensure regulatory
> compliance and for the protection of our clients and business, we may
> monitor and read e-mails sent to and from our server(s).
>


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

Re: using Camel with CloudKarafka

2024-03-01 Thread Chirag

Hello Andrea,

Thanks for the callout.

I had this correctly set up in my route that writes to Kafka but i had
missed it on my read from Kafka flow as well as ended up having two lines
of Yaml merged into one due to manual editing.

Both work now.

Here is my updated 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
saslMechanism: SCRAM-SHA-256
clientId: kafkaconsumer1
autoOffsetReset: latest
consumersCount: '10'
groupId: kafkaconsumergroup1
  steps:
- log:
id: log-1987
message: ${body}
ચિરાગ/चिराग/Chirag
--
Sent from My Gmail Account


On Fri, Mar 1, 2024 at 12:43 AM Andrea Cosentino  wrote:

> 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:

Re: Reconfigure incoming file endpoint to follow current date

2024-03-01 Thread Jan Bares, WOOD & Co.

Thank you for your time, we need exactly that.

Jan

Sent from Nine


From: Federico Mariani 
Sent: Friday, March 1, 2024 16:50
To: users@camel.apache.org
Subject: Re: Reconfigure incoming file endpoint to follow current date

Hi, I'd use a quartz scheduler and a route template, something like this:


routeTemplate("file-template")
.templateParameter("folder")
.from("file://data/{{folder}}")
.to("direct:computeFile");

from("quartz:scheduler?cron=0+0+12+*+*+?")
.id("timer-route")
.process(exchange -> {
if (exchange.getContext().getRoute("file-route") != null) {

exchange.getContext().getRouteController().stopRoute("file-route");
exchange.getContext().removeRoute("file-route");
}

exchange.getContext().addRouteFromTemplate(
"file-route", "file-template",
Map.of("folder", String.valueOf(LocalDate.now(;
});

from("direct:computeFile")
.id("compute-route")
.log("${body}");


Il giorno ven 1 mar 2024 alle ore 14:04 Jan Bares, WOOD & Co. <
jan.ba...@wood.cz> ha scritto:

> Hi,
>
> We need to read files from a folder,that contains current date. During
> quiet period after midnight we need to "switch" to the new folder. What are
> possible solutions? Essentially we need to change endpoint configuration on
> runtime at specific time. Our routes are configured using Java DSL.
>
> On March 1 the folder name is FILES/2024_03_01
> On March 2 the folder name will be FILES/2024_03_02
> ...
>
> Kind regards, Jan
>
> Jan Bares
> Head of Calypso development | IT Development
>
> Phone: +420 222 096 457
> Mobile: +420 776 333 676
> Email: jan.ba...@wood.cz
>
> WOOD & Company
> Palladium, n?m. Republiky 1079/1a, 110 00 Prague 1, Czech Republic |
> wood.cz
>
>
>
>
>
> 
> DISCLAIMER
> WOOD & Company Financial Services, a.s. and its branches are authorized
> and regulated by the CNB as Home State regulator and in Poland by the KNF,
> in Slovakia by the NBS, in Italy by the CONSOB and in the UK by the FCA as
> Host State regulators. For further information about WOOD & Co., its
> investment services, financial instruments and associated risks, safeguard
> client assets (incl. compensation schemes) and contractual relationship
> please see our website at www.wood.com under
> section Corporate Governance. Unless otherwise stated, this transmission is
> neither an offer nor the solicitation of an offer to sell or purchase any
> investment. All estimates, opinions and other information contained herein
> are subject to change without notice and are provided in good faith but
> without legal responsibility or liability. Opinion may be personal to the
> author and may not reflect the opinions of WOOD & Co. Communications from
> sales persons, sales traders or traders should not be regarded as
> investment research and may contain opinions or trading ideas which are
> different from WOOD & Co. investment research opinions. This e-mail and any
> attachments are confidential and may be privileged or otherwise protected
> from disclosure. If you are not a named addressee you must not use,
> disclose, distribute, copy, print or rely on this e-mail and any of its
> attachments. Please notify the sender that you have received this email by
> mistake by replying to the email, and then delete the email and any copies
> of it. Although WOOD & Co. routinely screens e-mails for viruses,
> addressees should scan this e-mail and any attachments for viruses. WOOD &
> Co. makes no representation or warranty as to the absence of viruses in
> this e-mail or any attachments. Please note that to ensure regulatory
> compliance and for the protection of our clients and business, we may
> monitor and read e-mails sent to and from our server(s).
>






DISCLAIMER
WOOD & Company Financial Services, a.s. and its branches are authorized and 
regulated by the CNB as Home State regulator and in Poland by the KNF, in 
Slovakia by the NBS, in Italy by the CONSOB and in the UK by the FCA as Host 
State regulators. For further information about WOOD & Co., its investment 
services, financial instruments and associated risks, safeguard client assets 
(incl. compensation schemes) and contractual relationship please see our 
website at www.wood.com under section Corporate 
Governance. Unless otherwise stated, this transmission is neither an offer nor 
the solicitation of an offer to sell or purchase any investment. All estimates, 
opinions and other information contained herein are subject to change without 
notice and are provided in good faith but without legal responsibility or 
liability. Opinion may be personal to the author and may not reflect the 
opinions of WOOD & Co. Communications from sales persons, sales traders

Re: Reconfigure incoming file endpoint to follow current date

2024-03-01 Thread Federico Mariani

Hi, I'd use a quartz scheduler and a route template, something like this:


routeTemplate("file-template")
.templateParameter("folder")
.from("file://data/{{folder}}")
.to("direct:computeFile");

from("quartz:scheduler?cron=0+0+12+*+*+?")
.id("timer-route")
.process(exchange -> {
if (exchange.getContext().getRoute("file-route") != null) {

exchange.getContext().getRouteController().stopRoute("file-route");
exchange.getContext().removeRoute("file-route");
}

exchange.getContext().addRouteFromTemplate(
"file-route", "file-template",
Map.of("folder", String.valueOf(LocalDate.now(;
});

from("direct:computeFile")
.id("compute-route")
.log("${body}");


Il giorno ven 1 mar 2024 alle ore 14:04 Jan Bares, WOOD & Co. <
jan.ba...@wood.cz> ha scritto:

> Hi,
>
> We need to read files from a folder,that contains current date. During
> quiet period after midnight we need to "switch" to the new folder. What are
> possible solutions? Essentially we need to change endpoint configuration on
> runtime at specific time. Our routes are configured using Java DSL.
>
> On March 1 the folder name is FILES/2024_03_01
> On March 2 the folder name will be FILES/2024_03_02
> ...
>
> Kind regards, Jan
>
> Jan Bares
> Head of Calypso development | IT Development
>
> Phone: +420 222 096 457
> Mobile: +420 776 333 676
> Email: jan.ba...@wood.cz
>
> WOOD & Company
> Palladium, n?m. Republiky 1079/1a, 110 00 Prague 1, Czech Republic |
> wood.cz
>
>
>
>
>
> 
> DISCLAIMER
> WOOD & Company Financial Services, a.s. and its branches are authorized
> and regulated by the CNB as Home State regulator and in Poland by the KNF,
> in Slovakia by the NBS, in Italy by the CONSOB and in the UK by the FCA as
> Host State regulators. For further information about WOOD & Co., its
> investment services, financial instruments and associated risks, safeguard
> client assets (incl. compensation schemes) and contractual relationship
> please see our website at www.wood.com under
> section Corporate Governance. Unless otherwise stated, this transmission is
> neither an offer nor the solicitation of an offer to sell or purchase any
> investment. All estimates, opinions and other information contained herein
> are subject to change without notice and are provided in good faith but
> without legal responsibility or liability. Opinion may be personal to the
> author and may not reflect the opinions of WOOD & Co. Communications from
> sales persons, sales traders or traders should not be regarded as
> investment research and may contain opinions or trading ideas which are
> different from WOOD & Co. investment research opinions. This e-mail and any
> attachments are confidential and may be privileged or otherwise protected
> from disclosure. If you are not a named addressee you must not use,
> disclose, distribute, copy, print or rely on this e-mail and any of its
> attachments. Please notify the sender that you have received this email by
> mistake by replying to the email, and then delete the email and any copies
> of it. Although WOOD & Co. routinely screens e-mails for viruses,
> addressees should scan this e-mail and any attachments for viruses. WOOD &
> Co. makes no representation or warranty as to the absence of viruses in
> this e-mail or any attachments. Please note that to ensure regulatory
> compliance and for the protection of our clients and business, we may
> monitor and read e-mails sent to and from our server(s).
>

Re: using Camel with CloudKarafka

2024-03-01 Thread Chirag

That is unfortunate.
CloudKarafka free tier allowed to get a kafka instance in about two minutes
on the web simplifying prototyping.



On Fri, Mar 1, 2024, 01:05 Claus Ibsen  wrote:

> Hi
>
> Just a caution that the company sent out this EOL announcement
> https://www.cloudkarafka.com/blog/end-of-life-announcement.html
>
> On Fri, Mar 1, 2024 at 2:20 AM Chirag  wrote:
>
> > 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
> >
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Reconfigure incoming file endpoint to follow current date

2024-03-01 Thread Jan Bares, WOOD & Co.

Hi,

We need to read files from a folder,that contains current date. During quiet 
period after midnight we need to "switch" to the new folder. What are possible 
solutions? Essentially we need to change endpoint configuration on runtime at 
specific time. Our routes are configured using Java DSL.

On March 1 the folder name is FILES/2024_03_01
On March 2 the folder name will be FILES/2024_03_02
...

Kind regards, Jan

Jan Bares
Head of Calypso development | IT Development

Phone: +420 222 096 457
Mobile: +420 776 333 676
Email: jan.ba...@wood.cz

WOOD & Company
Palladium, n?m. Republiky 1079/1a, 110 00 Prague 1, Czech Republic | wood.cz






DISCLAIMER
WOOD & Company Financial Services, a.s. and its branches are authorized and 
regulated by the CNB as Home State regulator and in Poland by the KNF, in 
Slovakia by the NBS, in Italy by the CONSOB and in the UK by the FCA as Host 
State regulators. For further information about WOOD & Co., its investment 
services, financial instruments and associated risks, safeguard client assets 
(incl. compensation schemes) and contractual relationship please see our 
website at www.wood.com under section Corporate 
Governance. Unless otherwise stated, this transmission is neither an offer nor 
the solicitation of an offer to sell or purchase any investment. All estimates, 
opinions and other information contained herein are subject to change without 
notice and are provided in good faith but without legal responsibility or 
liability. Opinion may be personal to the author and may not reflect the 
opinions of WOOD & Co. Communications from sales persons, sales traders or 
traders should not be regarded as investment research and may contain opinions 
or trading ideas which are different from WOOD & Co. investment research 
opinions. This e-mail and any attachments are confidential and may be 
privileged or otherwise protected from disclosure. If you are not a named 
addressee you must not use, disclose, distribute, copy, print or rely on this 
e-mail and any of its attachments. Please notify the sender that you have 
received this email by mistake by replying to the email, and then delete the 
email and any copies of it. Although WOOD & Co. routinely screens e-mails for 
viruses, addressees should scan this e-mail and any attachments for viruses. 
WOOD & Co. makes no representation or warranty as to the absence of viruses in 
this e-mail or any attachments. Please note that to ensure regulatory 
compliance and for the protection of our clients and business, we may monitor 
and read e-mails sent to and from our server(s).

Svar: Re: What happened to HTTP component OAuth support?

2024-03-01 Thread Mikael Andersson Wigander

Hi thanks

No need, the documentation is now updated with samples and explanations.

/M

Den 1 mars 2024 kl 13:27, Claus Ibsen <[claus.ib...@gmail.com](mailto:Den 1 
mars 2024 kl 13:27, Claus Ibsen < skrev:

> Hi
>
> You are welcome to look further, it could be due to http client v4 -> v5
> upgrade that causes major refactor.
> And as such this feature may need to be implement again. If so you are
> welcome to help. Create a JIRA and see how to do that.
>
> On Mon, Feb 19, 2024 at 12:22 PM Mikael Andersson Wigander
>  wrote:
>
>> Hi
>>
>> As of release 4.2 there’s support for OAuth in the http component but
>> nowhere to be found on how to use it.
>>
>> CAMEL-18637
>>
>> all I can find is a OAuth2ClientConfigurer class.
>>
>> /M
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2

Re: What happened to HTTP component OAuth support?

2024-03-01 Thread Claus Ibsen

Hi

You are welcome to look further, it could be due to http client v4 -> v5
upgrade that causes major refactor.
And as such this feature may need to be implement again. If so you are
welcome to help. Create a JIRA and see how to do that.

On Mon, Feb 19, 2024 at 12:22 PM Mikael Andersson Wigander
 wrote:

> Hi
>
> As of release 4.2 there’s support for OAuth in the http component but
> nowhere to be found on how to use it.
>
> CAMEL-18637
>
> all I can find is a OAuth2ClientConfigurer class.
>
> /M

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

Camel JMS / Move failing message to DLQ queue

2024-03-01 Thread Ephemeris Lappis

Hello.

For almost all our JMS consumer routes, we didn't need to move
messages to a DLQ queue : for now only redelivery is handled to avoid
repeated errors with something like that on the routes :


java.lang.Exception


false



Now, for some cases we need to move a failing message to the DLQ that
our ActiveMQ uses when its processing is failing.

For some "transacted routes", message read/write operations are rolled
back on error, and messages are already moved to the DLQ.

What's the simplest way to do it for "not transacted" routes ?

Thanks for your help.

Regards.

Re: Reconfigure incoming file endpoint to follow current date

Re: using Camel with CloudKarafka

Re: Reconfigure incoming file endpoint to follow current date

Re: Reconfigure incoming file endpoint to follow current date

Re: using Camel with CloudKarafka

Reconfigure incoming file endpoint to follow current date

Svar: Re: What happened to HTTP component OAuth support?

Re: What happened to HTTP component OAuth support?

Camel JMS / Move failing message to DLQ queue

9 matches

Site Navigation

Mail list logo

Footer information