Hi,
I think the script resolver should resolve scripts based primarily on
the content. This means based on the sling-content type, the Jcr
content type, including mixin types and only secondarily based on
attributes of the request like selectors.
What I would like to work out is how an intelligent script resolution
could work that allows multiple levels of fallbacks and that supports
mixin types.
Lars
On Oct 26, 2007, at 11:39 AM, Carsten Ziegeler <[EMAIL PROTECTED]>
wrote:
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]
