You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2012/09/18 09:28:08 UTC
[jira] [Created] (CAMEL-5622) CxfConsumer should avoid using the
async invocation with the decouple endpoints transport
Willem Jiang created CAMEL-5622:
-----------------------------------
Summary: CxfConsumer should avoid using the async invocation with the decouple endpoints transport
Key: CAMEL-5622
URL: https://issues.apache.org/jira/browse/CAMEL-5622
Project: Camel
Issue Type: Improvement
Components: camel-cxf
Reporter: Willem Jiang
Assignee: Willem Jiang
Fix For: 2.9.4, 2.11.0, 2.10.2
As the decouple endpoint transport already switch the thread and we cannot leverage the continuation to provide the async invocation any more. So we need to disable the async invocation in this situation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-5622) CxfConsumer should avoid using the
async invocation with the decouple endpoints transport
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CAMEL-5622.
---------------------------------
Resolution: Fixed
Applied patch into trunk, camel-2.10.x and camel-2.9.x branches.
> CxfConsumer should avoid using the async invocation with the decouple endpoints transport
> -----------------------------------------------------------------------------------------
>
> Key: CAMEL-5622
> URL: https://issues.apache.org/jira/browse/CAMEL-5622
> Project: Camel
> Issue Type: Improvement
> Components: camel-cxf
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 2.9.4, 2.11.0, 2.10.2
>
>
> As the decouple endpoint transport already switch the thread and we cannot leverage the continuation to provide the async invocation any more. So we need to disable the async invocation in this situation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira