[
https://issues.apache.org/activemq/browse/CAMEL-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51451#action_51451
]
Claus Ibsen commented on CAMEL-1574:
------------------------------------
See nabble:
http://www.nabble.com/Messages-not-being-delivered-once-SEDA-concurrentConsumers-set-td23176637.html
> Registering Endpoint by URI - Add strategy to Component to allow components
> to construct key
> --------------------------------------------------------------------------------------------
>
> Key: CAMEL-1574
> URL: https://issues.apache.org/activemq/browse/CAMEL-1574
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core
> Affects Versions: 1.6.0, 2.0-M1
> Reporter: Claus Ibsen
>
> URIs is the preferred means to identify and lookup endpoints. The general
> rule of thumb is that you must use the exact same URI every time to lookup
> the same endpoint.
> That can confuse for components that has a logical key that represents the
> same endpoint. For example
> - {{seda:foo}}
> - {{seda:foo?concurrentConsumers=2}}
> In peoples mind its the same endpoint, its the seda *foo* queue. But in Camel
> its 2 different endpoints. So you cannon link them together. So this wont
> work:
> {code}
> from(x)....to("seda:foo");
> ...
> from("seda:foo?concurrentConsumers=2").to(z);
> {code}
> So if we add some strategy to component so it can construct a the logical key
> for its endpoint.
> For instance the SedaComponent would be able to return the key: {{seda:foo}}
> for whether or without the concurrentConsumer option. Its the same logical
> endpoint.
> The same will apply for JMS component and others.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
