This interface is very similar to the interface except each method has an additional parameter.

Unless a database driver has some extremely-DB-specific requirements, any IDriverDelegate implementation classes should extend the class.

If removal of the results in an empty group, the group should be removed from the 's list of known group names.

If removal of the results in an 'orphaned' that is not 'durable', then the should be deleted also.

If removal of the results in an empty group, the group should be removed from the 's list of known group names.

If removal of the results in an 'orphaned' that is not 'durable', then the should be deleted also.

It is important to remember that the cron expression here describes a set of times to be excluded from firing. Whereas the cron expression in CronTrigger describes a set of times that can be included for firing. Thus, if a has a given cron expression and is associated with a with the same expression, the calendar will exclude all the times the trigger includes, and they will cancel each other out.

To create a scheduler that does not write anything to the database (is not persistent), you can call :

            DirectSchedulerFactory.Instance.CreateVolatileScheduler(10); // 10 threads 
            // don't forget to start the scheduler: 
            DirectSchedulerFactory.Instance.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, string schedulerInstanceId, ThreadPool threadPool, JobStore jobStore, string rmiRegistryHost, int rmiRegistryPort)
            

Here is an example of using this method:

            // create the thread pool 
            SimpleThreadPool threadPool = new SimpleThreadPool(maxThreads, Thread.NORM_PRIORITY); 
            threadPool.Initialize(); 
            // create the job store 
            JobStore jobStore = new RAMJobStore(); 
            jobStore.Initialize();
            
            DirectSchedulerFactory.Instance.CreateScheduler("My Quartz Scheduler", "My Instance", threadPool, jobStore, "localhost", 1099); 
            // don't forget to start the scheduler: 
            DirectSchedulerFactory.Instance.GetScheduler("My Quartz Scheduler", "My Instance").start();
            

This method is not cluster aware. That is, it will only return Jobs currently executing in this Scheduler instance, not across the entire cluster.

Note that the list returned is an 'instantaneous' snap-shot, and that as soon as it's returned, the true list of executing jobs may be different. Also please read the doc associated with - especially if you're using remoting.

