camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-10190) Fallback lookup components, data-formats and languages using suffix in name to avoid clash
Date Thu, 28 Jul 2016 07:13:20 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-10190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15397158#comment-15397158
] 

ASF GitHub Bot commented on CAMEL-10190:
----------------------------------------

Github user nicolaferraro closed the pull request at:

    https://github.com/apache/camel/pull/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
>             Fix For: 2.18.0
>
>
> 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)

Mime
View raw message