RE: [picocontainer-dev] ComponentMonitor becomes Monitor

> For some context.. I was complaining about a situation where:
> 
> * Create container A, and start it
> * Make a child container B from A
> * <app runs>
> * Stop container A
> * Stopping everything fails because B can't be stopped because it was
> never started.
> 
> So my suggestion was that we could not throw an exception on stop(),
> but since we don't want to eat it, it could be sent to the
> ComponentMonitor. Now since this is for the container and not
> components, renaming to just Monitor seemed reasonable.

Not only do I agree, but the other condition where a monitor trigger was
created is when someone calls getComponent() and the requested key doesn't
exist.  

Currently ComponentMonitor doesn't work for that situation either.

A definite 'aye' :)

							-Mike



---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email