Jon Tirsen said in his weblog that he had seen an interesting project called Picocontainer and was immediately engaged. What is the appeal of this micro-container, which calls itself "IoC (inversion of Control) Type 3"?
Picocontainer/nanocontainer I ' ve recently joined two new projects:
http://www.picocontainer.org
http://www.nanocontainer.org
The founders of the project are Paul (Altrmi, Enterprise Object Broker) and Aslak (XDoclet, Middlegen). Actually they pair-programmed most of it at Paul "s place and a lot of beer is involved. The end result:a neat, simplistic and wonderfully tdded piece of work. Joe (Sitemesh, Qdox), my unit-testing guru, are also in on it.
It ' s basically an inversion-of-control-container/framework/micro-kernel. Pico would be the simplistic micro-kernel and Nano'll be a bunch of containers serving different purposes (most built on Top of Pico).
I ' m not a ioc-expert by any means, and, the, I didn ' t know much about it before chatting with Paul and Aslak. The cool (and quite controversial) thing was that Pico (at least by default) implements style 3 IoC which means Constructo RS are used to define dependencies. smart!
I'll implement some nanning support in Nano so, aspects can define on services and the dependencies would r Esolve them properly, the aspects'll also is able to aspectify the components transparently. The details are far from finalized, just a bunch of semi-digested ideas. I ' ll give you a couple of use-cases though. An aspect implementing transparent persistence with Prevayler could retrieve it "s prevayler-instance just by declaring it In its constructor:
public class Prevayleraspect {public Prevayleras