camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jhberges <...@git.apache.org>
Subject [GitHub] camel pull request: Simplistic workaround for ...
Date Wed, 06 May 2015 14:47:20 GMT
GitHub user jhberges opened a pull request:

    https://github.com/apache/camel/pull/511

    Simplistic workaround for ...

    https://issues.apache.org/jira/browse/CAMEL-8460, that works for me.
    
    A bit difficult to write unit test for, since this requires multiple ApplicationContext
instances to have been started.
    
    I also would image there's a better way to implement this - perhaps by checking for existing
routes before adding them?
    I don't know, but this simple tweak works for us - so it's good enough for us, for now.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jhberges/camel master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/511.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 #511
    
----
commit f268a0c200a915d042d4d05b124e99a981ca60ea
Author: Jan-Helge Bergesen <jan.helgebergesen@free2.no>
Date:   2015-05-06T14:42:14Z

    Simplistic workaround for https://issues.apache.org/jira/browse/CAMEL-8460, that works
for me

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message