[
https://issues.apache.org/jira/browse/CAMEL-10190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395496#comment-15395496
]
Claus Ibsen commented on CAMEL-10190:
-------------------------------------
This would require the resolvers to use that -suffix as fallback in their
lookup by name, which can all be done in camel-core.
> Fallback lookup components, data-formats and languages using suffix in name
> to avoid clash
> ------------------------------------------------------------------------------------------
>
> Key: CAMEL-10190
> URL: https://issues.apache.org/jira/browse/CAMEL-10190
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
>
> You can define a component as a spring/blueprint id named "jms" etc for the
> jms component.
> But we have some components that has a naming clash with data format or
> language, such as avro, mvel, and some others.
> It would have been good if we supported looking up a component using a
> fallback naming convention, eg jms -> jms-component. And for dataformat avro
> -> avro-dataformat, and so on.
> Then end users can define those <bean> with that naming convention to avoid
> clashes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
