How to do Stateful SOAP servers?

[Bryan Field-Elliot]

Hi,

Being somewhat new to SOAP (and having pored over several books/resources), I'm finding a lack of explanation out there on how to do "Stateful" SOAP servers (in the same way that it's trivial to do Stateful JSP's/Servlets).

I've seen mention in the Axis docs of having your SOAP server implementations being mapped to Application vs. Session vs. Request scopes.. Is that the key functionality I'm looking for?

Basicly I want to provide a SOAP API with methods like:

logon()
putItem()
getItem()
removeItem()

And I want for the SOAP client to be required to call logon() before calling any other method on my server... Any deviation throwing a "fault" or something.

Help would be appreciated!

Thanks,
Bryan