[picocontainer-dev] Dan North - Reviewing the language of the new PicoBuilder
Paul Hammant <[email protected]>
| Newsgroups | gmane.comp.java.picocontainer.devel |
|---|---|
| Message-ID | <[email protected]> |
Dan North (main author of 'Rico' the first Ruby IoC container) and
'resting' committer to Pico is going to take a look at the language
of PicoBuilder.
Why? He's the JBehave fellow, black-belt NLP expert and lover of
good naming (my weakpoint).
For Dan -
PicoBuilder is a way of making a PicoContainer instance for
subsequent adding of components to.
We used to have half a dozen extended PicoContainer implementations
that offered alternate designs to DefaultPicoContainer. Namely
ImplementationHidingPicoContainer, HotSwappablePicoContainer,
CachingPicoContainer (etc). In then end they were just convenience
classes that chose their internal composition. For example,
CachingPicoContainer was just a wrapper to DefaultPicoContainer with
CachingComponentAdapterFactory as the frontmost CAF in the chain of
CAFs. new PicoBuilder().withCaching().build() is the builder-esque
alternative to new DefaultPicoContainer(new CachingBehaviorFactory()).
Note also that ComponentAdapterFactory is now either BehaviorFactory
or InjectionFactory (making some derivative of AbstractBehavior or
AbstractInjector respectively).
- Paul
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email