I also seem to recall that routeTemplates haven't all functionality from
Kamelets, and you can't call all routeTemplates exactly the same from the
Kamelet component, but maybe this is not a limitation anymore.
btw In my own runtime (Assimbly) I do load all Kamelets by default, so they
are
Yeah, calling a Kamelet has the advantage that the subroute is dynamically
created.
- Still need the to, not a separate EIP.
- Beginners would not search for "Kamelet", but function would be more
common
- You still need a from statement within the Kamelet
- Kamelet is not really part of the
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:
>
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:
>
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",
Hello.
If it's confirmed, it means that I can't retrieve the actual resulting
queue the message is sent to ?
I'd need to retrieve it in some event notifiers, out of the Camel
routes code, that spies all the exchanges, the same way I do for
generated files retrieving the header
