Hi,
Great to hear, thank you!
On Tuesday, June 13, 2023, Claus Ibsen wrote:
> Hi
>
> Okay so your use-cases will then work out of the box in 3.20.6 onwards.
>
> On Tue, Jun 13, 2023 at 2:59 PM Claus Ibsen wrote:
>
> > Hi
> >
> > I tracked down what I consider a little bug
> > https://issues.ap
Hi
Okay so your use-cases will then work out of the box in 3.20.6 onwards.
On Tue, Jun 13, 2023 at 2:59 PM Claus Ibsen wrote:
> Hi
>
> I tracked down what I consider a little bug
> https://issues.apache.org/jira/browse/CAMEL-19443
>
> With the bug fix then this use-case from Mikael works on 3.2
Hi
I tracked down what I consider a little bug
https://issues.apache.org/jira/browse/CAMEL-19443
With the bug fix then this use-case from Mikael works on 3.20.x as well.
The other ticket CAMEL-19411 to regard kameelts as "black box" still
stands. However this is maybe a different concept that re
Hi
Yes its a good idea to make kamelets like a "black box" and they should not
have any error handling (noErrorHandler), then
they are like calling a component.
We can add an option to the kamelet component that can turn on old
behaviour for users that somehow want the old way (just in case).
htt
Hi,
Thank you for the replies. It would be great if the Kamelets could
inherit the configuration as modifying the Kamelet specifications is
mostly out of the question as we're using the stock/built-in Kamelets,
like http-sink etc. I think this is quite a big issue (for me at least
:)) as it means
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
>
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
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 (w
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'
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-
10 matches
Mail list logo
