[
https://issues.apache.org/jira/browse/CAMEL-19080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693497#comment-17693497
]
Claus Ibsen commented on CAMEL-19080:
-------------------------------------
The DSL is only for routes / route-configurations etc - eg the stuff in the
camel-core-model.
General configuration is done via camel-main, application.properties, or java
apis on camel context etc.
This kind should not be in DSL.
> camel-yaml-dsl: Improve support for configuring gloabal options, thread pool
> profiles etc
> -----------------------------------------------------------------------------------------
>
> Key: CAMEL-19080
> URL: https://issues.apache.org/jira/browse/CAMEL-19080
> Project: Camel
> Issue Type: Improvement
> Components: camel-yaml-dsl
> Reporter: James Netherton
> Priority: Major
>
> I was browsing through the YAML DSL schema and noticed there are a few things
> that can be defined, but don't actually end up being used / configured in a
> way that makes them usable.
> * transformations
> * validations
> * thread pool profile
> * package scan
> * global options
> E.g consider the following. It parses fine, but there's nothing that actually
> ensures the global options are set on the {{CamelContext}}.
> {code}
> - global-options:
> global-option:
> - key: foo
> value: bar
> {code}
> The same is true for the other options mentioned above.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
