You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "James Netherton (Jira)" <ji...@apache.org> on 2023/02/21 14:34:00 UTC

[jira] [Created] (CAMEL-19080) camel-yaml-dsl: Improve support for configuring gloabal options, thread pool profiles etc

James Netherton created CAMEL-19080:
---------------------------------------

             Summary: 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


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)