Pico Container

# About

- What is PicoContainer?
- Introduction
- Javadoc
- Downloads
- News
- FAQ
- Project Goals
- Support

# Core Concepts

- Component Lifecycle
- Dependency Injection
- Scoped Containers

# Dependency Injection

- Constructor Injection
- Setter Injection
- Annotated Field Injection
- Annotated Method Injection
- Typed Field Injection
- Named Field Injection
- Method Injection
- Multiple Injection
- Composite Injection
- Factory Injection
- Reinjection
- Injection via Providers

# Configuration

- Disambiguation

# Modifying Component Behaviors

- Modifying Behaviors
- Caching and Singletons
- Hiding Implementations
- Thread Safety Behaviors
- AOP Style Interception

# Advanced Concepts

- Fluent Style
- Arrays, Collections and Maps
- Leveraging Parameter Names
- Building Containers
- Component Properties
- Component Configuration
- Monitoring Component Events

# PicoContainer's Architecture

- Design Patterns
- Inversion of Control
- Component Adapters
- Mock Objects
- Terminology
- Container Comparisons
- Transparency

# Container Choices

- DefaultPicoContainer
- CommandLinePicoContainer
- PropertiesPicoContainer
- SystemPropertiesPicoContainer
- TransientPicoContainer
- TieringPicoContainer

# Dependant & Related

- Web Frameworks
- Scripting Support
- Persistence
- Logging

# Anti-patterns

- Propagating Dependency
- Long Constructor Argument List
- Container Dependency
- Unit Tests Use Container
- Singleton

# Help Pages

- Ambiguous Injectable
- Unprocessed Properties

# History

- Inversion of Control History

# Project Info

- Project
- Team

# Hosted by

# Tools

## Constructor Injection

## Overview

Constructor Injection is a Dependency Injection variant where a component gets all its dependencies via its constructor.

The most important benefits of Constructor Injection are:

- It makes a strong dependency contract
- It makes testing easy, since dependencies can be passed in as Mock Objects
- It is very succinct in terms of lines of code
- Classes that rely on Constructor Injection are generally Good Citizens
- A dependency may be made immutable by making the dependency reference final

Martin Fowler explains Constructor Injection in more detail.

## Origin

In 2003, Rachel Davies, was reviewing book Java Open Source Programming for Joe Walnes. She left a Fermat-like margin note when looking at a code sample that used Setter Injection: "Why not use constructors ?". Brilliant and simple. Using constructors per se, is an ordinary OO feature, but having a container that works out what to inject where amongst a list of constructor arguments is something that is useful too. Read more about the back history.

## Example

    public class Apple {
        private final Orange orange;
        private final Pear pear;
        private final Banana banana;

        public Apple(Orange orange, Pear pear, Banana banana) {
            this.orange = orange;
            this.pear = pear;
            this.banana = banana;
        }

        // methods
    }

Note, for this there is no need to declare needs in any other way. No interfaces, no doclet tags, no external XML. Just your simple component(s) and PicoContainer. No need for post assembly/config initialization either. If it is constructed (not withstanding some asserts on nulls) it has its needs satisfied. Components need not be interface/implementation separated. This is the coder's choice.

### Using Constructor Injector Components Without a Container.

The component can be used directly, without any container. The missing dependency scenario is not an issue since it is impossible to instantiate an object without all dependencies being satisfied.

    Apple apple = new Apple(myOrange, aPear, theBanana);

### Using Constructor Injector Components With a PicoContainer

    pico = new DefaultPicoContainer(new ConstructorInjection());
    pico.addComponent(Apple.class);
    // etc
    Apple apple = pico.getComponent(Apple.class);

Constructor Injection, is a default too (via AdaptiveInjection):

    pico = new DefaultPicoContainer();
    pico.addComponent(Apple.class);
    // etc
    Apple apple = pico.getComponent(Apple.class);

The PicoContainer team recommends Constructor Injection over other types - the project was started to pioneer this approach. With PicoContainer is no need to mark up the constructor with an annotation. Having more than one constructor is OK too, as PicoContainer will try to use the one with the most arguments and fall back to ones with fewer if it cannot satisfy the longer ones.

The component factory for this is ConstructorInjection. It only handles constructor injection types of components. Factory AdaptiveInjection defaults to constructor injection, after checking first to see it the component in question is an Annotated Method or Field type (see below).

Constructor Injection is idiomatic PicoContainer - choose this style over all others if you can - especially if you are starting out with Dependency Injection.

## Summary

PicoContainer was the first lightweight container to support and popularize this for of dependency injection. PicoContainer also supports Setter Injection that is idiomatic of the Spring Framework.