You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2022/09/02 08:54:00 UTC

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

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

Claus Ibsen updated CAMEL-7778:
-------------------------------
    Fix Version/s: 4.0
                       (was: Future)

> 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
>            Priority: Major
>             Fix For: 4.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
(v8.20.10#820010)