[
https://issues.apache.org/jira/browse/SLING-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-1603:
-------------------------------------
Attachment: SLING-1603-fmeschbe.patch
Untested prototype implementation for this enhancement:
* Add a new Engine service interface (instead of SlingServlet)
* Split the SlingMainServlet into 5 classes
- SlingMainServlet is still the main servlet and registered as a DS
component and controls the other classes
- EngineImpl implements the Engine interface and contains the request
processing machinery
- SlingHttpContext is the OSGi HttpContext implementation used to
register the SlingMainServlet with the HttpService
- DefaultErrorHandler default implementation of the ErrorHandler
interface if no other ErrorHandler is registered
* Adapt all classes interacting with the former SlingMainServlet
* Add support for the new filter scopes as proposed by SLING-1213 (though
slightly different, to be discussed/fixed/changed).
> SlingServlet service
> --------------------
>
> Key: SLING-1603
> URL: https://issues.apache.org/jira/browse/SLING-1603
> Project: Sling
> Issue Type: Improvement
> Components: Engine
> Affects Versions: Engine 2.0.6
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
> Attachments: SLING-1603-fmeschbe.patch, SLING-1603.patch,
> SLING-1603.patch
>
>
> For SLING-550 I need to call the SlingMainServlet outside of the web
> container's request/response cycle.
> I'll attach a patch that introduces a new SlingServlet interface that
> SlingMainServlet implements.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
