camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernard Ligny (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-11217) ExchangePattern issue with direct-vm component
Date Fri, 28 Apr 2017 07:16:04 GMT

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

Bernard Ligny updated CAMEL-11217:
----------------------------------
    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) at Camel User forum:
http://camel.465427.n5.nabble.com/Body-lost-with-intra-context-calls-using-direct-vm-component-td5798327.html


  was:
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 exaemple) at Camel User forum:
http://camel.465427.n5.nabble.com/Body-lost-with-intra-context-calls-using-direct-vm-component-td5798327.html



> 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
>
> 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) at 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.3.15#6346)

Mime
View raw message