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)" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 20, 2005 11:49 PM
Subject: Re: Questi
keeps creating a new
session and also a new bean.
thanks,
sk
- Original Message -
From: "Wiener, Zach" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 20, 2005 8:26 PM
Subject: Question about session scope
Hello. If I deploy a service with se
: <[EMAIL PROTECTED]>
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
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 i
