Closed NickTheArchitect closed 3 years ago
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
0 out of 2 committers have signed the CLA.
:x: Nick James
:x: NickTheArchitect
Hey @NickTheArchitect - sorry - this got stuck. Do you agree to close it as it is outdated?
The Request Reply pattern is documented at http://camel.apache.org/request-reply.html. Note the following discussion about InOut pattern and using the in or out message: http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html
Fix:
Get the result of the Exchange from the Exchange's out message (to enable the InOut pattern) which will internally get the in message if the out isn't present
Update the tests so that the first of the original tests uses a "real" Camel Exchange (with mock CamelContext), to show that the new call to send.getOut() works exactly like the original call to send.getIn() when there is no "out" message available.
Add similar test which shows that an "out" message gets used if it exists.
Fix the rest of the tests to "know" that getOut() is called instead of getIn().
Result My test code now has a Camel flavor ServiceTask like this (note the exchangePattern and the resultVariable): `