On Wed, 2003-06-04 at 22:10, Scott Nichol wrote: > In Apache SOAP, the a SOAPHTTPConnection instance saves the cookies > it receives from a response and sends them back in subsequent > requests. Therefore, if you re-use a SOAPHTTPConnection instance > across multiple calls, those calls will be part of the same session, > assuming, of course, that session support is activated on the server > and uses cookies. > > On the server, you can handle sessions completely transparently by > giving services a scope of session. That means an instance of the > service is created for each session, which means any state maintained > by an instance will be the state for a single session. > Alternatively, you can access servlet sessions from your service and > store data in those, so that you can give your service a different > scope, such as application scope in which a single instance will > service all requests. > Ahm, and how to re-use SOAPHTTPConnection? And how to extract session ID? In servlets it is so fairly easy :) but I am a bit new in this :)
-- Bratislav Ljubisic A: Bul.Arsenija Carnojevica 171/26 11000 Beograd Srbija, Yugoslavia P: +381 11 123 375 M: +381 63 8 505 594 F: Stichting Kunst en Industrie E: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] W: www.fmmedia.co.yu www.kunstenindustrie.com I: 11412608 ---------------- WinNT error 003: FPU error - enter any 11 digit prime number to continue.
