Whatever the name is, I would say this is something that would polish off the life cycle methods support. I'll raise an issue in Jira and have a peek to see what the changes required would be.
On a different note, I was wondering what everyones thought would be on adding an 'before', 'after' and a 'name' attribute to the EagerLoad contribution point (similar to the interceptor contribution)? It would be great to be able to control te order of initialization and this adds a familiar way of doing so. Cheers, Johan James Carman wrote: > I probably would have used a method name like dispose() or shutdown() or > destroy() rather than registryDidShutdown() if you want to stress the > importance of removing a dependency (the "registry" part screams HiveMind). > But, your concern is a valid one. We have support for init methods, but not > destroy/shutdown methods. > > -----Original Message----- > From: Johan Lindquist [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 05, 2006 12:09 PM > To: hivemind-dev@jakarta.apache.org > Subject: Registry shutdown > > Hi all, > > Is there a particular reason for the RegistryShutdownListener interface? > Could this not be implemented just as the automagic initialization call > of the service? If a method on the implementation is named > 'registryDidShutdown', add it automatically to the list of shutdown > listeners? Would nicely remove another compile time dependancy. > > Cheers, > > Johan > > -- > you too? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- you too? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
