Hi Klaus, ahhh thats your problem. In the documentation they say, that you have to enable session on both sides. client AND server for getting the session working. So, if you dont set Maintainsession to true, your session does not work and you get a new Session-ID for each request. Did understand you now? I'm not sure, why it is like this, but I think the client does not send the Session-ID automatically to the server, so you have to activate it.
Greetings from Hamburg -----Ursprüngliche Nachricht----- Von: Klaus Thiele [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 17. Dezember 2002 10:02 An: [EMAIL PROTECTED] Betreff: AW: AW: AW: AW: AW: Deploying the client Hi, yes, but with scope as "session" i get _also_ a new session object each time i request a method if i don't set maintainsession to true at client-code - thats why i'm irritated. (with scope as "application" it works as expectet _without_ do anything at client-side - same object for each request from each client) klaus Am Dienstag, 17. Dezember 2002 09:52 schrieb [EMAIL PROTECTED]: > Hi Klaus, > > the difference is simply the lifecycle of your objects. If you define > the scope as "request" you get a new session-Object each time you > request a method from your webservice. When defining the scope as > "session" you have the same objects for several requests for this > session and when defining the scope as "application" you have the same > objects for every request, independent from the session. -- Klaus Thiele - Personal & Informatik AG mailto:[EMAIL PROTECTED] "There's got to be more to life than compile-and-go."
