你是否正在寻找关于schedulerfactorybean的内容?让我把最俱价值的东西奉献给你:
Return the ResourceLoader for the currently configured Quartz Scheduler, to be used by ResourceLoaderClassLoadHelper.
This instance will be set before initialization of the corresponding Scheduler, and reset immediately afterwards. It is thus only available during configuration.
See Also: , ResourceLoaderClassLoadHelperReturn the TaskExecutor for the currently configured Quartz Scheduler, to be used by LocalTaskExecutorThreadPool.
This instance will be set before initialization of the corresponding Scheduler, and reset immediately afterwards. It is thus only available during configuration.
See Also: , LocalTaskExecutorThreadPoolReturn the DataSource for the currently configured Quartz Scheduler, to be used by LocalDataSourceJobStore.
This instance will be set before initialization of the corresponding Scheduler, and reset immediately afterwards. It is thus only available during configuration.
See Also: , LocalDataSourceJobStoreReturn the non-transactional DataSource for the currently configured Quartz Scheduler, to be used by LocalDataSourceJobStore.
This instance will be set before initialization of the corresponding Scheduler, and reset immediately afterwards. It is thus only available during configuration.
See Also: , LocalDataSourceJobStoreSet the Quartz SchedulerFactory implementation to use.
Default is StdSchedulerFactory, reading in the standard quartz.properties from quartz.jar. To use custom Quartz properties, specify the "configLocation" or "quartzProperties" bean property on this FactoryBean.
See Also: StdSchedulerFactory, ,Set the name of the Scheduler to create via the SchedulerFactory.
If not specified, the bean name will be used as default scheduler name.
See Also: , ,Set the location of the Quartz properties config file, for example as classpath resource "classpath:quartz.properties".
Note: Can be omitted when all necessary properties are specified locally via this bean, or when relying on Quartz' default configuration.
See Also:Set Quartz properties, like "org.quartz.threadPool.class".
Can be used to override values in a Quartz properties config file, or to specify all necessary properties locally.
See Also:Set the Spring TaskExecutor to use as Quartz backend. Exposed as thread pool through the Quartz SPI.
Can be used to assign a JDK 1.5 ThreadPoolExecutor or a CommonJ WorkManager as Quartz backend, to avoid Quartz's manual thread creation.
By default, a Quartz SimpleThreadPool will be used, configured through the corresponding Quartz properties.
See Also: , LocalTaskExecutorThreadPool, ThreadPoolTaskExecutor, WorkManagerTaskExecutorSet the default DataSource to be used by the Scheduler. If set, this will override corresponding settings in Quartz properties.
Note: If this is set, the Quartz settings should not define a job store "dataSource" to avoid meaningless double configuration.
A Spring-specific subclass of Quartz' JobStoreCMT will be used. It is therefore strongly recommended to perform all operations on the Scheduler within Spring-managed (or plain JTA) transactions. Else, database locking will not properly work and might even break (e.g. if trying to obtain a lock on Oracle without a transaction).
Supports both transactional and non-transactional DataSource access. With a non-XA DataSource and local Spring transactions, a single DataSource argument is sufficient. In case of an XA DataSource and global JTA transactions, schedulerfactorybean's "nonTransactionalDataSource" property should be set, passing in a non-XA DataSource that will not participate in global transactions.
See Also: , , , LocalDataSourceJobStoreSet the DataSource to be used by the Scheduler for non-transactional access.
本文来自电脑杂谈,转载请注明本文网址:
http://www.pc-fly.com/a/jisuanjixue/article-3462-1.html
多少人丢了这份执着
尤其是反舰导弹和机场