[SLING-6782] Sling Job implementation should avoid unnecessary writes to the repository

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Event 4.2.2
• Fix Version/s: Event 4.2.4
• Component/s: Event
• Assignee: Carsten Ziegeler
• Reporter: Joerg Hoh
• Created: 18/Apr/17 19:39
• Updated: 20/Sep/17 11:17
• Resolved: 05/May/17 09:23

Description

I found in a number of occurences in the Sling Event code this pattern:

                        ResourceHelper.getOrCreateResource(resolver, newPath, props);
                        resolver.delete(jobResource);
                        resolver.commit();

and the getOrCreateResource is internally doing a commit on the resolver (autoCommit = true). So in the end there are 2 commits while only a single commit would be sufficient.

Removing these "double" commits could avoid a few write operations on the repository.