When is called (to bring the scheduler out of stand-by mode), trigger misfire instructions will NOT be applied during the execution of the method - any misfires will be detected immediately afterward (by the 's normal process).

The scheduler is not destroyed, and can be re-started at any time.

If more than one instance of the identified job is currently executing, the method will be called on each instance. However, there is a limitation that in the case that on one instances throws an exception, all remaining instances (that have not yet been interrupted) will not have their method called.

If you wish to interrupt a specific instance of a job (when more than one is executing) you can do so by calling to obtain a handle to the job instance, and then invoke on it yourself.

This method is not cluster aware. That is, it will only interrupt instances of the identified InterruptableJob currently executing in this Scheduler instance, not across the entire cluster.

If more than one instance of the identified job is currently executing, the method will be called on each instance. However, there is a limitation that in the case that on one instances throws an exception, all remaining instances (that have not yet been interrupted) will not have their method called.

If you wish to interrupt a specific instance of a job (when more than one is executing) you can do so by calling to obtain a handle to the job instance, and then invoke on it yourself.

This method is not cluster aware. That is, it will only interrupt instances of the identified InterruptableJob currently executing in this Scheduler instance, not across the entire cluster.

By default a properties are loaded from App.config's quartz section. If that fails, then the "quartz.properties" file located (as a embedded resource) in Quartz.dll is loaded. If you wish to use a file other than these defaults, you must define the system property 'quartz.properties' to point to the file you want.

See the sample properties that are distributed with Quartz for information about the various settings available within the file.

Alternativly, you can explicitly Initialize the factory by calling one of the methods before calling .

Instances of the specified , , 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 'quartz.jobStore. myProp = 10' then after the JobStore class has been instantiated, the property 'MyProp' will be set with the value. Type conversion to primitive CLR types (int, long, float, double, boolean, enum and string) are performed before calling the property's setter method.

The broadcasting behavior of this listener to delegate listeners may be more convenient than registering all of the listeners directly with the Trigger, and provides the flexibility of easily changing which listeners get notified.

You may also register a number of Regular Expression patterns to match the events against. If one or more patterns are registered, the broadcast will only take place if the event applies to a job who's name/group matches one or more of the patterns.

The broadcasting behavior of this listener to delegate listeners may be more convenient than registering all of the listeners directly with the Trigger, and provides the flexibility of easily changing which listeners get notified.

You may also register a number of Regular Expression patterns to match the events against. If one or more patterns are registered, the broadcast will only take place if the event applies to a trigger who's name/group matches one or more of the patterns.

Generally an instance of this listener would be registered as a global job listener, rather than being registered directly to a given job.

If for some reason there is a failure creating the trigger for the follow-up job (which would generally only be caused by a rare serious failure in the system, or the non-existence of the follow-up job), an error messsage is logged, but no other action is taken. If you need more rigorous handling of the error, consider scheduling the triggering of the flow-up job within your job itself.

The methods in this class are empty so you only need to override the subset for the events you care about.

You are required to implement to return the unique name of your .

The methods in this class are empty so you only need to override the subset for the events you care about.

You are required to implement to return the unique name of your .

The logged message is customizable by setting one of the following message properties to a string that conforms to the syntax of .

JobToBeFiredMessage - available message data are:

Element	Data Type	Description
0	String	The Job's Name.
1	String	The Job's Group.
2	Date	The current time.
3	String	The Trigger's name.
4	String	The Triggers's group.
5	Date	The scheduled fire time.
6	Date	The next scheduled fire time.
7	Integer	The re-fire count from the JobExecutionContext.

The default message text is "Job {1}.{0} fired (by trigger {4}.{3}) at: {2, date, HH:mm:ss MM/dd/yyyy"

JobSuccessMessage - available message data are:

Element	Data Type	Description
0	String	The Job's Name.
1	String	The Job's Group.
2	Date	The current time.
3	String	The Trigger's name.
4	String	The Triggers's group.
5	Date	The scheduled fire time.
6	Date	The next scheduled fire time.
7	Integer	The re-fire count from the JobExecutionContext.
8	Object	The string value (toString() having been called) of the result (if any) that the Job set on the JobExecutionContext, with on it. "NULL" if no result was set.

The default message text is "Job {1}.{0} execution complete at {2, date, HH:mm:ss MM/dd/yyyy} and reports: {8"

JobFailedMessage - available message data are:

Element	Data Type	Description
0	String	The Job's Name.
1	String	The Job's Group.
2	Date	The current time.
3	String	The Trigger's name.
4	String	The Triggers's group.
5	Date	The scheduled fire time.
6	Date	The next scheduled fire time.
7	Integer	The re-fire count from the JobExecutionContext.
8	String	The message from the thrown JobExecution Exception.

The default message text is "Job {1}.{0} execution failed at {2, date, HH:mm:ss MM/dd/yyyy} and reports: {8"

JobWasVetoedMessage - available message data are:

Element	Data Type	Description
0	String	The Job's Name.
1	String	The Job's Group.
2	Date	The current time.
3	String	The Trigger's name.
4	String	The Triggers's group.
5	Date	The scheduled fire time.
6	Date	The next scheduled fire time.
7	Integer	The re-fire count from the JobExecutionContext.

The default message text is "Job {1}.{0} was vetoed. It was to be fired (by trigger {4}.{3}) at: {2, date, HH:mm:ss MM/dd/yyyy"

The logged message is customizable by setting one of the following message properties to a string that conforms to the syntax of .

TriggerFiredMessage - available message data are:

Element	Data Type	Description
0	String	The Trigger's Name.
1	String	The Trigger's Group.
2	Date	The scheduled fire time.
3	Date	The next scheduled fire time.
4	Date	The actual fire time.
5	String	The Job's name.
6	String	The Job's group.
7	Integer	The re-fire count from the JobExecutionContext.

The default message text is "Trigger {1}.{0} fired job {6}.{5} at: {4, date, HH:mm:ss MM/dd/yyyy"

TriggerMisfiredMessage - available message data are:

Element	Data Type	Description
0	String	The Trigger's Name.
1	String	The Trigger's Group.
2	Date	The scheduled fire time.
3	Date	The next scheduled fire time.
4	Date	The actual fire time. (the time the misfire was detected/handled)
5	String	The Job's name.
6	String	The Job's group.

The default message text is "Trigger {1}.{0} misfired job {6}.{5} at: {4, date, HH:mm:ss MM/dd/yyyy}. Should have fired at: {3, date, HH:mm:ss MM/dd/yyyy"

TriggerCompleteMessage - available message data are:

Element	Data Type	Description
0	String	The Trigger's Name.
1	String	The Trigger's Group.
2	Date	The scheduled fire time.
3	Date	The next scheduled fire time.
4	Date	The job completion time.
5	String	The Job's name.
6	String	The Job's group.
7	Integer	The re-fire count from the JobExecutionContext.
8	Integer	The trigger's resulting instruction code.
9	String	A human-readable translation of the trigger's resulting instruction code.

The default message text is "Trigger {1}.{0} completed firing job {6}.{5} at {4, date, HH:mm:ss MM/dd/yyyy} with resulting trigger instruction code: {9"

It should be extremely rare for this method to throw an exception - basically only the the case where there is no way at all to instantiate and prepare the Job for execution. When the exception is thrown, the Scheduler will move all triggers associated with the Job into the state, which will require human intervention (e.g. an application restart after fixing whatever configuration problem led to the issue wih instantiating the Job.

It should be extremely rare for this method to throw an exception - basically only the the case where there is no way at all to instantiate and prepare the Job for execution. When the exception is thrown, the Scheduler will move all triggers associated with the Job into the state, which will require human intervention (e.g. an application restart after fixing whatever configuration problem led to the issue wih instantiating the Job.

The xml document must conform to the format defined in "job_scheduling_data.xsd"

After creating an instance of this class, you should call one of the functions, after which you may call the function to get a handle to the defined Jobs and Triggers, which can then be scheduled with the . Alternatively, you could call the function to do all of this in one step.

The same instance can be used again and again, with the list of defined Jobs being cleared each time you call a method, however a single instance is not thread-safe.

Cron expressions are comprised of 6 required fields and one optional field separated by white space. The fields respectively are described as follows:

The '*' character is used to specify all values. For example, "*" in the minute field means "every minute".

The '?' character is allowed for the day-of-month and day-of-week fields. It is used to specify 'no specific value'. This is useful when you need to specify something in one of the two fields, but not the other.

The '-' character is used to specify ranges For example "10-12" in the hour field means "the hours 10, 11 and 12".

The ',' character is used to specify additional values. For example "MON,WED,FRI" in the day-of-week field means "the days Monday, Wednesday, and Friday".

The '/' character is used to specify increments. For example "0/15" in the seconds field means "the seconds 0, 15, 30, and 45". And "5/15" in the seconds field means "the seconds 5, 20, 35, and 50". Specifying '*' before the '/' is equivalent to specifying 0 is the value to start with. Essentially, for each field in the expression, there is a set of numbers that can be turned on or off. For seconds and minutes, the numbers range from 0 to 59. For hours 0 to 23, for days of the month 0 to 31, and for months 1 to 12. The "/" character simply helps you turn on every "nth" value in the given set. Thus "7/6" in the month field only turns on month "7", it does NOT mean every 6th month, please note that subtlety.

The 'L' character is allowed for the day-of-month and day-of-week fields. This character is short-hand for "last", but it has different meaning in each of the two fields. For example, the value "L" in the day-of-month field means "the last day of the month" - day 31 for January, day 28 for February on non-leap years. If used in the day-of-week field by itself, it simply means "7" or "SAT". But if used in the day-of-week field after another value, it means "the last xxx day of the month" - for example "6L" means "the last friday of the month". When using the 'L' option, it is important not to specify lists, or ranges of values, as you'll get confusing results.

The 'W' character is allowed for the day-of-month field. This character is used to specify the weekday (Monday-Friday) nearest the given day. As an example, if you were to specify "15W" as the value for the day-of-month field, the meaning is: "the nearest weekday to the 15th of the month". So if the 15th is a Saturday, the trigger will fire on Friday the 14th. If the 15th is a Sunday, the trigger will fire on Monday the 16th. If the 15th is a Tuesday, then it will fire on Tuesday the 15th. However if you specify "1W" as the value for day-of-month, and the 1st is a Saturday, the trigger will fire on Monday the 3rd, as it will not 'jump' over the boundary of a month's days. The 'W' character can only be specified when the day-of-month is a single day, not a range or list of days.

The 'L' and 'W' characters can also be combined for the day-of-month expression to yield 'LW', which translates to "last weekday of the month".

The '#' character is allowed for the day-of-week field. This character is used to specify "the nth" XXX day of the month. For example, the value of "6#3" in the day-of-week field means the third Friday of the month (day 6 = Friday and "#3" = the 3rd one in the month). Other examples: "2#1" = the first Monday of the month and "4#5" = the fifth Wednesday of the month. Note that if you specify "#5" and there is not 5 of the given day-of-week in the month, then no firing will occur that month. If the '#' character is used, there can only be one expression in the day-of-week field ("3#1,6#3" is not valid, since there are two expressions).

The legal characters and the names of months and days of the week are not case sensitive.

NOTES:

• Support for specifying both a day-of-week and a day-of-month value is not complete (you'll need to use the '?' character in one of these fields).
• Overflowing ranges is supported - that is, having a larger number on the left hand side than the right. You might do 22-2 to catch 10 o'clock at night until 2 o'clock in the morning, or you might have NOV-FEB. It is very important to note that overuse of overflowing ranges creates ranges that don't make sense and no effort has been made to determine which interpretation CronExpression chooses. An example would be "0 0 14-6 ? * FRI-MON".

For those unfamiliar with "cron", this means being able to create a firing schedule such as: "At 8:00am every Monday through Friday" or "At 1:30am every last Friday of the month".

The format of a "Cron-Expression" string is documented on the class.

Here are some full examples:

Expression		Meaning
"0 0 12 * * ?"" />		Fire at 12pm (noon) every day" />
"0 15 10 ? * *"" />		Fire at 10:15am every day" />
"0 15 10 * * ?"" />		Fire at 10:15am every day" />
"0 15 10 * * ? *"" />		Fire at 10:15am every day" />
"0 15 10 * * ? 2005"" />		Fire at 10:15am every day during the year 2005" />
"0 * 14 * * ?"" />		Fire every minute starting at 2pm and ending at 2:59pm, every day" />
"0 0/5 14 * * ?"" />		Fire every 5 minutes starting at 2pm and ending at 2:55pm, every day" />
"0 0/5 14,18 * * ?"" />		Fire every 5 minutes starting at 2pm and ending at 2:55pm, AND fire every 5 minutes starting at 6pm and ending at 6:55pm, every day" />
"0 0-5 14 * * ?"" />		Fire every minute starting at 2pm and ending at 2:05pm, every day" />
"0 10,44 14 ? 3 WED"" />		Fire at 2:10pm and at 2:44pm every Wednesday in the month of March." />
"0 15 10 ? * MON-FRI"" />		Fire at 10:15am every Monday, Tuesday, Wednesday, Thursday and Friday" />
"0 15 10 15 * ?"" />		Fire at 10:15am on the 15th day of every month" />
"0 15 10 L * ?"" />		Fire at 10:15am on the last day of every month" />
"0 15 10 ? * 6L"" />		Fire at 10:15am on the last Friday of every month" />
"0 15 10 ? * 6L"" />		Fire at 10:15am on the last Friday of every month" />
"0 15 10 ? * 6L 2002-2005"" />		Fire at 10:15am on every last friday of every month during the years 2002, 2003, 2004 and 2005" />
"0 15 10 ? * 6#3"" />		Fire at 10:15am on the third Friday of every month" />