axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Afkham Azeez (JIRA)" <>
Subject [jira] Assigned: (AXIS2-3699) Termination of the soapsession
Date Thu, 06 Jan 2011 15:22:48 GMT


Afkham Azeez reassigned AXIS2-3699:

    Assignee: Afkham Azeez

> Termination of the soapsession
> ------------------------------
>                 Key: AXIS2-3699
>                 URL:
>             Project: Axis2
>          Issue Type: New Feature
>    Affects Versions: 1.3
>            Reporter: Matthias Gaiser
>            Assignee: Afkham Azeez
> I want to do some tidying up at the termination of the soapsession. The session is terminated
when the timeout, specified in axis2.xml, is reached.
> It would be of great help if you could have something like a SessionLifeCycle interface.
It may contain two methods init() and destroy() which are called whenever the session is started
or terminated.
> Like the ServiceLifeCycle, the implementing class of the SessionLifeCycle could be specified
via the services.xml, where you also have to declare that the service uses the soapsession
> To clarify my request:
> In a servicegroup with a single service I could do all the session specific initialization/termination
in the init()/destroy() method of the Service implementation class. But when there are multiple
services in a ServiceGroup, there is no way to init or destroy session-related resources used
by the whole serviceGroup.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message