You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2013/10/15 00:11:41 UTC

[jira] [Created] (SLING-3172) Job schedule name handling

Stefan Seifert created SLING-3172:
-------------------------------------

             Summary: Job schedule name handling
                 Key: SLING-3172
                 URL: https://issues.apache.org/jira/browse/SLING-3172
             Project: Sling
          Issue Type: Improvement
          Components: Extensions
            Reporter: Stefan Seifert
            Priority: Minor
             Fix For: Extensions Event 3.3.0


follow-up from SLING-3028

Q: JobBuilder.schedule - for what is the parameter "name" used? i does not get its meaning from the javadocs. why is it required to make it unique?

A: Schedule Name: each schedule gets a unique name to identify it and have a way to update the schedule or unschedule it. The other option I see would be to create a unique scheduling id when a new schedule is created and then use this to reference it. But in that case the client needs to store this id somewhere. If you think that this needs further enhancements or changes, please open a separate ticket.



--
This message was sent by Atlassian JIRA
(v6.1#6144)