The servlet resolution is based on the resource resolution - and this means a path points at exactly one resource. This is nothing we should change! Again, OptingServlet should be the exception to be used as it makes the servlet resolution much more complicated. You have to run the request to see which servlet is really used. Therefore this should be avoided whereever possible.We found out, that in most cases there are better option.
For the case at hand, you could register a single servlet at that path - which is not an opting servlet and this one dispatches to the other servlets, one after the other, until one is processing this request. Regards Carsten 2011/8/22 Reto Bachmann-Gmür <[email protected]>: > On Mon, Aug 22, 2011 at 3:10 PM, Bertrand Delacretaz > <[email protected]> wrote: >> >> If I'm correct, we might need to use a single ServletResourceProvider >> in such a case, and allow it to point to a set of OptingServlet. > This set could be ordered by service priority. > > I think it is important to support multiple OptingServlets with the > same registrations. The Patch I attached to SLING-2192 to support > jax-rs resources works reliably as long as the test-services are not > installed, otherwise the OptingServlets conflict. > > Reto > -- Carsten Ziegeler [email protected]
