You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by yuruki <gi...@git.apache.org> on 2015/04/05 12:08:00 UTC

[GitHub] camel pull request: CAMEL-7833 InOnly and InOut routes as Observab...

GitHub user yuruki opened a pull request:

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

    CAMEL-7833 InOnly and InOut routes as Observable<Exchange> sequences

    Basic InOnly and InOut routes seem to just work as Observable<Exchange> sequences.
    
    To be honest, I don't quite understand why the response is correctly propagated to consumer automatically without an explicit call to UnitOfWork.done() and friends...

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

    $ git pull https://github.com/yuruki/camel camel-rx-routes

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

    https://github.com/apache/camel/pull/467.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 #467
    
----
commit 88417414d3679178adbe9abd8b3b4bde99c37119
Author: Jyrki Ruuskanen <yu...@kotikone.fi>
Date:   2015-04-05T09:59:12Z

    InOnly and InOut routes as Observable<Exchange> sequences

----


---
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.
---

[GitHub] camel pull request: CAMEL-7833 InOnly and InOut routes as Observab...

Posted by yuruki <gi...@git.apache.org>.
Github user yuruki closed the pull request at:

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


---
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.
---