You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2016/08/18 11:58:20 UTC
[jira] [Updated] (SLING-5974) Allow to configure/document misfire
behaviour of Sling Scheduler
[ https://issues.apache.org/jira/browse/SLING-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated SLING-5974:
-----------------------------------
Summary: Allow to configure/document misfire behaviour of Sling Scheduler (was: Allow to configure misfire behaviour of Sling Scheduler)
> Allow to configure/document 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
> Fix For: Commons Scheduler 2.5.2
>
> 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)