[wsas-java-dev] WSAS Session Management

[saminda abeyruwan]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hi all,

Before WSAS 1.1, all the administration services were under a single
Administration service group. Thus, an instance of an admin service
group id (Service group context Id) were used to manage session. Thus,
we use private header <axis2:serviceGroupId/> in addressing to mange it.

With the current refactoring, most of the admin services have been
removed from WSAS and has been established as a separate WSO2 Common
projects. Ex: JavaClient generation service; Tracer Admin service etc.
Thus, there will be multiple service groups for admin purposes; and we
could not use a single service group context Id to manage sessions.

Thus I would see following options;

1. Since these are common services (service groups); lets treat them as
regular services ; and when AJAX admin calls for these services  lets
not send the service group context Id. This will be a minor modification
in the Javascripts.

2. Treat them as admin services (service groups) and try another session
management other that "soapsession" management. In this case we could
use transport session management with Cookies. This has to be
implemented with WSAS listeners.

Please be kind enough to express your thoughts on this.

Thank you

Saminda
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFrbFeYmklbLuW6wYRAhfPAJ9l5XcS91Y77ia2mV3zghVEYSIkeACfaYA4
OMcPROrV3EoZCqMykSMg8Ao=
=n3h+
-----END PGP SIGNATURE-----