1 see the DSL doc - its not much doc as its just a human description and has no logic 2 no 3 no
This is not a desired feature and to APIs and controllers to manage lifecycle of routes is already complex and vast and need to deal with many things. On Fri, Nov 17, 2023 at 10:58 AM ski n <raymondmees...@gmail.com> wrote: > OK, then another three questions (one less): > > 1. Do you have a link to the documentation on this feature (can find it, > only jgroups) > 2. Is an API for this (a new one or enhancement of routecontroller API) > planned > 3. If the API is not planned yet, should I make a Jira issue for this as > enhancement request? > > Raymond > > On Fri, Nov 17, 2023 at 9:07 AM Claus Ibsen <claus.ib...@gmail.com> wrote: > > > 1 2 3 yes > > 4 no > > > > > > > > On Fri, Nov 17, 2023 at 8:26 AM ski n <raymondmees...@gmail.com> wrote: > > > > > Recently, a “route group“ was added: > > > > > > https://issues.apache.org/jira/browse/CAMEL-11669 > > > > > > The ticket mentioned that the route group is a “logical group” that one > > or > > > more routes are attached to. Some questions about this new feature: > > > > > > 1. Is the syntax still the same as in the ticket? > > > 2. Is this already documented? > > > 3. Is this also part of Camel 4? (The fixed version is 3.22.0. Probably > > > this also added to Camel 4) > > > 4. Is there also an API for this feature (for example to retrieve the > > group > > > of a route, or to start/stop a complete group of routes). I have > similar > > > functionality in Assimbly (a group of routes is called a flow there) > and > > > would rather port this functionality to Camel 4 if if rich enough. > > > > > > What I currently do to manage a group of routes is to have routeid that > > is > > > build up like this: > > > > > > groupid_routeid > > > > > > Then I can stop a group like this: > > > > > > List<Route> routeList = getRoutesByFlowId(id); > > > > > > for (Route route : routeList) { > > > String routeId = route.getId(); > > > log.info("Stopping step | flowid=" + route.getId()); > > > routeController.stopRoute(routeId, stopTimeout, TimeUnit.SECONDS); > > > context.removeRoute(routeId); > > > if(route.getConfigurationId()!=null) { > > > removeRouteConfiguration(route.getConfigurationId()); > > > } > > > } > > > > > > The getRoutesByFlouwId gets the related routes for a group and then > loops > > > them one by one. This however with large groups can take a while. Would > > be > > > nice to do something like this: > > > > > > routeController.stopGroup("groupId") > > > > > > Raymond > > > > > > > > > -- > > Claus Ibsen > > ----------------- > > @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > > > -- Claus Ibsen ----------------- @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
