1 cron.getNextExecutions
This tag is useful to print in a calendar the execucions plan of programmed system tasks.
Returns a list with de dates of the following executions for a provided expression used to define the scheduler.
The number of dates that will be calculated it is defined by count attribute (by default 30).
<cron.getNextExecutions
expression='expression'
count='count'
/>
Attributes | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Name | Type | Required | Default | Description | |||||||||||||||||||||||||
Aexpression | string |
The expression that determines the scheduler. Cron-Expressions are strings that are actually made up of seven sub-expressions, that describe individual details of the schedule. These sub-expression are separated with white-space, and represent:
Individual sub-expressions can contain ranges and/or lists. For example, the day of week field in the previous (which reads “WED”) example could be replaced with “MON-FRI”, “MON,WED,FRI”, or even “MON-WED,SAT”. Wild-cards (the ‘’ character) can be used to say “every” possible value of this field. Therefore the ‘’ character in the “Month” field of the previous example simply means “every month”. A ‘*’ in the All of the fields have a set of valid values that can be specified. These values should be fairly obvious - such as the numbers 0 to 59 for seconds and minutes, and the values 0 to 23 for hours. Day-of-Month can be any value 1-31, but you need to be careful about how many days are in a given month! Months can be specified as values between 0 and 11, or by using the strings JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV and DEC. Days-of-Week can be specified as values between 1 and 7 (1 = Sunday) or by using the strings SUN, MON, TUE, WED, THU, FRI and SAT. The '*' character is used to specify all values. For example, "*" in the minute field means "every minute". The '?' character is allowed for the 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 The ‘/’ character can be used to specify increments to values. For example, if you put ‘0/15’ in the Minutes field, it means ‘every 15th minute of the hour, starting at minute zero’. If you used ‘3/20’ in the Minutes field, it would mean ‘every 20th minute of the hour, starting at minute three’ - or in other words it is the same as specifying ‘3,23,43’ in the Minutes field. Note the subtlety that “/35” does *not mean “every 35 minutes” - it mean “every 35th minute of the hour, starting at minute zero” - or in other words the same as specifying ‘0,35’. The ‘L’ character is allowed for the The 'W' character is allowed for the The 'L' and 'W' characters can also be combined for the The '#' character is allowed for the |
|||||||||||||||||||||||||||
Acount | int | 30 | Indicates the number of following times that must be calculated. |
Returns | |
---|---|
Type | Description |
ArryList<Date> | Returns an array with the dates of the following calculated executions. |
Expression | Scheduler |
---|---|
0 0/5 * * * ? | An expression to create a trigger that simply fires every 5 minutes. |
0 30 10-13 ? * WED,FRI | An expression to create a trigger that fires at 10:30, 11:30, 12:30, and 13:30, on every Wednesday and Friday. |
0 0/30 8-9 5,20 * ? | An expression to create a trigger that fires every half hour between the hours of 8 am and 10 am on the 5th and 20th of every month. Note that the trigger will NOT fire at 10:00 am, just at 8:00, 8:30, 9:00 and 9:30. |
Note that some scheduling requirements are too complicated to express with a single trigger - such as “every 5 minutes between 9:00 am and 10:00 am, and every 20 minutes between 1:00 pm and 10:00 pm”. The solution in this scenario is to simply create two triggers, and register both of them to run the same job.
The expression generates a scheduler starting on the first day of december at 12 hour and runs every 15 minutes. The count number it is not define so the result shows the first 30 calculated dates.
<xsql-script> <body> <iterator name='next'> <in> <cron.getNextExecutions expression='5 /15 * * 12 ?' /> </in> <do> <println><date.format format='dd-MM-yyyy hh:mm:ss'><next /></date.format></println> </do> </iterator> </body> </xsql-script>
01-12-2018 12:00:05
01-12-2018 12:15:05
01-12-2018 12:30:05
01-12-2018 12:45:05
01-12-2018 01:00:05
01-12-2018 01:15:05
01-12-2018 01:30:05
01-12-2018 01:45:05
01-12-2018 02:00:05
01-12-2018 02:15:05
01-12-2018 02:30:05
01-12-2018 02:45:05
01-12-2018 03:00:05
01-12-2018 03:15:05
01-12-2018 03:30:05
01-12-2018 03:45:05
01-12-2018 04:00:05
01-12-2018 04:15:05
01-12-2018 04:30:05
01-12-2018 04:45:05
01-12-2018 05:00:05
01-12-2018 05:15:05
01-12-2018 05:30:05
01-12-2018 05:45:05
01-12-2018 06:00:05
01-12-2018 06:15:05
01-12-2018 06:30:05
01-12-2018 06:45:05
01-12-2018 07:00:05
01-12-2018 07:15:05
The expression generates a scheduler that returns a plan to execute it every day (from now) on 10:15:05 time.
<xsql-script> <body> <iterator name='next'> <in> <cron.getNextExecutions expression='5 15 10 * * ?' count='10'/> </in> <do> <println><date.format format='dd-MM-yyyy hh:mm:ss'><next /></date.format></println> </do> </iterator> </body> </xsql-script>
[The sample is executed on 27-06-2018 16:14:34]
28-06-2018 10:15:05
29-06-2018 10:15:05
30-06-2018 10:15:05
01-07-2018 10:15:05
02-07-2018 10:15:05
03-07-2018 10:15:05
04-07-2018 10:15:05
05-07-2018 10:15:05
06-07-2018 10:15:05
07-07-2018 10:15:05