Return-Path: X-Original-To: apmail-camel-issues-archive@minotaur.apache.org Delivered-To: apmail-camel-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 69156DC05 for ; Tue, 25 Sep 2012 07:39:12 +0000 (UTC) Received: (qmail 76541 invoked by uid 500); 25 Sep 2012 07:39:12 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 76025 invoked by uid 500); 25 Sep 2012 07:39:09 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 75970 invoked by uid 99); 25 Sep 2012 07:39:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Sep 2012 07:39:07 +0000 Date: Tue, 25 Sep 2012 18:39:07 +1100 (NCT) From: "Willem Jiang (JIRA)" To: issues@camel.apache.org Message-ID: <628141541.120896.1348558747773.JavaMail.jiratomcat@arcas> In-Reply-To: <805978311.91438.1347953288689.JavaMail.jiratomcat@arcas> Subject: [jira] [Resolved] (CAMEL-5622) CxfConsumer should avoid using the async invocation with the decouple endpoints transport MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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