|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Object | +--javatools.cron.Cron.CronConfig
Why do we make a separate class out of these two variables? It allows us to replace both atomically without resorting to using synchronized. (Which is to be avoided for performance and simplicity reasons).
Field Summary | |
(package private) java.util.List |
cronEntries
a collection of CronEntry objects. |
(package private) java.util.List |
schedule
This is the schedule of "soon to occur" events. |
Constructor Summary | |
(package private) |
Cron.CronConfig(java.util.List cronEntries)
|
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
Field Detail |
java.util.List cronEntries
java.util.List schedule
Constructor Detail |
Cron.CronConfig(java.util.List cronEntries)
|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |