Hi, in our Sling application we create jobs for long-running tasks using the JobManager service, and in those jobs, subtasks are scheduled to a separate compute grid.
What I was curious about was whether there was any way to asynchronously detect and perform cleanup when a job is stopped by the user via jobManager.stopJobById(). Or is it that the only way to handle this is to intersperse checks for the job STOPPED state throughout logic that I've implemented under the process() method of each JobConsumer that I've implemented? >From the documentation and codte, it looks like I have to do the latter, but I >thought I'd check as if the former were possible it might simplify the job >cancellation processing, and it would allow canceled jobs to be cleaned up >more quickly. Thank you! John Logan
