On Wed, Aug 24, 2011 at 2:13 PM, Carsten Ziegeler <[email protected]> wrote: > Maybe I'm missing a point, but if that's the case why do you install > the test-services? I'm proposing my patch for integration into sling, so it shouldn't break the tests and I'd like to add a test testing the feature. I could simply modify the existing OptingServletTest, but my impression was (and still is) that it is a bug that one can have only one OptingServlet for a ResourceType as imho the skipping of a servlet by the framework invoking accept is of little use if there is only one servlet. Also it seems to contradict the idea of OptingServlet as described in
http://mail-archives.apache.org/mod_mbox/sling-dev/200909.mbox/%[email protected]%3E Cheers, Reto > > Regards > Carsten > > 2011/8/24 Reto Bachmann-Gmür <[email protected]>: >> On Wed, Aug 24, 2011 at 10:35 AM, Carsten Ziegeler <[email protected]> >> wrote: >>> >>> If I understand you correctly, you with JAX-RS you want to have >>> several (Opting)Servlets at the same path (handling the same resource >>> type). So instead of directly registering all these servlets at the >>> same path, you register a special JAX-RS servlet at this path which >>> then delegates to all the various servlets. >> If I could register servlet to a path-regex I could register a servlet >> for every resource. The current patch uses a Single Opting Servlet >> that accepts only the requests for which there is a root resource >> available. The problem is that this servlet is registered to the same >> resource as the one in test-services so that the jax-rs opting-servlet >> conflicts with the opting-servlet from test-services. >> >> Reto >> >>> >>> Carsten >>>> >>>> Regards, >>>> Reto >>>> >>> >>> >>> >>> -- >>> Carsten Ziegeler >>> [email protected] >>> >> > > > > -- > Carsten Ziegeler > [email protected] >
