Proposal: PicoBuilder interface

Once in a while with Pico, my hands cramp up writing the compositions. pico.registerComponentImplementation() just starts getting long after the 20th or 30th time

I like the Groovy Builder syntax for its brevity and wanted to see something similar available for Pico in pure Java code.

So today I created a basic interface that while not quite as flexible as Pico's core API, it is really darn convenient. It simply sits aside PicoContainer, no changes in the core API necessary.

Example Usage (More in javadocs in patch)

 
MutablePicoContainer pico = new DefaultPicoBuilder()
        .component(ArrayList.class)
        .instance("This is a test")
        .component(ServiceOneInterface.class, ServiceOne.class)
        .component(ServiceTwo.class, ServiceTwo.class, new Parameter[] {....})
        .build();

assertEquals("This is a test", pico.getComponentInstance(String.class);

The real limitation with this method is that it doesn't return the component adapter, so you can't find tune the component adapters during the build. (I basically mirrored the MutablePico API otherwise). But since build() doesn't call any lifecycles, you can have:

MutablePicoContainer pico = new DefaultPicoBuilder().instance("test").build();
ComponentAdapter ca = pico.getComponentAdapter(String.class)

Again, my goal was to save typing, but I believe this could get very handy.

What do you guys think?

-Mike (R)