[picocontainer-dev] Lifecycle usage question


CachingBehavior, when start(PicoContainer) is called, hands off thru  
a series of delegations to AbstractInjector to actually call start 
(Object) on the LifecycleStrategy

This seems odd.  CachingBehavior (during instantiation) has a handle  
on the same LifecycleStrategy so could easily do it there.  Meaning  
the Injectors (all subclasses of AbstractInjector) could lose their  
Lifecycle logic - it seems unassociated there.

I could refactor to that, but then lifecycle will only work with  
Caching or Pooling behavior.

So the question - does anyone have any use for Lifecycle on  
components that are not cached/pooled ?

- Paul