[picocontainer-dev] Builder confusion and cycles in annotation

2 points:

- The builder and default container are confusing: if you use the
builder, you get the caching by default even when you don't say
withCaching() because most contructors of picocontainer create the
caching adapter. Also having a NOCACHE characteristic + settings in the
builder is somehow redundant. I find the componentcharacteristic system
not elegant at all.

- The current strategy of dealing with cycles is to throw an exception
when a cycle is found. However many cycles can be solved when using only
method and field injection. What I suggest (and have done) is to track
all the instances being injected and keep going recursively until they
are all done even when there are cycles. A current limitation is that
all relies on getComponent, so I'm not sure there is a way to flush a
cache in a CA after the root getComponent is processed.

 

Erik.