[
https://issues.apache.org/jira/browse/SLING-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889521#action_12889521
]
Carsten Ziegeler commented on SLING-1603:
-----------------------------------------
I'm not sure what the best way is, but I think that adding the
AuthenticationInfo as a third parameter makes sense. If it is missing, the
SlingServlet should try to use the request (maybe the request is already
authenticated and can be used). If both is missing, throw an exception
> 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.
