[jira] [Comment Edited] (CAMEL-7778) EndpointRegistry in camel-core that allows refer endpoints using and logical id, like you can do in spring

["Claus Ibsen (JIRA)" <ji...@apache.org>]

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

Claus Ibsen edited comment on CAMEL-7778 at 8/9/15 8:25 AM:
------------------------------------------------------------

You can use @EndpointInject in your route builder classes, though they dont allow that nice id association.


was (Author: davsclaus):
You can use @EndpointInject in your route builder classes. 

> EndpointRegistry in camel-core that allows refer endpoints using and logical id, like you can do in spring
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-7778
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7778
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core
>    Affects Versions: 2.12.0
>            Reporter: Serge Smertin
>            Assignee: Claus Ibsen
>             Fix For: 2.16.0
>
>
> Generally, it's more efficient/loosely coupled to send to endpoint aliases, so we might change implementation of endpoint without changing the code:
> {code}
>     // in cases of dynamic routing
>     producer.asyncSend("specificMessageChannel", new Processor() {
>         ...
>     });
> {code}
> It's possible to do it through Spring DSL, but impossible to register endpoints from route builder if we use spring. Also it is easier to configure number of consumers and etc for endpoints. 
> {code}
> <endpoint id="specificMessageChannel" uri="seda:internalProcessing?concurrentConsumers=8" />
> {code}
> JndiRegistry has "bind" method and ApplicationContextAwareRegistry does not have it.
> Another use-case for that is camel-test component



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)