Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
Received-SPF: pass (asf.osuosl.org: domain of davanum@gmail.com designates
 66.249.82.225 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=PihjEh/CIrl7wTaMk6lDYWuWorSIN4NnYSZRL9miFLn5KSMwmoOiqrzOnrdqAAMonUvkFbYs6pVXMkTaJOqwkYalzMyL/c1QiHdIab4YaFQCqxDqBNRLZZFcrm2+hJ7gGdkNQrv7+qB6QKgxeodZpQgYE6l6ofJQYPB00N1wR1I=
Message-ID: <19e0530f0610101602m3067e6c3v155068f39466080d@mail.gmail.com>
Date: Tue, 10 Oct 2006 19:02:24 -0400
From: "Davanum Srinivas" <davanum@gmail.com>
Reply-To: dims@apache.org
To: axis-dev@ws.apache.org
Subject: Re: [Axis2] Summery of todays Hackathon
Cc: "axis-user@ws.apache.org" <axis-user@ws.apache.org>
In-Reply-To: <452C2494.6030607@opensource.lk>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <452C2494.6030607@opensource.lk>

Deepal,

Please create JIRA issue(s) and let's work on them.

thanks,
dims

On 10/10/06, Deepal Jayasinghe <deepal@opensource.lk> wrote:
> 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
>
>


-- 
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org