[
https://issues.apache.org/jira/browse/CAMEL-10190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396105#comment-15396105
]
ASF GitHub Bot commented on CAMEL-10190:
----------------------------------------
GitHub user nicolaferraro opened a pull request:
https://github.com/apache/camel/pull/1087
CAMEL-10190: Fallback lookup components, data-formats and languages using
suffix in name to avoid clash
I changed the behavior of the default, blueprint and OSGi resolvers to
introduce the fallback names.
I refactored all three resolvers to use a common Helper instead of
repeating the code.
Unit tests added. Executed all unit tests on all changed modules.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nicolaferraro/camel CAMEL-10190
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1087.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1087
----
----
> 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
> Assignee: Nicola Ferraro
>
> 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)
