On Tue, Apr 1, 2008 at 9:23 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> ...maybe an API > call such as > > boolean canHandle(SlingHttpServletRequest) > > in an interface, which a servlet may implement. If a servlet would be > selected which implements the method and returns false, the servlet > would be ignored for the resolution and the resolution process would > continue as if the servlet would not exist..... Maybe providing extension points for the ServletResolver would be cleaner, and allow for easier control of the priority of servlet resolution? We could use additional ServletResolver services, that the main ServletResolver would call in (configurable) priority order, and stop as soon as one returns a Servlet. A class can be both a Servlet and ServletResolver service, so this could be used in a similar way than what you suggest, but in addition allow more sophisticated resolving algorithms. WDYT? -Bertrand
