[ https://issues.apache.org/jira/browse/SLING-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-3172. ------------------------------------- Resolution: Fixed I've dropped the name from the api for now, internally we use a uuid as the name to handle reschedule, unscheduling etc. > 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 > Assignee: Carsten Ziegeler > 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)