java.lang.Object | ||
↳ | org.springframework.beans.factory.config.AbstractFactoryBean<T> | |
↳ | org.springframework.beans.factory.config.ObjectFactoryCreatingFactoryBean |
A FactoryBean
implementation that
returns a value which is an ObjectFactory
that in turn returns a bean sourced from a BeanFactory
.
As such, this may be used to avoid having a client object directly calling
getBean(String)
to get
a (typically prototype) bean from a
BeanFactory
, which would be a
violation of the inversion of control principle. Instead, with the use
of this class, the client object can be fed an
ObjectFactory
instance as a
property which directly returns only the one target bean (again, which is
typically a prototype bean).
A sample config in an XML-based
BeanFactory
might look as follows:
<beans> <!-- Prototype bean since we have state --> <bean id="myService" class="a.b.c.MyService" scope="prototype"/> <bean id="myServiceFactory" class="org.springframework.beans.factory.config.ObjectFactoryCreatingFactoryBean"> <property name="targetBeanName"><idref local="myService"/></property> </bean> <bean id="clientBean" class="a.b.c.MyClientBean"> <property name="myServiceFactory" ref="myServiceFactory"/> </bean> </beans>
The attendant MyClientBean
class implementation might look
something like this:
package a.b.c; import org.springframework.beans.factory.ObjectFactory; public class MyClientBean { private ObjectFactory<MyService> myServiceFactory; public void setMyServiceFactory(ObjectFactory<MyService> myServiceFactory) { this.myServiceFactory = myServiceFactory; } public void someBusinessMethod() { // get a 'fresh', brand new MyService instance MyService service = this.myServiceFactory.getObject(); // use the service object to effect the business logic... } }
An alternate approach to this application of an object creational pattern
would be to use the ServiceLocatorFactoryBean
to source (prototype) beans. The ServiceLocatorFactoryBean
approach
has the advantage of the fact that one doesn't have to depend on any
Spring-specific interface such as ObjectFactory
,
but has the disadvantage of requiring runtime class generation. Please do
consult the ServiceLocatorFactoryBean JavaDoc
for a fuller discussion of this issue.
[Expand]
Inherited Fields | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From class
org.springframework.beans.factory.config.AbstractFactoryBean
|
Public Constructors | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Eagerly create the singleton instance, if necessary.
| |||||||||||
This abstract method declaration mirrors the method in the FactoryBean
interface, for a consistent offering of abstract template methods.
| |||||||||||
Set the name of the target bean.
|
Protected Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Template method that subclasses must override to construct
the object returned by this factory.
|
[Expand]
Inherited Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From class
org.springframework.beans.factory.config.AbstractFactoryBean
| |||||||||||
From class
java.lang.Object
| |||||||||||
From interface
org.springframework.beans.factory.BeanClassLoaderAware
| |||||||||||
From interface
org.springframework.beans.factory.BeanFactoryAware
| |||||||||||
From interface
org.springframework.beans.factory.DisposableBean
| |||||||||||
From interface
org.springframework.beans.factory.FactoryBean
| |||||||||||
From interface
org.springframework.beans.factory.InitializingBean
|
Eagerly create the singleton instance, if necessary.
Exception |
---|
This abstract method declaration mirrors the method in the FactoryBean interface, for a consistent offering of abstract template methods.
null
if not known at the time of the callSet the name of the target bean.
The target does not have> to be a non-singleton bean, but realisticially always will be (because if the target bean were a singleton, then said singleton bean could simply be injected straight into the dependent object, thus obviating the need for the extra level of indirection afforded by this factory approach).
Template method that subclasses must override to construct the object returned by this factory.
Invoked on initialization of this FactoryBean in case of
a singleton; else, on each getObject()
call.