hivemind-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Carman" <ja...@carmanconsulting.com>
Subject RE: [jira] Commented: (HIVEMIND-103) Core service implementations which implement RegistryShutdownListener are not notified for primitive, singleton, and pooled service models
Date Mon, 28 Mar 2005 23:13:51 GMT
So, are we okay with leaving these changes in and allowing service
implementations to automatically receive registry shutdown events, if they
implement RegistryShutdownListener?

-----Original Message-----
From: Howard Lewis Ship [mailto:hlship@gmail.com] 
Sent: Monday, March 28, 2005 5:47 PM
To: hivemind-dev@jakarta.apache.org
Subject: Re: [jira] Commented: (HIVEMIND-103) Core service implementations
which implement RegistryShutdownListener are not notified for primitive,
singleton, and pooled service models


I've been thinking of adding one or two "special cases" to HiveMind for
things like the ShutdownCoordinator; basically, a way to programatically
provide an instance as the core service implementation of a well known
service (such as hivemind.ShutdownCoordinator).


On Tue, 29 Mar 2005 00:42:17 +0200 (CEST), James Carman (JIRA)
<hivemind-dev@jakarta.apache.org> wrote:
>      [ 
> http://issues.apache.org/jira/browse/HIVEMIND-103?page=comments#action
> _61681 ]
> 
> James Carman commented on HIVEMIND-103:
> ---------------------------------------
> 
> I added a test case which showed exactly what you said.  You were 
> correct.  It was calling registryDidShutdown() twice in all cases.  I 
> added code to the ShutdownCoordinatorImpl to verify that it's not 
> calling registryDidShutdown() on the same exact instance more than 
> once (it uses the identity hashcode so that objects which aren't 
> playing nice can't mess things up).  Also, I found out there there are 
> actually TWO ShutdownCoordinatorImpl objects created at runtime.  One 
> which is exposed as a service and one that's used internally by the 
> infrastructure.  I changed my code to make sure I was adding the 
> implementation objects to the service version rather than the 
> infrastructure version, as this is most likely where service 
> implementations will add themselves if they do so.
> 
> > Core service implementations which implement 
> > RegistryShutdownListener are not notified for primitive, singleton, and
pooled service models
> >
----------------------------------------------------------------------------
--------------------------------------------------------------
> >
> >          Key: HIVEMIND-103
> >          URL: http://issues.apache.org/jira/browse/HIVEMIND-103
> >      Project: HiveMind
> >         Type: Bug
> >   Components: framework
> >     Versions: 1.1
> >     Reporter: James Carman
> >     Assignee: James Carman
> >      Fix For: 1.1
> 
> >
> > Per the documentation, if a core service implementation object 
> > implements RegistryShutdownListener, it is supposed to automatically 
> > be added as a listener to the ShutdownCoordinator.  This is only 
> > supposed to be true for the primitive, singleton, and pooled service 
> > models, but it's not happening.
> 
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
>    http://issues.apache.org/jira/secure/Administrators.jspa
> -
> If you want more information on JIRA, or have a bug to report see:
>    http://www.atlassian.com/software/jira
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hivemind-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: hivemind-dev-help@jakarta.apache.org
> 
> 


-- 
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind

Professional Tapestry training, mentoring, support
and project work.  http://howardlewisship.com

---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-dev-help@jakarta.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-dev-help@jakarta.apache.org


Mime
View raw message