Return-Path: Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: (qmail 30184 invoked from network); 25 Aug 2008 07:38:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Aug 2008 07:38:50 -0000 Received: (qmail 52405 invoked by uid 500); 25 Aug 2008 07:38:49 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 52173 invoked by uid 500); 25 Aug 2008 07:38:48 -0000 Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list dev@cxf.apache.org Received: (qmail 52162 invoked by uid 99); 25 Aug 2008 07:38:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Aug 2008 00:38:48 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of freeman.fang@gmail.com designates 209.85.142.186 as permitted sender) Received: from [209.85.142.186] (HELO ti-out-0910.google.com) (209.85.142.186) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Aug 2008 07:37:50 +0000 Received: by ti-out-0910.google.com with SMTP id u5so883352tia.10 for ; Mon, 25 Aug 2008 00:38:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=zt3kUnqvJnoQUUzuQSmwQGNzyWvNAqHW2pQTQ/dbPrQ=; b=XZ3Sr7W2xBympfX7OBOP2CueNnpSjTwT0iXl+UW9ltva3tAvuveNOnOWN5jx4TyF4A XG0hl5tqUO9j2on7mkIffwVFKaYnAET1y/IqIFqHluL1/zF71sMmeWti5s+dGcE0dRYT h9uFVTz4MddHH7jm4MziFm+e45IIUC5+FBzpw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=WiTNtol4h229h5pF5wF3TcuXjbsCK3NUqK65eO6of5zWWvwOCEPcW6pzcH9MQBCDpW 4o/nLb+czIWEjWYMc6YvuiWkUlNCJ1cC4xymH6DKCfEQO9fL35uSRKQd5K7QHVOHMuQF 7JvLZDGJ6JxP4Kk+kVcq/bTUtTHMzLkgj3gTY= Received: by 10.110.20.17 with SMTP id 17mr4718203tit.12.1219649882392; Mon, 25 Aug 2008 00:38:02 -0700 (PDT) Received: from ?192.168.2.110? ( [222.131.141.164]) by mx.google.com with ESMTPS id u12sm10785306tia.5.2008.08.25.00.38.00 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 25 Aug 2008 00:38:01 -0700 (PDT) Message-ID: <48B25F15.4050703@gmail.com> Date: Mon, 25 Aug 2008 15:28:21 +0800 From: Freeman Fang User-Agent: Thunderbird 1.5.0.2 (X11/20060524) MIME-Version: 1.0 To: dev@cxf.apache.org Subject: can we use asyn way for jms transport Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, Currently we are using sync way for jms transport which means the thread get blocked until response messsage is coming or the client side timeout, see the handleResponse() method of JMSConduit? Is it possible that we use non-block way for JMSConduit, something like implement JMS MessageListener API? Or any special reason we need this sync invocation for JMS conduit? Thanks Freeman