[
https://issues.apache.org/jira/browse/SLING-9874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17228455#comment-17228455
]
Radu Cotescu edited comment on SLING-9874 at 11/9/20, 9:36 AM:
---------------------------------------------------------------
The adapter factory should not have been brought back - it was a mistake from
the times the code was donated by Adobe to Apache Sling, because the XSS API
has nothing to do with the Resource API.
was (Author: radu.cotescu):
These methods should not have been brought back. While the API use to have
them, it was a mistake from the times the code was donated by Adobe to Apache
Sling.
> Allow adapting SlingHttpServletRequest and ResourceResolver to XSSAPI
> ---------------------------------------------------------------------
>
> Key: SLING-9874
> URL: https://issues.apache.org/jira/browse/SLING-9874
> Project: Sling
> Issue Type: New Feature
> Components: XSS Protection API
> Affects Versions: XSS Protection API 2.2.6
> Reporter: Julian Sedding
> Assignee: Julian Sedding
> Priority: Minor
> Fix For: XSS Protection API 2.2.8
>
>
> Most commonly an {{XSSAPI}} instance is needed when rendering a response
> body. In such circumstances, it can be cumbersome to retrieve the {{XSSAPI}}
> service. To add some convenience, it would be nice to be able to adapt a
> {{SlingHttpServletRequest}} or a {{ResourceResolver}} to an {{XSSAPI}}
> instance.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
