You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2010/09/07 10:48:32 UTC

[jira] Resolved: (SLING-1603) SlingServlet service

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

Felix Meschberger resolved SLING-1603.
--------------------------------------

    Resolution: Fixed

Applied a modified version of the patch in Rev. 993280.

The main change is the rename of the interface Engine to SlingRequestProcessor as proposed.

Other modifications are related to fixes of bugs contained in the original patch.

> 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: Felix Meschberger
>            Priority: Minor
>             Fix For: Engine 2.1.2
>
>         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.