[
https://issues.apache.org/jira/browse/CAMEL-11547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092069#comment-16092069
]
Claus Ibsen commented on CAMEL-11547:
-------------------------------------
There is some limitations of this way, as now end users need to work with
xxxDefinition classes which they are not really using normally. Also they need
to use static import of that from class to get the easy DSL. And then they can
only do 1 route. Then to configure other things like error handler, data
formats etc then they can't really do this with the @Bean unless we start
adding stuff for that too.
I am just wondering if we end up shooting ourselves in the foot. I dont think
we should add this so quickly. The existing RouteBuilder classes is IMHO the
best way.
I suggest to hold you horse on this one, and maybe consider reverting or moving
to a branch this work, and then lets look at this in the future, or a bit
later. And if the code is kept then I would really suggest to mark it with
"This code is experimental and subject for change" so we have the freedom to
change it in the upcoming releases.
> camel-core: load route definitions from registry
> ------------------------------------------------
>
> Key: CAMEL-11547
> URL: https://issues.apache.org/jira/browse/CAMEL-11547
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Luca Burgazzoli
> Assignee: Luca Burgazzoli
> Priority: Minor
> Fix For: 2.20.0
>
>
> This would allow to write routes i.e. in spring boot like
> {code:java}
> import static RouteDefinitionHelper.from;
> @Bean
> RouteDefinition myRoute() {
> return from("...")
> .process(..)
> .to("...")
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
