Home >> All >> org >> quartz >> [ impl Javadoc ]

•	org.quartz.impl.calendar.* (5)	•	org.quartz.impl.jdbcjobstore.* (26)
•	org.quartz.impl.jdbcjobstore.oracle.* (2)

• org.quartz.impl: Javadoc index of package org.quartz.impl.


Package Samples:

• org.quartz.impl.calendar: Contains implementations of the SchedulerFactory, JobStore, ThreadPool, and other interfaces required by the org.quartz.core.QuartzScheduler.  
• org.quartz.impl.jdbcjobstore.oracle
• org.quartz.impl.jdbcjobstore

Classes:

• DirectSchedulerFactory: A singleton implementation of org.quartz.SchedulerFactory . Here are some examples of using this class: To create a scheduler that does not write anything to the database (is not persistent), you can call createVolatileScheduler : DirectSchedulerFactory.getInstance().createVolatileScheduler(10); // 10 threads * // don't forget to start the scheduler: DirectSchedulerFactory.getInstance().getScheduler().start(); Several create methods are provided for convenience. All create methods eventually end up calling the create method with all the parameters: public void createScheduler(String schedulerName, ...
• StdSchedulerFactory: An implementation of org.quartz.SchedulerFactory that does all of it's 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 ...
• QuartzServer: Instantiates an instance of Quartz Scheduler as a stand-alone program, if the scheduler is configured for RMI it will be made available. The main() method of this class currently accepts 0 or 1 arguemtns, if there is an argument, and its value is "console" , then the program will print a short message on the console (std-out) and wait for the user to type "exit" - at which time the scheduler will be shutdown. Future versions of this server should allow additional configuration for responding to scheduler events by allowing the user to specify org.quartz.JobListener , org.quartz.TriggerListener ...
• DriverDelegate: This is the base interface for all driver delegate classes. This interface is very similar to the org.quartz.spi.JobStore interface except each method has an additional java.sql.Connection parameter. Unless a database driver has some extremely-DB-specific requirements, any DriverDelegate implementation classes should extend the StdJDBCDelegate class.
• BaseCalendar: This implementation of the Calendar may be used (you don't have to) as a base class for more sophisticated one's. It merely implements the base functionality required by each Calendar. Regarded as base functionality is the treatment of base calendars. Base calendar allow you to chain (stack) as much calendars as you may need. For example to exclude weekends you may use WeeklyCalendar. In order to exclude holidays as well you may define a WeeklyCalendar instance to be the base calendar for HolidayCalendar instance.
• JobStoreTX: JobStoreTX is meant to be used in a standalone environment. Both commit and rollback will be handled by this class. If you need a org.quartz.spi.JobStore class to use within an application-server environment, use JobStoreCMT instead.
• StdJobRunShellFactory: Responsible for creating the instances of org.quartz.core.JobRunShell to be used within the org.quartz.core.QuartzScheduler instance. This implementation does not re-use any objects, it simply makes a new JobRunShell each time borrowJobRunShell() is called.
• JobStoreCMT: JobStoreCMT is meant to be used in an application-server environment that provides container-managed-transactions. No commit / rollback will be1 handled by this class. If you need commit / rollback, use JobStoreTX instead.
• StdJDBCConstants: This interface extends Constants to include the query string constants in use by the StdJDBCDelegate class.
• StdJDBCDelegate: This is meant to be an abstract base class for most, if not all, DriverDelegate implementations. Subclasses should override only those methods that need special handling for the DBMS driver in question.
• HolidayCalendar: This implementation of the Calendar stores a list of holidays (full days that are excluded from scheduling). The implementation DOES take the year into consideration, so if you want to exclude July 4th for the next 10 years, you need to add 10 entries to the exclude list.
• Constants: This interface can be implemented by any DriverDelegate class that needs to use the constants contained herein.
• OracleDelegate: This is a driver delegate for the Oracle JDBC driver. To use this delegate, jdbcDriverVendor should be configured as 'Oracle' with any jdbcDriverVersion .
• RemoteScheduler: An implementation of the Scheduler interface that remotely proxies all method calls to the equivalent call on a given QuartzScheduler instance, via RMI.
• MonthlyCalendar: This implementation of the Calendar excludes a set of days of the month. You may use it to exclude every 1. of each month for example. But you may define any day of a month.
• StdScheduler: An implementation of the Scheduler interface that directly proxies all method calls to the equivalent call on a given QuartzScheduler instance.
• SchedulerRepository: Holds references to Scheduler instances - ensuring uniqueness, and preventing garbage collection, and allowing 'global' lookups - all within a ClassLoader space.
• WeeklyCalendar: This implementation of the Calendar excludes a set of days of the week. You may use it to exclude weekends for example. But you may define any day of the week.
• AnnualCalendar: This implementation of the Calendar excludes a set of days of the year. You may use it to exclude bank holidays which are on the same date every year.
• WebLogicOracleDelegate: Handle Blobs correctly when Oracle is being used inside of Weblogic 8.1, as discussed at: http://edocs.bea.com/wls/docs81/jdbc/thirdparty.html#1043705
• StdRowLockSemaphore: An interface for providing thread/resource locking in order to protect resources from being altered by multiple threads at the same time.
• SimpleSemaphore: An interface for providing thread/resource locking in order to protect resources from being altered by multiple threads at the same time.
• Semaphore: An interface for providing thread/resource locking in order to protect resources from being altered by multiple threads at the same time.
• DB2v6Delegate: Quartz JDBC delegate for DB2 v6 databases. select count(name) had to be replaced with select count(*) .
• NoSuchDelegateException: Exception class for when a driver delegate cannot be found for a given configuration, or lack thereof.

Home | Contact Us | Privacy Policy | Terms of Service