-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
Hi Ted;

what do u mean by that does not work ? , I recently changed scope
handling , and I hope that should work.

and that work as follows ,
  1. If you deploy a service under the scope "request" , then there
wont be any sessions management even if you send the service group ID
back (we mange session using ServiceGroup ID)
  2. If you deploy a service in the transport session scope , then the
there will be session management using transport cookies and there
will be only one instance of service impl class for that transport
session.
 3. If you deploy a service in scope of SOAP session then you can
manage session using ServiceGroupID , but that session will be removed
from the system if you did not touch the session for about 30s. (there
will be only one instance of the service impl for that session)
4. If you deploy service in application scope then one can manage a
session using servicegroupID throughout the life time of the
system.(there will be only one instance of the service impl for that
session)

and can you pls clarify what do you mean by it does not work , so that
I can fix that

[EMAIL PROTECTED] wrote:

>Hello,
>
>trying to deploy some services under the use of the
>attribute scope="application" at the <service>-tag in
>services.xml, I noticed that this setting of the scope
>doesn't work in Axis2 0.94. The only correct working
>scope is the scope="transport". Are there any knows
>bugs? I thought that this application scope setting
>worked well, using release 0.93...
>
>Thanks Ted
>
>
>
>
>
>
>___________________________________________________________
>Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
>
>

- --
Thanks,
Deepal
................................................................
~Future is Open~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
 
iD8DBQFD6Z/ajOGcXNDx0CARAnxlAJ9QWwpSlj7guWeZnwvpCrCjulPJDQCfTC6c
T47YjD9rTeMWqwUQrT/IhG8=
=XjMa
-----END PGP SIGNATURE-----


Reply via email to