PicoContainer is a "micro-kernel" container. It uses Inversion Of Control Mode and Template Method mode to provide components-oriented development, running environments. As can be seen from the name, PicoContainer is "extremely" container that only provides the most basic feature. Other containers can add more features on it based. Because of its small, PicoContainer is also an analysis of the best objects.
----------------
The PicoContainer Team IS PROUD TO Announce The Release of The First Beta of PicoContainer 1.0.
PicoContainer is an embeddable container for type-3 Inversion of Control (IoC) components. It is delivered as a set of abstractions, a couple of instantiable containers, a few adaptors for hierarchies and (optional) lifecycle management as well as support classes. We Genuinely Believe this To Be The Logical Conclusion of the IOC Component Model.
Components:
The component model (igoring our lifecycle support) is unencumbered by obligations of API. There is nothing to extend, nothing to implement and nothing to throw. The component model forces no obligations for XML meta-data on the developer or user of PicoContainer components. The design is so simple, that for very tightly coupled deployments, a developer could cherry pick components and embed them in their application without even importing let alone using anything from the org.picocontainer codebase.
Diversity:
From the abstractions, other container developers can build containers compatible and interoperable with PicoContainer. We encourage diversity of implementation as we are not building a single container. In terms of the PicoContainer deliverable, there are no external Jar dependancies, and no use of XML for component declarations. Along with the PicoContainer deliverable, there is a Technology Compatability Kit (TCK). This is in the form of the abstract JUnit test cases. A container developer can use this to ensure than their implementation of a PicoContainer is compatible with the design . Container Developers May Choose from-scratch designs, wrapping of existing classes, or extenting existing classes.nanocontainer:
As a sister project to PicoContainer, we also have NanoContainer. Like PicoContainer, NanoContainer is more than one container. All are built to the PicoContainer design, and offer different embeddable visions. One interoperates with Nanning (the aspect framework) to provide aspect capability for Arbitary Components. Another Retrofits JMX Compatabase. Some of the Nanocontainers Deliver Component Assembly And Configuration VIA XML.
The Plan:
.
- The Picocontainer Team.
Visit
Www.picocontainer.org
