DefaultManagedTaskScheduler@Deprecated public class TimerManagerFactoryBean extends TimerManagerAccessor implements FactoryBean<TimerManager>, InitializingBean, DisposableBean, Lifecycle
FactoryBean that retrieves a
CommonJ TimerManager and exposes it for bean references.
This is the central convenience class for setting up a CommonJ TimerManager in a Spring context.
Allows for registration of ScheduledTimerListeners. This is the main
purpose of this class; the TimerManager itself could also be fetched
from JNDI via JndiObjectFactoryBean.
In scenarios that just require static registration of tasks at startup,
there is no need to access the TimerManager itself in application code.
Note that the TimerManager uses a TimerListener instance that is shared between repeated executions, in contrast to Quartz which instantiates a new Job for each execution.
ScheduledTimerListener,
TimerManager,
TimerListenerCONTAINER_PREFIXloggerOBJECT_TYPE_ATTRIBUTE| Constructor and Description |
|---|
TimerManagerFactoryBean()
Deprecated.
|
| Modifier and Type | Method and Description |
|---|---|
void |
afterPropertiesSet()
Deprecated.
Invoked by the containing
BeanFactory after it has set all bean properties
and satisfied BeanFactoryAware, ApplicationContextAware etc. |
void |
destroy()
Deprecated.
Cancels all statically registered Timers on shutdown,
and stops the underlying TimerManager (if not shared).
|
TimerManager |
getObject()
Deprecated.
Return an instance (possibly shared or independent) of the object
managed by this factory.
|
Class<? extends TimerManager> |
getObjectType()
Deprecated.
Return the type of object that this FactoryBean creates,
or
null if not known in advance. |
boolean |
isSingleton()
Deprecated.
Is the object managed by this factory a singleton? That is,
will
FactoryBean.getObject() always return the same object
(a reference that can be cached)? |
void |
setScheduledTimerListeners(ScheduledTimerListener[] scheduledTimerListeners)
Deprecated.
Register a list of ScheduledTimerListener objects with the TimerManager
that this FactoryBean creates.
|
getTimerManager, isRunning, obtainTimerManager, setShared, setTimerManager, setTimerManagerName, start, stopconvertJndiName, isResourceRef, lookup, lookup, setResourceRefgetJndiEnvironment, getJndiTemplate, setJndiEnvironment, setJndiTemplatepublic void setScheduledTimerListeners(ScheduledTimerListener[] scheduledTimerListeners)
public void afterPropertiesSet()
throws NamingException
InitializingBeanBeanFactory after it has set all bean properties
and satisfied BeanFactoryAware, ApplicationContextAware etc.
This method allows the bean instance to perform validation of its overall configuration and final initialization when all bean properties have been set.
afterPropertiesSet in interface InitializingBeanafterPropertiesSet in class TimerManagerAccessorNamingException@Nullable public TimerManager getObject()
FactoryBeanAs 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 FactoryBeanNotInitializedException.
As of Spring 2.0, FactoryBeans are allowed to return null
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.
getObject in interface FactoryBean<TimerManager>null)FactoryBeanNotInitializedExceptionpublic Class<? extends TimerManager> getObjectType()
FactoryBeannull if 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.
getObjectType in interface FactoryBean<TimerManager>null if not known at the time of the callListableBeanFactory.getBeansOfType(java.lang.Class<T>)public boolean isSingleton()
FactoryBeanFactoryBean.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 true
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 SmartFactoryBean interface
may explicitly indicate independent instances through its
SmartFactoryBean.isPrototype() method. Plain FactoryBean
implementations which do not implement this extended interface are
simply assumed to always return independent instances if the
isSingleton() implementation returns false.
The default implementation returns true, since a
FactoryBean typically manages a singleton instance.
isSingleton in interface FactoryBean<TimerManager>FactoryBean.getObject(),
SmartFactoryBean.isPrototype()public void destroy()
destroy in interface DisposableBeandestroy in class TimerManagerAccessorTimer.cancel(),
TimerManager.stop()