Package net.sf.jguiraffe.di.impl.providers

In the providers sub package different implementations of the BeanProvider interface can be found.

See: Description

Class Summary

Class	Description
CollectionBeanProvider	An abstract base class for BeanProvider implementations that create beans derived from collections.
ConstantBeanProvider	A concrete implementation of the BeanProvider interface that will always return the same bean instance.
ConstructorBeanProvider	A simple bean provider that creates new bean instances by invoking a constructor.
FactoryBeanProvider	A specialized life-cycle supporting BeanProvider implementation for creating new bean instances on each invocation.
LifeCycleBeanProvider	An abstract base class for BeanProvider implementations with life-cycle support.
ListBeanProvider	A specific CollectionBeanProvider implementation that creates a list bean.
MapBeanProvider	A specialized BeanProvider implementation for creating beans of type java.util.Map.
MethodInvocationBeanProvider	A specialized BeanProvider that creates beans by invoking a method.
PropertiesBeanProvider	A specialized BeanProvider implementation for creating a java.util.Properties object.
SetBeanProvider	A specialized CollectionBeanProvider implementation that creates a java.util.Set bean.
SimpleBeanProvider	A base class for simple bean providers.
SingletonBeanProvider	A specialized life-cycle supporting BeanProvider implementation for creating singleton beans.

Package net.sf.jguiraffe.di.impl.providers Description

In the providers sub package different implementations of the BeanProvider interface can be found.

The implementations in this package can be divided into two groups:

• Simple providers are only responsible for creating new bean instances, which can happen in a bunch of different ways (e.g. calling Class.newInstance(), invoking a constructor, using a constant object).
• Life-cycle providers wrap a simple provider and add a certain semantic to the create operation. So an implementation exists that calls its simple provider only once and then caches the returned bean. This provider de facto implements a singleton. Another implementation will create a new bean instance for every transaction. These life-cycle providers also support enhanced initialization (e.g. by invoking methods on the created beans).

$Id: package.html 205 2012-01-29 18:29:57Z oheger $