Hi All,
I'm a bit concerned about this issue as well. I mean the addressing
reference property will keep the SOAP session over different operations of
the same service but if you are to keep the session across *services* then
the client must know this special ID! Am I mistaken here or what ?
On 1/21/06, Srinath Perera <hemapani@gmail.com> wrote:
>
> Sorry for interrupting, Let me ask a Q
>
> Let me take the inout MEP
> When a server reply to a request reference property approach works!
> because server uses reply to EPR. How can we make it work with the
> request.
>
> How the client know the To EPR, is there any association to WSDL. How
> first message on a interaction get a To EPR? Can you explain how in a
> In-Out MEP, Service Provider (Server) keep a session across number of
> In-Out Invocations?
>
> Thanks
> Srinath
>
> On 1/20/06, Sanjiva Weerawarana <sanjiva@opensource.lk> wrote:
> > On Fri, 2006-01-20 at 20:10 -0500, Rajith Attapattu wrote:
> > >
> > >
> > > 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??
> >
> > No- WS-Addressing is a core part of the foundation of Web services. If
> > the client doesn't support WS-Addressing then its life is very boring
> > because it can't participate in pretty much anything except message
> > exchanges over a bi-directional protocol such as HTTP.
> >
> > Sanjiva.
> >
> >
> >
> >
>
>
> --
> ============================
> Srinath Perera:
> http://www.cs.indiana.edu/~hperera/
> http://www.bloglines.com/blog/hemapani
>
--
Ajith Ranabahu
|