[
https://issues.apache.org/jira/browse/SLING-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794548#comment-13794548
]
Stefan Seifert commented on SLING-3172:
---------------------------------------
as with the (now deprecated) job name i find it very cumbersome for the client
code to have to deal with unique names when posting jobs. in most scenarios
this will be "fire and forget" code and only in few usecase code has the need
to later reference the schedule and update it.
another topic is a possible management GUI: but in this case the scenario is
different. the mangement GUI is (normally) not the one which posts the jobs,
but which visualizes and manages it. thus the GUI needs to access to all
exsiting jobs, and than should have the possibility to change the schedule if
required. this should already be possible using the getScheduledJobs method.
for the first usecase with client code wanting to reschedule: if the
JobManager.getScheduledJob is transformed to something like
getScheduledJobById(<jobid>) it is possible to re-access a ScheduledJobInfo by
the jobid which was generated when starting the job, eliminating the schedule
name altogether.
> 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)
