axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rajith Attapattu <rajit...@gmail.com>
Subject Re: [Axis2] Transport independent Session Mgt [Proposal]
Date Sat, 21 Jan 2006 01:10:09 GMT
On 1/20/06, Sanjiva Weerawarana <sanjiva@opensource.lk> wrote:
>
> On Fri, 2006-01-20 at 11:03 -0500, Rajith Attapattu wrote:
>
>
> > Well, For Axis2 vs Axis2 scenario this is true.  However I feel that
> > we should be thinking of non-Axis2 clients as well in which case they
> > "have" to know the specifc id to be sent in the SOAP header.
> >
> > This is exactly my concern as well. How are we going to handle this
> > scenario.
>
> No no this is incorrect. Reference parameters such as the service group
> ID are totally opaque to the client side. *Any* client which supports
> WS-Addressing will do the right thing.
>
> Sanjiva, you just solved the biggest concern I had about impacting
> existing client code and being interoperable !!


   So if a service is deployed in SOAP session scope we do that with the
understanding that any client that uses this service supports WS-Addressing.

  If above assumption is wrong,  How about the client that don' support
WS-Addressing ?? is this scenario something to be concerned or not??

  Rajith

Mime
View raw message