[
https://issues.apache.org/jira/browse/SLING-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196986#comment-13196986
]
Reto Bachmann-Gmür commented on SLING-2191:
-------------------------------------------
In some situations an alternative to using opting-servlets as afallback is to
use servlet filters. As this is done with my lates patch for SLING-2192 (which
is awaiting review and acceptance), howver this has the consequence that one
cannot first rely on the default sling resolution mechanism and fallback to the
alternative but that it has to be the other way round.
Previous posts on the list indicate that OptingServlet has indeed been seen as
a generic fallback mechanism
Quoting
http://mail-archives.apache.org/mod_mbox/sling-dev/200909.mbox/%3Cf767f0600909140441l49c34d6bo2ae615ecc436592d%40mail.gmail.com%3E
>> ...The OptingServlet sounds interesting. It means that I can register several
>> servlets for the same resourceType and implement accept() accordingly?..
>
>Yes, that's the idea, for those (hopefully rare) cases where the other
>mechanisms aren't sufficient.
Also the test for OptingServlet seem to suggest such a usecase. I fully agree
with the "hopefully rare" remark, but I think this a generic property of a
fallback mechanism.
> 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
