Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
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
Attachments
Issue Links
- is a clone of
-
SLING-5783 Add service property to identify the ServletContext registered by Sling
- Closed
- is blocked by
-
SLING-6168 ServletContext is registered with wrong name
- Closed