The proposed SlingScriptResolver is currenly only able to resolve a script based on the current sling request.
I think it makes sense to be able to resolve a script based on a path. A possible use case for this is to invoke some helper scripts during request processing, for example if I want to call some javascript script to do some funky stuff from within my java based component etc. I have no good idea how the method signature should look like? If it should take a path or a Resource? WDYT? Carsten -- Carsten Ziegeler [EMAIL PROTECTED]
