On 20 Mar 2002 07:06:30 -0700, Bryan Field-Elliot <[EMAIL PROTECTED]> wrote:
||| 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). ||| ||| 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. I'm facing the same problem right now with a client. What we are planning on doing is to pass to the client code a "transaction token" that we create in the login process. The client code will then pass this token as the first argument of each successive service invocation. We didn't see any other way to do it. I think the SOAP that comes with WLS6.1 has some statefull qualities, but it doesn't work with all client implementations. (I could be wrong about that; we've been doing rapid research on this and this is what we found...) Does anyone have a better way to do it? Joey -- Blue canary in the outlet by the lightswitch, -- who watches over you...
