You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by urbanenomad <gi...@git.apache.org> on 2016/04/26 19:25:41 UTC

[GitHub] camel pull request: Fix over writing previous addToResult calls

GitHub user urbanenomad opened a pull request:

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

    Fix over writing previous addToResult calls

    I noticed that multiple calls to the addToResult method in the org.apache.camel.component.aws.ddb.AbstractDdbCommand within the child class org.apache.camel.component.aws.ddb.ScanCommand caused the next call to over write the previous calls to addToResult in the header results.  The end result is only having the last result value returned in the out message which is the SCANNED_COUNT header.
    
    The exchange.getOut() already passes back the "In" Message or creates a new Message object if no out message exists does not need to copy over the "In" message into the "Out" message.

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

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

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

    https://github.com/apache/camel/pull/961.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 #961
    
----
commit f9c65d0c621206a316ea81a9b4e3164d009dbe1c
Author: Won <gi...@urbanenomad.com>
Date:   2016-04-26T17:09:18Z

    Fix over writing previous addToResult calls
    
    I noticed that multiple calls to the addToResult method in the org.apache.camel.component.aws.ddb.AbstractDdbCommand within the child class org.apache.camel.component.aws.ddb.ScanCommand caused the next call to over write the previous calls to addToResult in the header results.  The end result is only having the last result value returned in the out message which is the SCANNED_COUNT header.
    
    The exchange.getOut() already passes back the "In" Message or creates a new Message object if no out message exists does not need to copy over the "In" message into the "Out" message.

----


---
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: Fix over writing previous addToResult calls

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

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


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