Hi Chetan Am 02.09.2012 um 10:11 schrieb Chetan Mehrotra:
>> I am not sure whether it is possible at all to have a single plugin suitable >> for all of the Http Service plus any existing frameworks ... This would >> rather be something pluggable... > > A - Would it make sense to implement a new plugin in Http base module. > As the Http base module has access to all the internal state and which > is also super set of information present with Http Whiteboard module. > This plugin can dump all the information present in HandlerRegistry. +1 > > B - Further it can expose some API similar to ConfigurationPrinter say > ServletConfigPrinter. This API can then be implemented by Sling > servlet resolver module module which provide the information it has > about various servlets it manages. The information might consist of > > 1. Servlet Alias > 2. Servlet Class > 3. Bundle which provides that servlet > > Similarly information about registered filters can be captured The problem is that for Sling there is no "Servlet alias" and servlet selection for request exection is really special and a lot more elaborate than plain Servlet API. We (Sling) could of course fold the servlet registration paths (we use for Servlet Resource Registration) into a multi-value alias definition. But I am not sure, whether this helps, really. Regards Felix > > Chetan Mehrotra > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
