public class SpringPersistenceManagerProxyBean extends java.lang.Object implements FactoryBean<javax.jdo.PersistenceManager>, InitializingBean
PersistenceManagerinterface, delegating to the current thread-bound PersistenceManager (the Spring-managed transactional PersistenceManager or the single OpenPersistenceManagerInView PersistenceManager, if any) on each invocation. This class makes such a Spring-style PersistenceManager proxy available for bean references.
The main advantage of this proxy is that it allows DAOs to work with a
plain JDO PersistenceManager reference in JDO 3.0 style
while still participating in Spring's resource and transaction management.
The behavior of this proxy matches the behavior that the JDO 3.0 spec
defines for a PersistenceManager proxy. Hence, DAOs could seamlessly switch
StandardPersistenceManagerProxyBean and this Spring-style proxy,
receiving the reference through Dependency Injection. This will work without
any Spring API dependencies in the DAO code!
|Constructor and Description|
|Modifier and Type||Method and Description|
Invoked by the containing
Return the JDO dialect to use for this proxy.
Return an instance (possibly shared or independent) of the object managed by this factory.
Return the type of object that this FactoryBean creates, or
Return the target PersistenceManagerFactory for this proxy.
Return the PersistenceManager interface to expose.
Return whether the PersistenceManagerFactory proxy is allowed to create a non-transactional PersistenceManager when no transactional PersistenceManager can be found for the current thread.
Is the object managed by this factory a singleton? That is, will
Set whether the PersistenceManagerFactory proxy is allowed to create a non-transactional PersistenceManager when no transactional PersistenceManager can be found for the current thread.
Set the JDO dialect to use for this proxy.
Set the target PersistenceManagerFactory for this proxy.
Specify the PersistenceManager interface to expose, possibly including vendor extensions.
public void setPersistenceManagerFactory(javax.jdo.PersistenceManagerFactory persistenceManagerFactory)
protected javax.jdo.PersistenceManagerFactory getPersistenceManagerFactory()
public void setJdoDialect(JdoDialect jdoDialect)
Default is a DefaultJdoDialect based on the PersistenceManagerFactory's underlying DataSource, if any.
protected JdoDialect getJdoDialect()
public void setPersistenceManagerInterface(java.lang.Class<? extends javax.jdo.PersistenceManager> persistenceManagerInterface)
Default is the standard
protected java.lang.Class<? extends javax.jdo.PersistenceManager> getPersistenceManagerInterface()
public void setAllowCreate(boolean allowCreate)
Default is "true". Can be turned off to enforce access to
transactional PersistenceManagers, which safely allows for DAOs
written to get a PersistenceManager without explicit closing
call without corresponding
protected boolean isAllowCreate()
public void afterPropertiesSet()
BeanFactoryafter it has set all bean properties and satisfied
This method allows the bean instance to perform validation of its overall configuration and final initialization when all bean properties have been set.
public javax.jdo.PersistenceManager getObject()
As with a
BeanFactory, this allows support for both the
Singleton and Prototype design pattern.
If this FactoryBean is not fully initialized yet at the time of
the call (for example because it is involved in a circular reference),
throw a corresponding
As of Spring 2.0, FactoryBeans are allowed to return
objects. The factory will consider this as normal value to be used; it
will not throw a FactoryBeanNotInitializedException in this case anymore.
FactoryBean implementations are encouraged to throw
FactoryBeanNotInitializedException themselves now, as appropriate.
public java.lang.Class<? extends javax.jdo.PersistenceManager> getObjectType()
nullif not known in advance.
This allows one to check for specific types of beans without instantiating objects, for example on autowiring.
In the case of implementations that are creating a singleton object, this method should try to avoid singleton creation as far as possible; it should rather estimate the type in advance. For prototypes, returning a meaningful type here is advisable too.
This method can be called before this FactoryBean has been fully initialized. It must not rely on state created during initialization; of course, it can still use such state if available.
NOTE: Autowiring will simply ignore FactoryBeans that return
null here. Therefore it is highly recommended to implement
this method properly, using the current state of the FactoryBean.
nullif not known at the time of the call
public boolean isSingleton()
FactoryBean.getObject()always return the same object (a reference that can be cached)?
NOTE: If a FactoryBean indicates to hold a singleton object,
the object returned from
getObject() might get cached
by the owning BeanFactory. Hence, do not return
unless the FactoryBean always exposes the same reference.
The singleton status of the FactoryBean itself will generally be provided by the owning BeanFactory; usually, it has to be defined as singleton there.
NOTE: This method returning
false does not
necessarily indicate that returned objects are independent instances.
An implementation of the extended
may explicitly indicate independent instances through its
SmartFactoryBean.isPrototype() method. Plain
implementations which do not implement this extended interface are
simply assumed to always return independent instances if the
isSingleton() implementation returns