You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Hakim Sadikali (Resolved) (JIRA)" <ji...@apache.org> on 2012/02/16 06:34:59 UTC
[jira] [Resolved] (SLING-2421) Sling Event - JobManager Remove
[ https://issues.apache.org/jira/browse/SLING-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hakim Sadikali resolved SLING-2421.
-----------------------------------
Resolution: Invalid
My mistake, I had a class cast exception that was preventing items from being deleted.
I see how the flow works now:
((DefaultJobManager)this.jobManager).notifyRemoveJob(jobId);
actually removes the jobs from the list.
I'm still not sure why mine werent being deleted but I'll investigate further.
> Sling Event - JobManager Remove
> -------------------------------
>
> Key: SLING-2421
> URL: https://issues.apache.org/jira/browse/SLING-2421
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Extensions Event 3.1.2
> Reporter: Hakim Sadikali
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> The DefaultJobManager removeJob method does not remove the job from the allEventsByTopic map. This results in the two Maps being out of sync.
> The removeJob method should be similar (if not the same) as the notifyRemoveJob method
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira