Mailing-List: contact commits-help@tapestry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tapestry.apache.org
Message-ID: <11191807.10481291065731253.JavaMail.jira@thor>
Date: Mon, 29 Nov 2010 16:22:11 -0500 (EST)
From: "Paul Stanton (JIRA)" <jira@apache.org>
To: commits@tapestry.apache.org
Subject: [jira] Updated: (TAP5-1359) add 'registryAboutToShutdown' handler
In-Reply-To: <7465793.10441291065612927.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/TAP5-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Stanton updated TAP5-1359:
-------------------------------

    Description: 
It is impossible to inject a service into a handler of 'RegistryShutdownListener .registryDidShutdown' since the registry is already shutdown at this point. this makes it difficult to perform some more intricate termination logic when multiple services need to collude.

I propose the inclusion of a new interface 'RegistryAboutToShutdownListener' with the method 'registryAboutToShutDown'.

In the case of a tapestry application, it would need to be called after Http requests have been disallowed, but before the registry becomes unusable.

There may need to be some ordered configuration to control service dependencies as they shut down, and I expect some other considerations I haven't thought of....

  was:
It is impossible to inject a service into a handler of 'RegistryShutdownListener .registryDidShutdown' since the registry is already shutdown at this point. this makes it difficult to perform some more intricate termination logic when multiple services need to collude.

I propose the inclusion of a new interface 'RegistryAboutToShutdownListener' with the method 'registryAboutToShutDown'.

In the case of a tapestry application, it would need to be called after Http requests have been disallowed, but before the registry because unusable.

There may need to be some ordered configuration to control service dependencies as they shut down, and I expect some other considerations I haven't thought of....


for an example of when it would be useful see
http://www.mail-archive.com/users@tapestry.apache.org/msg48540.html

> add 'registryAboutToShutdown' handler
> -------------------------------------
>
>                 Key: TAP5-1359
>                 URL: https://issues.apache.org/jira/browse/TAP5-1359
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-ioc
>    Affects Versions: 5.2.4
>            Reporter: Paul Stanton
>
> It is impossible to inject a service into a handler of 'RegistryShutdownListener .registryDidShutdown' since the registry is already shutdown at this point. this makes it difficult to perform some more intricate termination logic when multiple services need to collude.
> I propose the inclusion of a new interface 'RegistryAboutToShutdownListener' with the method 'registryAboutToShutDown'.
> In the case of a tapestry application, it would need to be called after Http requests have been disallowed, but before the registry becomes unusable.
> There may need to be some ordered configuration to control service dependencies as they shut down, and I expect some other considerations I haven't thought of....

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