Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
Servlets Resolver 2.0.4
-
None
-
None
Description
The SlingServletResolver fails to activate if a servlet service is to be used, which cannot be acquired. This may be the case if the respective service is registered as a ServiceFactory and fails to instantiate when retrieving it. This is for example the case for the recently added Deployment Admin console page of the Felix Web Console.
In addition, the resolver acquires the service instance to early: It should first check whether the service is actually destined at Sling. Only if this is the case, should the servlet service be acquired – better in a try-catch statement to prevent startup failure.