RE: [picocontainer-dev] Lifecycle usage question
Jörg Schaible <[email protected]>
| Newsgroups | gmane.comp.java.picocontainer.devel |
|---|---|
| Message-ID | <[email protected]> |
JMX componnets. Register at start, deregister at end. It depednds on the nature of the component whether is some kind of singleton (cached) or not. ________________________________ From: Paul Hammant [mailto:[email protected]] Sent: Sunday, July 01, 2007 6:35 PM To: dev-qxt/[email protected] Subject: [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 --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email