Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 70875 invoked from network); 10 Oct 2006 22:55:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Oct 2006 22:55:17 -0000 Received: (qmail 19789 invoked by uid 500); 10 Oct 2006 22:55:13 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 19740 invoked by uid 500); 10 Oct 2006 22:55:13 -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: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 19729 invoked by uid 99); 10 Oct 2006 22:55:13 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Oct 2006 15:55:13 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [209.68.5.15] (HELO relay01.pair.com) (209.68.5.15) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 10 Oct 2006 15:55:13 -0700 Received: (qmail 39789 invoked from network); 10 Oct 2006 22:54:50 -0000 Received: from unknown (HELO ?127.0.0.1?) (unknown) by unknown with SMTP; 10 Oct 2006 22:54:50 -0000 X-pair-Authenticated: 66.194.95.2 Message-ID: <452C2494.6030607@opensource.lk> Date: Tue, 10 Oct 2006 17:54:12 -0500 From: Deepal Jayasinghe User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "axis-dev@ws.apache.org" , "axis-user@ws.apache.org" Subject: [Axis2] Summery of todays Hackathon X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi All; Few note from todays Hackathon we had at ApacheCon US. We are having very ugly name called finalizeInvoke() in service client with restriction, so we (Glen and I agreed) to remove that method and move the code into cleanup (well I am doing the changes in current codebase). Why do we need operation client ?........ As Dennis suggested , having annon name as public static seems not that good , so we need to remove them I mean we need to make the private. Rather than giving two client API to client cant we have one API , we can have all the methods in serviceClient then no one need to know about the operationClient (service client will use that internally ). So our proposal is to add few more methods into ServiceCleint; public MessageContext sendReceive(MessageContext req){} public void sendReceiveNonBlocking(MessageContext req){} public fireAndForget(MessageContext req){} public sendRobust(MessageContext req){} if we introduce these methods into ServiceClient then we do not too much worry about how to create operationClient etc... I am +1 on adding these four methods in to serviceClient. ======= How do we reflect service group concept in to client , and manage session using that. Well I do understand if we use Axis2 client <-> Axis2 service this will work , but what if we use .Net client <-> Axis2 Service. Is there any kind of specification sending session related data in SOAP message ? , if there is such a thing then we need to use them. Thanks Deepal --------------------------------------------------------------------- To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-dev-help@ws.apache.org