An implementation of org.quartz.SchedulerFactory that
does all of its work of creating a QuartzScheduler instance
based on the contenents of a Properties file.
By default a properties file named "quartz.properties" is loaded from the
'current working directory'. If that fails, then the "quartz.properties"
file located (as a resource) in the org/quartz package is loaded. If you
wish to use a file other than these defaults, you must define the system
property 'org.quartz.properties' to point to the file you want.
See the sample properties files that are distributed with Quartz for
information about the various settings available within the file.
Alternatively, you can explicitly initialize the factory by calling one of
the initialize(xx) methods before calling getScheduler().
Instances of the specified org.quartz.spi.JobStore,
org.quartz.spi.ThreadPool, classes will be created
by name, and then any additional properties specified for them in the config
file will be set on the instance by calling an equivalent 'set' method. For
example if the properties file contains the property
'org.quartz.jobStore.myProp = 10' then after the JobStore class has been
instantiated, the method 'setMyProp()' will be called on it. Type conversion
to primitive Java types (int, long, float, double, boolean, and String) are
performed before calling the property's setter method.
author: James House author: Anthony Eden author: Mohammad Rezaei
Initialize the org.quartz.SchedulerFactory with
the contents of a Properties file and overriding System
properties.
By default a properties file named "quartz.properties" is loaded from
the 'current working directory'. If that fails, then the
"quartz.properties" file located (as a resource) in the org/quartz
package is loaded. If you wish to use a file other than these defaults,
you must define the system property 'org.quartz.properties' to point to
the file you want.
System properties (environment variables, and -D definitions on the
command-line when running the JVM) override any properties in the
loaded file. For this reason, you may want to use a different initialize()
method if your application security policy prohibits access to
java.lang.System.getProperties.