Claus Ibsen created CAMEL-14568:

             Summary: camel component configurations include configuration 
classes in documentation
                 Key: CAMEL-14568
             Project: Camel
          Issue Type: Improvement
          Components: build system
            Reporter: Claus Ibsen
             Fix For: 3.2.0

We should make the build system generate camel component json metadata with 
nested configuration options, like we do for endpoints.

For example some components allow to set a global configuration class which is 
then copied and then per endpoint can override individual settings. This class 
is annotated with @UriParams and the metadata tool generate these options 
included for endpoint.

For component we only refer to the configuration class itself and not its 

Then the options table in the generated docs should also be updated for 
components to be more similar to what we do for SB, eg with as prefix. Then its the same way to configure this 
with SB, Main, Quarkus, Kafka Connectors and whatnot. And for Java 
configuration you still have just java code. Also the componentdsl tool needs 
to be updated to support this.

This message was sent by Atlassian Jira

Reply via email to