On Wednesday 23 October 2002 22:06, Alan Moore wrote: > FYI: > > If your service is marked for session scope, you don't need to > store your data in the session itself. You can store it in your > service class as a member variable. This reduces your dependency > on accessing the Session object via an Axis-specific api (e.g. > getCurrentContext()) > > Since your service object instance is reused on a per-session > basis when your service method is called for a given session > client, the data member state is still valid.
Of course, if you want your session to be persistent, you should not do this AFAIK. Best approach then is changing the value in the Session object whenever it changes, but reading it from a member variable. -- Matthias Brunner <[EMAIL PROTECTED]> PGP FP 7862 32B3 3B75 292A F76F 5042 8587 21AB 5B89 D501 Check out http://blumenstrasse.vol.at/~mb/gpgkey.asc
