Hi Betrand, Cool !
"ScriptResolution" works somewhat differently as in current Sling, where the Component (aka Servlet) is resolved from the Content (aka Resource) and either directly implements the actions or selects the concrete script for the request from a limited set of scripts (generally one to only a very few number). As such the "presentation framework" integrations (VelocityTemplatesServlet, RhinoJavascriptServlet) operate in the "background" at the service of the Component and its script depending on the script selected. I am also not sure, whether script resolution according to the resource path is actually a good idea (of course it serves as a simple placeholder for a general principle). So further discussion should probably concretate on Servlet/ScriptResolution, right ? Or am I missing something ? Regards Felix Am Donnerstag, den 11.10.2007, 18:44 +0200 schrieb Bertrand Delacretaz: > Hi Sling community, > > I think the current revision of > http://svn.apache.org/repos/asf/incubator/sling/whiteboard/microsling > is worth having a look at if you're interested in the current API / > redesign discussions. > > Fifteen minutes should be enough to build it and have a look at how it > works, provided you have a JDK 1.5, Maven 2.0.7 and a WebDAV client > installed. The README.txt explains how to run it. > > I have attached the current microsling webapp homepage (which explains > what it is in more detail) to > https://issues.apache.org/jira/browse/SLING-47, just in case. > > -Bertrand
