whole new component, just to overload
the createEndpoint() function. Anyway, thanks for your input, which confirms my
presumption.
Best regards
Jens
-Original Message-
From: Claus Ibsen
Sent: Dienstag, 10. Dezember 2024 14:59
To: users@camel.apache.org
Subject: Re: endpoint in io dsl
Hi
tag, 10. Dezember 2024 14:36
> To: users@camel.apache.org
> Subject: Re: endpoint in io dsl
>
> Hi
>
> is not supported in Camel DSL.
> It's a legacy from old Camel OSGi blueprint and the old spring xml
>
> On Tue, Dec 10, 2024 at 12:40 PM Kordowski, Jens
> wrot
Hi
We have a ticket about added it in the future, but it has some implications
(it's rarely in use) and only from the old legacy osgi world
https://issues.apache.org/jira/browse/CAMEL-19946
On Tue, Dec 10, 2024 at 2:35 PM Claus Ibsen wrote:
> Hi
>
> is not supported in Camel DSL.
> It's a lega
@camel.apache.org
Subject: Re: endpoint in io dsl
Hi
is not supported in Camel DSL.
It's a legacy from old Camel OSGi blueprint and the old spring xml
On Tue, Dec 10, 2024 at 12:40 PM Kordowski, Jens
wrote:
> Hello.
>
> Using Camel blueprint dsl, I was able to get hold of an endpoint,
Hi
is not supported in Camel DSL.
It's a legacy from old Camel OSGi blueprint and the old spring xml
On Tue, Dec 10, 2024 at 12:40 PM Kordowski, Jens
wrote:
> Hello.
>
> Using Camel blueprint dsl, I was able to get hold of an endpoint, e.g. an
> AMQP endpoint:
>
> id="MessageFlow_4_configura
Hello.
Using Camel blueprint dsl, I was able to get hold of an endpoint, e.g. an AMQP
endpoint:
...
By doing so, I could hand over that endpoint to a "endpoint configurator bean"
to manipulate that endpoint. In my particular case, I
