Hi, Am Montag, den 18.02.2008, 09:57 +0100 schrieb Bertrand Delacretaz: > >... * The LaunchpadDefaultServlet and its renderers should be moved > > to the sling/servlet-resolver module and become the Sling default > > servlet. The servlet is registered for the sling/servlet/default > > resource type and the request method GET.... > > Why the servlet-resolver module? These renderers have nothing to do > with resolving Resources, IMHO they would deserve their own > sling/renderers or sling/default-servlet module.
Well the servlet-resolver has nothing to do with resource resolution either ;-) In fact, this bundle is probably slightly wrong-named as it contains the following: * The actual ServletResolver and ScriptResolver implementations * Implementation of ResourceProvider for Servlets * Default ErrorHandler servlet * Default "DefaultServlet" As such, I think moving the launchpad default servlet with its renderers to the servlet-resolver bundle looks like natural - in fact we should probably tear the LaunchpadDefaultServlet and the renderers apart as servlets by be registered for explicit extensions and the LaunchpadDefaultServlet may be kept as a final fallback. Dispatching with renderers is not required any more. But we may as well create a small bundle just containing the per-extension rendering servlets. Regards Felix
