You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2017/04/26 14:29:04 UTC

[jira] [Resolved] (SLING-6798) Only start the SlingServletResolver once all service user mappings are there

     [ https://issues.apache.org/jira/browse/SLING-6798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konrad Windszus resolved SLING-6798.
------------------------------------
       Resolution: Fixed
    Fix Version/s: Servlets Resolver 2.4.12

Fixed in [r1792750|https://svn.apache.org/r1792750].

> Only start the SlingServletResolver once all service user mappings are there
> ----------------------------------------------------------------------------
>
>                 Key: SLING-6798
>                 URL: https://issues.apache.org/jira/browse/SLING-6798
>             Project: Sling
>          Issue Type: Improvement
>          Components: Servlets
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>             Fix For: Servlets Resolver 2.4.12
>
>
> Currently the {{SlingServletResolver#activate()}} will throw an exception if there is not yet the user mapping configured. Therefore the mechanism from SLING-4312 should be leveraged to defer the service start until that mapping is available.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)