[
https://issues.apache.org/jira/browse/SLING-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889852#action_12889852
]
Bertrand Delacretaz commented on SLING-1603:
--------------------------------------------
I did think about leaving the SlingServlet interface in the engine bundle, and
you're right that it's more "reversible" than putting it into Sling API:
What made me wonder is that all interfaces in the org.apache.sling.engine
package are @deprecated - IIUC that's a coincidence, not a willingness to have
the engine bundle export no interfaces.
I this case, I'll move the SlingServlet interface to org.apache.sling.engine, I
agree with your point.
> 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.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.
