Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 31724 invoked from network); 23 Mar 2005 11:08:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 23 Mar 2005 11:08:22 -0000 Received: (qmail 65304 invoked by uid 500); 23 Mar 2005 11:08:19 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 65252 invoked by uid 500); 23 Mar 2005 11:08:18 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 65236 invoked by uid 99); 23 Mar 2005 11:08:18 -0000 X-ASF-Spam-Status: No, hits=0.4 required=10.0 tests=DNS_FROM_RFC_ABUSE,RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of jayachandra@gmail.com designates 64.233.184.196 as permitted sender) Received: from wproxy.gmail.com (HELO wproxy.gmail.com) (64.233.184.196) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 23 Mar 2005 03:08:17 -0800 Received: by wproxy.gmail.com with SMTP id 68so161266wri for ; Wed, 23 Mar 2005 03:08:15 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=QhH69/Uw3tLJLSKa4SRBWFHWDs+JXu9ZUxnM/Wn3MQnkLstUNzpX6qDqXIvsWNfzsOpkhc6d2C7RK/TWjU9fHvz/ulAEdV5psB1CUYOiYT/+qXCykNacHnZXZjCgiGQgiBIT/ypaTQDb2FcFUjecbDwa0Py1ECpqszvBecEUYrg= Received: by 10.54.96.7 with SMTP id t7mr189051wrb; Wed, 23 Mar 2005 03:08:15 -0800 (PST) Received: by 10.54.68.13 with HTTP; Wed, 23 Mar 2005 03:08:15 -0800 (PST) Message-ID: <57023d1305032303086c3da7a3@mail.gmail.com> Date: Wed, 23 Mar 2005 16:38:15 +0530 From: jayachandra Reply-To: jayachandra To: axis-dev@ws.apache.org Subject: [Axis2] Fwd: Doubts regarding client side DD and test case for HTTPTransportSender. In-Reply-To: <57023d13050323024477491e3e@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <57023d13050323024477491e3e@mail.gmail.com> X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Extremely sorry guys! Resending with proper subject line ---------- Forwarded message ---------- From: jayachandra Date: Wed, 23 Mar 2005 16:14:00 +0530 Subject: Doubts regarding client side DD and test case for HTTPTransportSender. To: axis-dev@ws.apache.org With the idea of each transport being a new module, the way any TransportSender handler gets picked up got totally changed. Everything seems to be through DD. On the client side how should the deployment info be mentioned to use a specific transport handler for communication, is it through some client.xml present in the classpath. Can someone point to some example/resource relevant to this. I've with me a CommonsHTTPTransportSender file written to fit into the Axis2 codebase. It will provide synchronous invocation functionality. And I want to provide a test case to prove that it's working. Are there any test cases written to test the functionality of HTTPTransportSender (synchronous invocation only) currently, I'll go in those lines. JC -- -- Jaya