On Mon, Aug 22, 2011 at 3:54 PM, Bertrand Delacretaz <[email protected]> wrote: > Yes, in this case (SLING-2192 is the final use case) it's probably > better for the OptingServlet to be mounted on a path as opposed to > resource types, and manage what's happening in there.
Not sure how I register to the root uri space. Also, it seems like the same problem could occur if another applications want to register an opting servlet to the same (root) uri space. If sling would support path matching with regex a path bound servlet could be registered for every root resource. Current OptingServlets seems the best approach. Reto
