axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Klaus Thiele <...@pi-ag.com>
Subject AW: AW: AW: AW: AW: Deploying the client
Date Tue, 17 Dec 2002 09:02:24 GMT
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 Sebastian.Beyer@wettschereck-partner.de:
> 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:kth@pi-ag.com

 "There's got to be more to life than compile-and-go."


Mime
View raw message