[SLING-1687] JobStatusProvider should lazy load events when returning

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Event 2.3.0
• Fix Version/s: Event 2.4.0
• Component/s: Extensions
• Assignee: Carsten Ziegeler
• Reporter: Carsten Ziegeler
• Created: 24/Aug/10 06:00
• Updated: 06/Sep/10 14:02
• Resolved: 31/Aug/10 09:54

Description

The current implementation of the job status provider does a query, then loads all jobs and returns a list.
If you just want to know how many jobs are available or just want to return the first X jobs, the implementation is too expansive.

One solution would be to return a kind of range iterator instead of a list and load jobs on demand. There are two potential problems:

• if the jcr query does not return a count, we can't return a count either without going through the hole result set
• it might be that a job can't be loaded because of missing classes; in this cases the job count from the query result is higher than the count of the jobs that get processed. I think we can neglect this