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
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
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:
Hello Mikael
I believe that component configuration in application.properties should
work, so don't need to duplicate in YAML:
camel.component.jira.jira-url=URL
camel.component.jira.password=PASSWORD
Marat
On Thu, Feb 29, 2024 at 9:00 AM Mikael Koskinen wrote:
> Hi,
>
> Property
Hi,
Property placeholders allow us to reuse single things like Jira username
and password. But is there a concept in Camel that works with Camel YAML &
Karavan where we could reuse "named" endpoint definitions?
So the idea is that I could (hopefully in application.properties) define
something
Hi
Ad 1)
https://issues.apache.org/jira/browse/CAMEL-20492
Ad 2)
Whats the use for this this, can you provide more detail and some example
Ad 3)
You can write a custom processor / ben / interceptor and do your own
validation - no need for pojo and all those crazy validation annotations.
On
