[
https://issues.apache.org/activemq/browse/CAMEL-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52459#action_52459
]
Claus Ibsen commented on CAMEL-1756:
------------------------------------
Maybe we should add some flag to an endpoint whether it supports *same
endpoint* but with different parameters.
In the seda case it should not do this as its confusing so we could do
- seda:foo
And when you do a getEndpoint with
- seda:foo?concurrentConsumers=5
You will get an exception that seda:foo is already registered.
> getEndpoint() should match for singleton endpoints even if url does not
> contain params
> --------------------------------------------------------------------------------------
>
> Key: CAMEL-1756
> URL: https://issues.apache.org/activemq/browse/CAMEL-1756
> Project: Apache Camel
> Issue Type: Improvement
> Affects Versions: 1.6.1, 2.0-M2
> Reporter: Hadrian Zbarcea
> Assignee: Hadrian Zbarcea
> Fix For: 1.6.2, 2.0.0
>
>
> When one uses endpoint injection, if the url does not exactly match, the
> CamelContext will not find the endpoint (and create a new one).
> I think singleton Endpoint(s) should not be registered with the full url,
> just with the url stripped of parameters, since they are mostly configuration
> and not necessarily relevant to the producer. Also if the configuration of a
> singleton endpoint will change slightly, an update/recompile of the producer
> code is no longer necessary.
> I cannot think of a situation in which this improvement would cause problems.
> I have a fix for this but I'll wait a few days. Thoughts?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
