[
https://issues.apache.org/jira/browse/SLING-10014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17253062#comment-17253062
]
Eric Norman commented on SLING-10014:
-------------------------------------
[~kwin] I hadn't heard of that best practice guidance, is it written down
somewhere that I can reference and review?
Honestly, I don't think it would be appropriate to register a servlet with an
unsatisfied dependency that you know isn't going to work. Do you mainly
object to the presence of the ServiceUserMapped reference, or just the error
reporting and visibility of the misconfigured server?
Would you be satisfied with some sort of validator component that logs a
warning and registers some temporary placeholder servlet in the place of these
well known unsatisfied servlets? Then if a user would attempt to invoke those
endpoints, the placeholder servlet could return a something like a 503 error
instead of falling through to the default handling?
> Use ServiceUserMapped to ensure presence of service user mapping
> ----------------------------------------------------------------
>
> Key: SLING-10014
> URL: https://issues.apache.org/jira/browse/SLING-10014
> Project: Sling
> Issue Type: Improvement
> Reporter: Eric Norman
> Assignee: Eric Norman
> Priority: Major
> Fix For: JCR Jackrabbit User Manager 2.2.14
>
>
> some functionality in the create user and change password servlets require
> the service user to be mapped.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
