[jira] [Updated] (CAMEL-7778) BindableRegistry interface with JndiRegistry and ApplicationContextAware implementations

["Serge Smertin (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-7778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Serge Smertin updated CAMEL-7778:
---------------------------------
    Affects Version/s: 2.12.0

> BindableRegistry interface with JndiRegistry and ApplicationContextAware implementations
> ----------------------------------------------------------------------------------------
>
>                 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
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> 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)