[
https://issues.apache.org/jira/browse/SLING-9874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17226794#comment-17226794
]
Julian Sedding commented on SLING-9874:
---------------------------------------
[~sseifert] well, it sort of has a relation to the request in that it usually
gets used during request processing. It does not have a relation in terms of a
shared or derived state, however. The issue I am trying to resolve is one of
backwards compatibility in AEM, where earlier versions provided an adapter
factory for XSSAPI and later versions don't any longer. I could have simply
added the adapter factory to the project, but thought it may benefit other
users if it is available in Sling. Also, I don't think it does any harm,
because it only adds an import to a Sling API package and the implementation is
trivial.
> 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)
