[
https://issues.apache.org/jira/browse/SLING-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196135#comment-13196135
]
Carsten Ziegeler commented on SLING-2191:
-----------------------------------------
Ok, granted the javadocs of the opting servlet are not very specific - however,
the intend has always been to just mark a registered servlet as optional which
allows the servlet to refuse to handle a request. This assumes the whole
resolution process with the way it works today where it is not possible to have
several servlets at the registraion location (with the same properties), except
choosing the /libs, /apps approach.
This still allows for a relatively clear resolution process. Opening this up
makes it way harder to follow what really is going on. Having let's say 10
opting servlets for the same resource, where you except that just one of them
at a time processes the resource is not the intention of the OptingServlet. And
I can already imagine the additional confusion and misuse it will provide.
I fail to see why registering a dispatcher servlet in your case does not solve
your problem? Writing this servlet is really easy and instead of using some
properties defined by Sling to mount this servlet, you define one or two custom
ones, and tell your teams to use them instead. This does neither create more
overhead nor does it require more communication between your teams. And the
interfaces would still be the same, so except of changing properties no need to
change any code.
> Allow multiple OptingServletS for the same resource type
> --------------------------------------------------------
>
> Key: SLING-2191
> URL: https://issues.apache.org/jira/browse/SLING-2191
> Project: Sling
> Issue Type: Bug
> Reporter: Reto Bachmann-Gmür
> Attachments: SLING-2191-tests-launchpad.patch
>
>
> It should be possible to have multiple OptinServlets (accepting different
> sets of requests) for the same resource type.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
