[CAMEL-11217] ExchangePattern issue with direct-vm component

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Later
• Affects Version/s: 2.18.3
• Component/s: camel-core
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Bernard Ligny
• Created: 28/Apr/17 07:14
• Updated: 20/Jul/17 08:09
• Resolved: 20/Jul/17 08:09

Description

A same route definition with a In Only exchange behaves differently depending on whether the call to the sub-route (of the same CamelContext) is done using direct or direct-vm component.

My personal conclusion is that the ExchangePattern for the sub-route invokation seems to vary:

• In&Out when "direct:" used in to uri
• inherited from "parent" exchange (=InOnly) when "direct-vm:" used in to uri

See full problem description (and example) in Camel User forum:
http://camel.465427.n5.nabble.com/Body-lost-with-intra-context-calls-using-direct-vm-component-td5798327.html