[
https://issues.apache.org/jira/browse/SLING-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426314#comment-15426314
]
Konrad Windszus commented on SLING-5974:
----------------------------------------
Since coming up with a configurable misfire behaviour binds the API really
tightly to Quartz and would require quite some extensions to the API (because
not all options are available for all triggers). Also with the default misfire
behaviour explicitly documented I don't really feel the need of adjusting it
for a certain use case. Therefore just adjusting the javadoc is good enough for
the moment.
> Allow to configure misfire behaviour of Sling Scheduler
> -------------------------------------------------------
>
> Key: SLING-5974
> URL: https://issues.apache.org/jira/browse/SLING-5974
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Affects Versions: Commons Scheduler 2.5.0
> Reporter: Konrad Windszus
> Attachments: SLING-5974-javadoc-v1.patch
>
>
> Scheduler is internally relying on Quartz (http://www.quartz-scheduler.org/).
> Unfortunately the API exposed through Sling does not allow to configure the
> so misfire behaviour (compare with
> http://www.quartz-scheduler.org/documentation/quartz-2.x/tutorials/tutorial-lesson-04.html
> and https://dzone.com/articles/quartz-scheduler-misfire).
> Especially since the default misfire behaviour (called smart policy) differs
> by trigger type the default should be documented and it should be possible to
> overwrite the default.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
