[
https://issues.apache.org/jira/browse/CAMEL-11604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16102105#comment-16102105
]
ASF GitHub Bot commented on CAMEL-11604:
----------------------------------------
GitHub user Rajani-K opened a pull request:
https://github.com/apache/camel/pull/1852
CAMEL-11604: Added new method expectedPropertyValuesReceivedInAnyOrder
Submitting PR for CAMEL-11604
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Rajani-K/camel master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1852.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 #1852
----
commit ad304058c794ee8b91a57c9b8b190a37e9e41650
Author: Rajani-K <[email protected]>
Date: 2017-07-26T18:45:15Z
CAMEL-11604: Added new method expectedPropertyValuesReceivedInAnyOrder
----
> New method expectedPropertyValuesReceivedInAnyOrder in MockEndpoint
> -------------------------------------------------------------------
>
> Key: CAMEL-11604
> URL: https://issues.apache.org/jira/browse/CAMEL-11604
> Project: Camel
> Issue Type: Improvement
> Components: camel-test
> Affects Versions: 2.19.1
> Reporter: Saravanakumar Selvaraj
> Priority: Minor
>
> MockEndpoint.expectedPropertyReceived always expects the property in the
> first exchange in the endpoint. So it does not function correctly when the
> endpoint expects more than one message exchange.
> There can be a new method introduced in MockEndpoint like
> expectedPropertyValuesReceivedInAnyOrder and this can be similar to
> expectedHeaderValuesReceivedInAnyOrder.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)