On 10/30/07, Lars Trieloff <[EMAIL PROTECTED]> wrote: > ...I still think having a > level of inheriance and aspect-orientation in rendering is something > we want, because it eases the development process....
I agree that this might be useful in some cases - but do you think we can achieve this efficiently and simply with a path-based system for selecting scripts? I fear that it might be very hard to find rules for conflict resolution and priorities that work for all users. An alternative might be a kind of "meta-script" that, if present in the path where Sling starts looking for scripts, allows more flexible script/servlet selection: the ScriptResolver would execute or interpret that script, if it finds it, instead of using its default resolution mechanism. Something like the Cocoon sitemap mechanism, but local to the slingResourceType (or nodetype) path to keep things simple, and only concerned about script resolution. Without having looked at all the possible use-cases, I have a gut feeling that keeping the ScriptResolver simple, yet allowing scripted overrides, might be the best mix of simplicity and power. -Bertrand
