类 TimerManagerAccessor

构造器详细资料

• TimerManagerAccessor

  public TimerManagerAccessor()

  已过时。

方法详细资料

• setTimerManager

  public void setTimerManager​(TimerManager timerManager)

  已过时。
  Specify the CommonJ TimerManager to delegate to.

  Note that the given TimerManager's lifecycle will be managed by this FactoryBean.

  Alternatively (and typically), you can specify the JNDI name of the target TimerManager.

  另请参阅:

  setTimerManagerName(java.lang.String)

• setTimerManagerName

  public void setTimerManagerName​(String timerManagerName)

  已过时。
  Set the JNDI name of the CommonJ TimerManager.

  This can either be a fully qualified JNDI name, or the JNDI name relative to the current environment naming context if "resourceRef" is set to "true".

  另请参阅:

  setTimerManager(commonj.timers.TimerManager), JndiLocatorSupport.setResourceRef(boolean)

• setShared

  public void setShared​(boolean shared)

  已过时。
  Specify whether the TimerManager obtained by this FactoryBean is a shared instance ("true") or an independent instance ("false"). The lifecycle of the former is supposed to be managed by the application server, while the lifecycle of the latter is up to the application.

  Default is "false", i.e. managing an independent TimerManager instance. This is what the CommonJ specification suggests that application servers are supposed to offer via JNDI lookups, typically declared as a resource-ref of type commonj.timers.TimerManager in web.xml, with res-sharing-scope set to 'Unshareable'.

  Switch this flag to "true" if you are obtaining a shared TimerManager, typically through specifying the JNDI location of a TimerManager that has been explicitly declared as 'Shareable'. Note that WebLogic's cluster-aware Job Scheduler is a shared TimerManager too.

  The sole difference between this FactoryBean being in shared or non-shared mode is that it will only attempt to suspend / resume / stop the underlying TimerManager in case of an independent (non-shared) instance. This only affects the Lifecycle support as well as application context shutdown.

  另请参阅:

  stop(), start(), destroy(), TimerManager

• afterPropertiesSet

  public void afterPropertiesSet()
                          throws NamingException

  已过时。
  从接口复制的说明: InitializingBean
  Invoked by the containing BeanFactory 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 在接口中 InitializingBean

  抛出:

  NamingException

• getTimerManager

  @Nullable
  protected final TimerManager getTimerManager()

  已过时。
  Return the configured TimerManager, if any.

  返回:

  the TimerManager, or null if not available

• obtainTimerManager

  protected TimerManager obtainTimerManager()

  已过时。
  Obtain the TimerManager for actual use.

  返回:

  the TimerManager (never null)

  抛出:

  IllegalStateException - in case of no TimerManager set

  从以下版本开始:

  5.0

• start

  public void start()

  已过时。
  Resumes the underlying TimerManager (if not shared).

  指定者:

  start 在接口中 Lifecycle

  另请参阅:

  TimerManager.resume()

• stop

  public void stop()

  已过时。
  Suspends the underlying TimerManager (if not shared).

  指定者:

  stop 在接口中 Lifecycle

  另请参阅:

  TimerManager.suspend()

• isRunning

  public boolean isRunning()

  已过时。
  Considers the underlying TimerManager as running if it is neither suspending nor stopping.

  指定者:

  isRunning 在接口中 Lifecycle

  返回:

  whether the component is currently running

  另请参阅:

  TimerManager.isSuspending(), TimerManager.isStopping()

• destroy

  public void destroy()

  已过时。
  Stops the underlying TimerManager (if not shared).

  指定者:

  destroy 在接口中 DisposableBean

  另请参阅:

  TimerManager.stop()