[
https://issues.apache.org/jira/browse/SLING-9874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17228446#comment-17228446
]
Konrad Windszus commented on SLING-9874:
----------------------------------------
[~jsedding] Look at SLING-6793 which deliberately removed the adapter
bq. At the same time we should remove the XSSAPIAdapterFactory as this is
abusing the adapter pattern. Getting an XSSAPI service in Java or JSP is easy
and there is no need to use the adapter pattern here.
So I think that reintroducing calls for some discussion on the mailing list...
> 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)
