[
https://issues.apache.org/jira/browse/CAMEL-11105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15956379#comment-15956379
]
ASF GitHub Bot commented on CAMEL-11105:
----------------------------------------
GitHub user onders86 opened a pull request:
https://github.com/apache/camel/pull/1595
CAMEL-11105 - disable endpoint to be singleton
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/onders86/camel CAMEL-11105
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1595.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1595
----
commit 06e15faad98b75b387125c3f12c2a82d18ee157f
Author: onders86 <[email protected]>
Date: 2017-04-05T06:22:44Z
CAMEL-11105 - disable endpoint to be singleton
----
> camel-eventadmin does not allow multiple consumers with the same URI
> --------------------------------------------------------------------
>
> Key: CAMEL-11105
> URL: https://issues.apache.org/jira/browse/CAMEL-11105
> Project: Camel
> Issue Type: Improvement
> Components: osgi
> Reporter: David Franke
> Priority: Minor
>
> I have an application which uses the OSGi EventAdmin to send events when
> something important happens. I want to register several EventHandlers for the
> same event topic to perform different tasks.
> Using the eventadmin endpoint I can register an endpoint that listens on the
> OSGi Events.
> However if I try to define several routes with the same event topic I get the
> following exception:
> {{org.apache.camel.FailedToStartRouteException: Failed to start route
> myapp.example.custom-events because of Multiple consumers for the same
> endpoint is not allowed: Endpoint[eventadmin://mycustom/events/*]}}
> I think it should be possible to register several Endpoints for the same
> Event topic as it is possible to have several EventHandlers listening on the
> same topic.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
