Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <02a801c4ff1e$4d575f90$8dc35f3d@laptop>
From: "Shantha Kumar" <shanthakumar@mentor-labs.com>
To: <axis-user@ws.apache.org>
References: <ED9D00474EBF2C439E4A430BA2BE3B8B061CA6C3@artemis.argon.local>
 <018d01c4ff16$f2910450$8dc35f3d@laptop> <41EFF620.3090400@ugcs.net>
Subject: Re: Question about session scope
Date: Fri, 21 Jan 2005 00:01:46 +0530
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

thanks Tim.

I was of the opinion that the implementation was done for statelessness.

thanks for the eye-opener.

SK
----- Original Message -----
From: "Tim K. (Gmane)" <tkgmane+at@ugcs.net>
To: <axis-user@ws.apache.org>
Sent: Thursday, January 20, 2005 11:49 PM
Subject: Re: Question about session scope


> The scope (session, application, request) on the server side tells Axis
> how many instance of the server implementation classes to create, it
> doesn't have much to do with the session on the client side. The client
> is not aware of the session scope on the server side. So you can for
> example use sessions on the client even if the scope on the server is
> application (or request).
>
> Now, session tracking on the client side via HTTP cookies has a few
> issues. You may want to look at these bugs (some may or may not apply to
> your usage case but it's good to be aware of them):
>
> http://issues.apache.org/jira/browse/AXIS-1080
>
> http://issues.apache.org/jira/browse/AXIS-986
>
> http://issues.apache.org/jira/browse/AXIS-1754
>
> Tim
>
> Shantha Kumar wrote:
> > Hi,
> >
> > if the client doesn't call setMaintainSession(true) the JSessionID
cookie
> > doesn't get transported to the server. The server keeps creating a new
> > session and also a new bean.
> >
> > thanks,
> > sk
> > ----- Original Message -----
> > From: "Wiener, Zach" <Zach.Wiener@argonst.com>
> > To: <axis-user@ws.apache.org>
> > Sent: Thursday, January 20, 2005 8:26 PM
> > Subject: Question about session scope
> >
> >
> > Hello.  If I deploy a service with session scope, then why must the
> > client call setMaintainSession(true)?  It seems that the service, or
> > Axis, should be responsible for maintaining the scope of the service as
> > session.  How is the scope of a service published to clients?  What
> > happens if a service is deployed as session scope, but the client
> > doesn't call setMaintainSession(true)?
> >
> > Thanks.
> >
> >
> >
> >
>
>