[jira] [Resolved] (CAMEL-11217) ExchangePattern issue with direct-vm component

["Claus Ibsen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-11217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-11217.
---------------------------------
    Resolution: Later
      Assignee: Claus Ibsen

Try with newest version as the direct-vm component has been improved since.

> ExchangePattern issue with direct-vm component
> ----------------------------------------------
>
>                 Key: CAMEL-11217
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11217
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.18.3
>            Reporter: Bernard Ligny
>            Assignee: Claus Ibsen
>
> 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



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)