Pipeline createNewExchange method copies the previous exchange and sets the
previous Out to current In. However it leaves the current Out to previous
Out ??
I fixed this by these two lines
answer.getOut().setBody(null);
answer.getOut().setHeaders(null);
However the PipelineTest assert fails... incorrect assertion IMHO of the
result from a template send coming back with the out populated... only the
mock:result should have the out populated and that assertion of the tests
still stands
Could someone take a look and opine?
Nicky
--
View this message in context:
http://www.nabble.com/Pipeline-createNewExchange-tf4609319s22882.html#a13162515
Sent from the Camel - Development mailing list archive at Nabble.com.
