类 TimerManagerFactoryBean
- java.lang.Object
- org.springframework.jndi.JndiAccessor
- org.springframework.jndi.JndiLocatorSupport
- org.springframework.scheduling.commonj.TimerManagerAccessor
- org.springframework.scheduling.commonj.TimerManagerFactoryBean
- 所有已实现的接口:
DisposableBean
,FactoryBean<TimerManager>
,InitializingBean
,Lifecycle
@Deprecated public class TimerManagerFactoryBean extends TimerManagerAccessor implements FactoryBean<TimerManager>, InitializingBean, DisposableBean, Lifecycle
已过时。as of 5.1, in favor of EE 7'sDefaultManagedTaskScheduler
FactoryBean
that retrieves a CommonJTimerManager
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.
- 从以下版本开始:
- 2.0
- 作者:
- Juergen Hoeller
- 另请参阅:
ScheduledTimerListener
,TimerManager
,TimerListener
字段概要
从类继承的字段 org.springframework.jndi.JndiLocatorSupport
CONTAINER_PREFIX
从类继承的字段 org.springframework.jndi.JndiAccessor
logger
从接口继承的字段 org.springframework.beans.factory.FactoryBean
OBJECT_TYPE_ATTRIBUTE
构造器概要
构造器 构造器 说明 TimerManagerFactoryBean()
已过时。
方法概要
所有方法 实例方法 具体方法 已过时的方法 修饰符和类型 方法 说明 void
afterPropertiesSet()
已过时。Invoked by the containingBeanFactory
after it has set all bean properties and satisfiedBeanFactoryAware
,ApplicationContextAware
etc.void
destroy()
已过时。Cancels all statically registered Timers on shutdown, and stops the underlying TimerManager (if not shared).TimerManager
getObject()
已过时。Return an instance (possibly shared or independent) of the object managed by this factory.Class<? extends TimerManager>
getObjectType()
已过时。Return the type of object that this FactoryBean creates, ornull
if not known in advance.boolean
isSingleton()
已过时。Is the object managed by this factory a singleton?void
setScheduledTimerListeners(ScheduledTimerListener[] scheduledTimerListeners)
已过时。Register a list of ScheduledTimerListener objects with the TimerManager that this FactoryBean creates.从类继承的方法 org.springframework.scheduling.commonj.TimerManagerAccessor
getTimerManager, isRunning, obtainTimerManager, setShared, setTimerManager, setTimerManagerName, start, stop
从类继承的方法 org.springframework.jndi.JndiLocatorSupport
convertJndiName, isResourceRef, lookup, lookup, setResourceRef
从类继承的方法 org.springframework.jndi.JndiAccessor
getJndiEnvironment, getJndiTemplate, setJndiEnvironment, setJndiTemplate
构造器详细资料
TimerManagerFactoryBean
public TimerManagerFactoryBean()
已过时。
方法详细资料
setScheduledTimerListeners
public void setScheduledTimerListeners(ScheduledTimerListener[] scheduledTimerListeners)
已过时。Register a list of ScheduledTimerListener objects with the TimerManager that this FactoryBean creates. Depending on each ScheduledTimerListener's settings, it will be registered via one of TimerManager's schedule methods.
afterPropertiesSet
public void afterPropertiesSet() throws NamingException
已过时。从接口复制的说明:InitializingBean
Invoked by the containingBeanFactory
after it has set all bean properties and satisfiedBeanFactoryAware
,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.
getObject
@Nullable public TimerManager getObject()
已过时。从接口复制的说明:FactoryBean
Return an instance (possibly shared or independent) of the object managed by this factory.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
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
在接口中FactoryBean<TimerManager>
- 返回:
- an instance of the bean (can be
null
) - 另请参阅:
FactoryBeanNotInitializedException
getObjectType
public Class<? extends TimerManager> getObjectType()
已过时。从接口复制的说明:FactoryBean
Return the type of object that this FactoryBean creates, ornull
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
在接口中FactoryBean<TimerManager>
- 返回:
- the type of object that this FactoryBean creates, or
null
if not known at the time of the call - 另请参阅:
ListableBeanFactory.getBeansOfType(java.lang.Class<T>)
isSingleton
public boolean isSingleton()
已过时。从接口复制的说明:FactoryBean
Is the object managed by this factory a singleton? That is, willFactoryBean.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 returntrue
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 extendedSmartFactoryBean
interface may explicitly indicate independent instances through itsSmartFactoryBean.isPrototype()
method. PlainFactoryBean
implementations which do not implement this extended interface are simply assumed to always return independent instances if theisSingleton()
implementation returnsfalse
.The default implementation returns
true
, since aFactoryBean
typically manages a singleton instance.- 指定者:
isSingleton
在接口中FactoryBean<TimerManager>
- 返回:
- whether the exposed object is a singleton
- 另请参阅:
FactoryBean.getObject()
,SmartFactoryBean.isPrototype()
destroy
public void destroy()
已过时。Cancels all statically registered Timers on shutdown, and stops the underlying TimerManager (if not shared).- 指定者:
destroy
在接口中DisposableBean
- 覆盖:
destroy
在类中TimerManagerAccessor
- 另请参阅:
Timer.cancel()
,TimerManager.stop()