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

Posted to dev@sling.apache.org by "Oliver Lietz (JIRA)" <ji...@apache.org> on 2016/07/09 19:16:10 UTC

[jira] [Updated] (SLING-5784) Use service property to identify the ServletContext registered by Sling

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

Oliver Lietz updated SLING-5784:
--------------------------------
    Fix Version/s:     (was: Servlets Resolver 2.4.4)
                   Servlets Resolver 2.4.6

> Use service property to identify the ServletContext registered by Sling
> -----------------------------------------------------------------------
>
>                 Key: SLING-5784
>                 URL: https://issues.apache.org/jira/browse/SLING-5784
>             Project: Sling
>          Issue Type: Improvement
>          Components: Scripting, Servlets
>            Reporter: Carsten Ziegeler
>             Fix For: Scripting JSP 2.1.10, Scripting Java 2.0.16, Servlets Resolver 2.4.6
>
>
> The Sling Engine currently registers a ServletContext service, however without any properties to identify this service. On the other hand, the scripting bundles and the resolver simply take the first service they get. There is no guarantee that this is really the context registered by Sling



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)