[picocontainer-dev] Latest Pico Commit.... changed behavior on AbstractContainerBuilder

Hi guys,

Pico 2 behavior:  AbstractContainerBuilder would automatically start all
containers that it created.
New Pico 3 behavior I just checked in:  Starting behavior has been
refactored out into a decorating AutoStartingContainerBuilder.  So you get
Pico 2 behavior with:  
ContainerBuilder builder = new AutoStartingContainerBuilder(new
GroovyContainer(.....));

I needed it for me because I kept running into situations where
parent.makeChildContainer() would cause all sorts of conniptions when both
the parent and child were deployed through the container builders; and my
"don't change any behavior" fix through the constructor args was __U G L
Y__.  

Let me know if there are better options that you can see.

	
-Mike


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

    http://xircles.codehaus.org/manage_email