[
https://issues.apache.org/jira/browse/SLING-11315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534950#comment-17534950
]
Bertrand Delacretaz edited comment on SLING-11315 at 5/11/22 3:14 PM:
----------------------------------------------------------------------
I have tentatively added [a new
test|https://github.com/apache/sling-org-apache-sling-servlets-resolver/commit/1603a0ecb2ab8b4395560c0d53d9e5569b68a568]
to the servlets resolver module to check the current behavior.
Running the test multiple times it looks like it's the first registered servlet
that wins if two are registered with the same mount parameters.
I'm not sure if that's by design or just by chance, but refusing to register
the second servlet seems to make more sense to me in such cases. I'll discuss
[on our dev
list|https://lists.apache.org/thread/4dgf75dd4sdwyh851ovl7bxfo7wft008].
was (Author: bdelacretaz):
I have tentatively added [a new
test|https://github.com/apache/sling-org-apache-sling-servlets-resolver/commit/1603a0ecb2ab8b4395560c0d53d9e5569b68a568]
to the servlets resolver module to check the current behavior.
Running the test multiple times it looks like it's the first registered servlet
that wins if two are registered with the same mount parameters.
I'm not sure if that's by design or just by chance, but refusing to register
the second servlet seems to make more sense to me in such cases. I'll discuss
on our dev list.
> Reject duplicate servlet mount configurations
> ---------------------------------------------
>
> Key: SLING-11315
> URL: https://issues.apache.org/jira/browse/SLING-11315
> Project: Sling
> Issue Type: New Feature
> Components: Servlets
> Reporter: Adrian Kozma
> Priority: Major
>
> Multiple servlets having the same mount parameters should trigger an error.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)