[
https://issues.apache.org/jira/browse/CAMEL-20740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17843753#comment-17843753
]
Luca Burgazzoli commented on CAMEL-20740:
-----------------------------------------
Just for reference, I think at some point in the past we had a special
_configurations_ entry in spring boot, like:
{code}
# standard component
camel.component.sql.batch = 333
# custom sql component registered as {alias}
camel.component.sql.configurations.${alias}.batch = 444
{code}
> Allow to configure multiple components of same type in application.properties
> -----------------------------------------------------------------------------
>
> Key: CAMEL-20740
> URL: https://issues.apache.org/jira/browse/CAMEL-20740
> Project: Camel
> Issue Type: New Feature
> Components: camel-main
> Reporter: Claus Ibsen
> Priority: Major
> Fix For: 4.x
>
>
> See if we can make it easier to define 2 JMS or 2+ SQL components with their
> own configuration and do all of this via application.properties.
> The default camel.component.sql is for the default component only.
> So something
> camel.component.mysql.alias=sql
> camel.component.mysql.batch=123
> camel.component.oracle-db.alias=sql
> camel.component.oracle-db.batch=444
> So the name of the component needs to use a non OOTB component name and have
> an alias option that refers to the actual component.
> This does impact tooling as they dont understand these "fake components" so
> maybe we need to put this into another prefix to avoid confusion.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
