Groovy Builder for Nano does not propate parent container types or component adapters.

Using the Groovy Builder, it appears currently impossible to implicitly propagate parent container types and adapterfactories to children containers. The following test case will fail. (NOTE: The test case depends on the BasePicoVisitor enhancement submitted in PICO-235, but it is easy enough to backport)

public void testChildContainerHasParentAdapter() {
Reader script = new StringReader("" +
"builder = new org.nanocontainer.script.groovy.NanoContainerBuilder()\n"
+ "pico = builder.container(parent) { \n"
+ " container()

{\n" + " component(ArrayList)" + " }

\n"
+ "}"
);

//Build the parent
ObjectReference parent = new SimpleReference();
parent.set(new DefaultPicoContainer(new BeanPropertyComponentAdapterFactory(new DefaultComponentAdapterFactory())));

//Build target
ScriptedContainerBuilder builder = new GroovyContainerBuilder(script, Thread.currentThread().getContextClassLoader());
builder.buildContainer(new SimpleReference(),parent,null, true);

//Collect a list of all containers.
final List allContainers = new ArrayList();
PicoVisitor testingVisitor = new BasePicoVisitor() {
public void visitContainer(PicoContainer pico)

{ super.visitContainer(pico); //Calls checkTraversal for us. allContainers.add(pico); }

};
testingVisitor.traverse((PicoContainer)parent.get());

//Verify that default component adapter factory gets propagated
//down the hierarchy much in the way that pico.makeChildContainer() works.
for (Iterator i = allContainers.iterator(); i.hasNext()

{ PicoContainer oneContainer = (PicoContainer)i.next(); assertNotNull(oneContainer.getComponentAdapterOfType(BeanPropertyComponentAdapterFactory.class)); }

}