On 10/11/07, Felix Meschberger <[EMAIL PROTECTED]> wrote: > ...I am also not sure, whether script resolution according to the resource > path is actually a good idea...
You're right, that was a bad idea...I have added a String getResourceType(); method to the Resource interface, which is meant to point to a repository location where scripts and other definitions can be found. And rewritten the SlingScriptResolver to use this. Script names are also based on the request extension now, so for example if a scripting SlingServlet is looking for a script with a "vlt" extension: When rendering a Resource with resourceType=/some/stuff For a GET request with with URL extension=html The SlingScriptResolver looks for a script named /sling/scripts/some/stuff/get.html.vlt The updated microsling-homepage.html attached to https://issues.apache.org/jira/browse/SLING-47 contains links to source code for a quick code walkthrough. Do you guys think we need to add more stuff to microsling to reflect the core ideas of the Sling request processing? ResponseFilters maybe? -Bertrand.
