[
https://issues.apache.org/jira/browse/SLING-5783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-5783:
------------------------------------
Description: 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
(was: The Sling Engine currently registers a HttpContext 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)
> Add service property to identify the ServletContext registered by Sling
> -----------------------------------------------------------------------
>
> Key: SLING-5783
> URL: https://issues.apache.org/jira/browse/SLING-5783
> Project: Sling
> Issue Type: Improvement
> Components: Engine, Scripting
> Reporter: Carsten Ziegeler
> Fix For: Servlets Resolver 2.4.4, Scripting JSP 2.1.10, Engine
> 2.4.8, Scripting Java 2.0.16
>
>
> 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)
