+1 for implementing support for multiple OptingServlets per resourceType/methods/etc combination
On Mon, Aug 22, 2011 at 9:10 AM, Bertrand Delacretaz <[email protected]> wrote: > Hi, > > I've been looking at SLING-2191 - it looks like if several > OptingServlets have the exact same registration parameters, only one > is actually used. > > In Reto's example there we have two servlets registered with > > @Property(name="sling.servlet.resourceTypes", value={ > "sling/servlet/default", > "sling/nonexisting" > }), > @Property(name="sling.servlet.methods", value={"POST","GET"}) > > which differ only in the results of their OptingServlet.accepts method. > > This causes their ServletResourceProviders to have the same provider > roots, am I correct to assume that this is what causes one of the > servlets to mask the other? > > 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. > > -Bertrand >
