Transfer from: http://www.picocontainer.org/one minute Description
One Minute Description one minute a minute
Authors: Paul Hammant, Aslak Hellesoy, Jon Tirsen
What is picocontainer? What is the microemer?
Picocontainer is a lightweight container. It is a lightweight container IT IS Not a Replacement for a J2EE Container, as it doesn't Offer, INFRASTRUCTRUCTRUCTRUCTRUCTRUCTRUCTRUCTRUCTRUCTRUCTRUCE Services out of the box. It is not an alternative to the J2EE container, so it cannot be detached The infrastructure provides any basic service. (Here, I now understand the basic framework, if there is an error, please help me guidance. Thank you) IT can help you write better code. It can help you write more complete code.
What Does PicoContainer Do? What can I do with the microemers?
Dependency Injections and Lacing Them Together With Other Dependent Components. A method of initializing components and assembling components associated with them together. PicoContainer is non-intrusive. Components Don't Have To Implement Any Funny Apis. The Microerer is non-inserted. Components do not need to implement any special APIs, which can be a simple Java object (Pojos). Lifecycle Support is Built-in. Components' Lifecycle CAN Be Managed Easily by PicoContainer. (The Default Lifecycle IS Simple) Microerer integrates lifecycle management, which can easily manage the life cycle of components. (The default lifecycle management function is very simple, but it is can be extended) Very extensible design enabling virtually any form of extensions to the core. flexible design allows the core functions of any form of extension. It is embeddable inside other applications. a 50k jar that has no external dependencies except JDK 1.3. he can Embedded to other application services. In addition to JDK1.3, he can only 50K without any external class libraries.
How do I use picoContainer? How do I use a micro-capacity?
Components are implemented as ordinary Java classes and do typically not have to rely on any PicoContainer APIs. Implementation of a component can be basic java classes and does not rely on any API micro-containers. The components are assembled in the container using a simple Java API that is similar to a hash map. in the micro-container, using the java hash map to the mounting assembly. If lifecycle callbacks are required the simple lifecycle interfaces can be implemented. If you prefer to use your own lifecycle interfaces you can do that ( But Remember That Third Party Components Might Release. If you need a lifecycle management, you can use the container's own interfaces. If you need to use your own lifecycle management, you can implement your interface (but pay attention to Third-party components may rely on the default lifecycle management mode). WHY SHOULD I Use PicoContainer? Why should I use a micro-capacity?
To Modularize How Dependencies Between Parts of Your Application Are Laced Up. It is Common Having this Scattered All Over. Modular, allows the associated components together. In general, they will be dispersed in your application. TO Improve The Testability of Your Code. Improve the tester of your code. To Improve How Components Are Configured In Application. Physicality.
Next: Two Minute Tutorial Next: Two minute tutorial
