[
https://issues.apache.org/jira/browse/CAMEL-18189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17716310#comment-17716310
]
Grzegorz Grzybek commented on CAMEL-18189:
------------------------------------------
bq. yaml-dsl already have -beans today where you can setup beans
{{org.apache.camel.dsl.yaml.deserializers.NamedBeanDefinition}} was indeed
added with CAMEL-16584.
But there's also
{{org.apache.camel.xml.in.ModelParser#doParseBeanDefinition()}} which deals
with {{org.apache.camel.model.BeanDefinition}}
But these look like the good old _beans_ you can use as processors and which
are configured in {{org.apache.camel.model.ProcessorDefinition}} (and derived
classes)...
I'm not sure how easy it'd be allow top level {{<bean>}} elements. On the other
hand it wouldn't be wise to duplicate the beans... Still thinking (you know - i
always have to re-learn Camel after getting back to its core after some
time...).
> camel-core - XML DSL <beans> for custom beans and to embed Camel routes in
> same file
> ------------------------------------------------------------------------------------
>
> Key: CAMEL-18189
> URL: https://issues.apache.org/jira/browse/CAMEL-18189
> Project: Camel
> Issue Type: New Feature
> Components: camel-core-xml
> Reporter: Claus Ibsen
> Assignee: Grzegorz Grzybek
> Priority: Major
> Fix For: Future
>
>
> We may consider a root tag such as <beans> that are Camel specific and
> therefore works on all runtimes, where we can have basic support for
> dependency injection with <bean> and also embed Camel <routes> and <rests>
> and <routeConfigurations> and <routeTemplates> etc all in the same file.
> This can be handy for low-code projects with Camel K / Camel JBang.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
