[SLING-1473] Resolve script resource lazy

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Scripting Core 2.0.10
• Fix Version/s: Scripting Core 2.0.14
• Component/s: Scripting
• Assignee: Carsten Ziegeler
• Reporter: Carsten Ziegeler
• Created: 06/Apr/10 09:08
• Updated: 02/Nov/10 13:21
• Resolved: 06/Apr/10 09:09

Description

The script implementations use the SlingScript.getScriptResource().getPath() as a unique key for the script. The script resource is resolved in the current user context. This results in unnecessary resolutions during script executions just to get the path of the script - especially with a jcr backed resource this is quiet expensive.
Therefore we should rather use a lazy resource implementation which directly responds to getResourcePath() for getScriptResource(). Only if other methods of the Resource interface are used, the resource should be resolved.
First test showed a hugh performance increase of a lot of scripts are used to render a single request.