On Thu, Feb 16, 2017 at 11:11 AM, Tristan Hill <tris...@me.uk.eu.org> wrote:
> On 2017-02-16 09:52, Claus Ibsen wrote:
>> What version of Camel do you use, and what kind of Camel component is
>> the message originally from
> I'm using 2.18.2 with the File component. The other user I referenced
> mentions 2.12.1 also with the File component.
>> On Wed, Feb 15, 2017 at 3:22 PM, Tristan Hill <tris...@me.uk.eu.org>
>>> Perhaps in the DefaultUnitOfWork constructor the exchange should be set
>>> on originalInMessage for this to work?
Can you log a JIRA.
The copy logic need a way to copy over the exchange reference as well.
> Further on this, it appears message.setExchange is not on the Message
> interface but a public method on MessageSupport. Would it make sense to
> have it on the interface as well so the object doesn't need to cast?
No you should not change exchange on a message, so no setter.
Camel in Action 2: https://www.manning.com/ibsen2