Hi
This is expected, the direct:start route gets inlined into rest-dsl and is
not an independent route, you can call from elsewhere.
On Thu, Nov 21, 2024 at 10:51 AM Remco Schoen <re...@dieselwalm.nl> wrote:
> We were doing some testing now Quarkus 3.15.2 has been released with the
> Camel LTS version 4.8.1 and we found some unexpected behaviour with the
> change of the default for inlineRoutes.
>
> We have a setup like this and with the changed default we get an error
> after the timeout from the timer route: No consumers available on endpoint:
> direct://start. Calling the same route via rest is successful.
>
> rest()
> .get("start")
> .to("direct:start")
> ;
>
>
> from(timer("start").repeatCount(1).delay(0))
> .routeId("startTimer")
> .to("direct:start")
> ;
>
> from("direct:start")
> .routeId("start")
> .log("Hello world!")
> .setBody().constant("{\"status\": \"SUCCESS\"}")
> ;
>
> If we change the setting of inlineRoutes to the old default value false,
> it works from both routes.
>
> It also doesn't show up in the list of started routes:
>
> Routes startup (total:2 rest-dsl:1)
> Started startTimer (timer://start)
> Started start (rest://get:start)
>
>
> Should these routes still work with the new default?
>
> I created and attached a simple test project that shows the behaviour.
>
>
> With kind regards,
>
> Remco Schoen
>
>
>
--
Claus Ibsen
-----------------
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
