(B
(BThanks Barry,
(B
(BThis was the kind of "statefulness" and "persistence" that I am
(Binterested in (though I was also interested to hear what was said re
(BSOAP and sessions by Anne et al., as this was another question I had).
(B
(BCan you tell me, why does the client need to set "maintain sessions" to
(BTRUE (Axis) (or use the cookie container in .NET). I would have thought
(Bthat for the example (bank account) that you and I describe,
(Bpreservation of state would be an entirely server-side consideration,
(Bwith no client-side requirements other than a valid SOAP invocation?
(B
(BRegards
(B
(BDavid
(B
(B
(B
(BBarry Levinson wrote:
(B
(B>Maybe I'm missing something, but it seems this is really a simple
(B>question with a simple answer.
(B>
(B>Here's the original question :
(B>
(B>For example, can I create a "bank account" web service, which supports
(B>deposit(), withdrawl() and getBalance() operations, and have that web
(B>service preserve the current account balance between separate
(B>invocations?
(B>
(B>The answer is yes.
(B>
(B>You can use axis to do this by simply setting session scope in your
(B>deploy.wsdd.
(B>
(B>Session scope means that class instances are persistant. If you simply
(B>have a private "int ballance" member (*not* static) of you bankAccount
(B>class, it will retain its value across multiple calls. The client needs
(B>to "cooperate" by passing some session info, this is done simply by
(B>adding a cookie container (.net client) or setting maintain session to
(B>true (axis client).
(B>
(B>--Barry
(B>
(B>Anne Thomas Manes wrote:
(B>
(B>
(B>
(B>
(B>
(B>
