joerghoh opened a new pull request, #22: URL: https://github.com/apache/sling-org-apache-sling-event/pull/22
When using the suggested approach in the Sling documentation (https://sling.apache.org/documentation/bundles/apache-sling-eventing-and-job-handling.html#scheduled-jobs-1) the ```scheduleName``` is a random value. If on an OSGI component's activation a scheduledjob is registered that (and never unscheduled, because it's not documented, that you have to), you are registering a new scheduled job with each startup of this component. To avoid this situation, instead of selecting a random value a ```scheduleName``` with the value ``` null``` is provided. In this case the ```scheduleName``` is derived from the topic, the job properties and the schedule(s); that means that if this approach is used to register a scheduled job, it will be automatically deduplicated, and it's not possible anymore to register the very same job twice. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
