[
https://issues.apache.org/jira/browse/SLING-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-652:
------------------------------------
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.
was:The SlingServlet
Summary: SlingServletResolver rfails to activate if a servlet service
reference cannot be acquired (was: SlingServletResolve rfails to activate if a
servlet service reference cannot be acquired)
> SlingServletResolver rfails to activate if a servlet service reference cannot
> be acquired
> -----------------------------------------------------------------------------------------
>
> Key: SLING-652
> URL: https://issues.apache.org/jira/browse/SLING-652
> Project: Sling
> Issue Type: Bug
> Affects Versions: Servlets Resolver 2.0.4
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: Servlets Resolver 2.0.6
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
