You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (Jira)" <ji...@apache.org> on 2019/11/04 10:05:00 UTC
[jira] [Closed] (SLING-8804) Mock SlingHttpServletRequest should
follow same caching as SlingHttpServletRequest
[ https://issues.apache.org/jira/browse/SLING-8804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seifert closed SLING-8804.
---------------------------------
> Mock SlingHttpServletRequest should follow same caching as SlingHttpServletRequest
> ----------------------------------------------------------------------------------
>
> Key: SLING-8804
> URL: https://issues.apache.org/jira/browse/SLING-8804
> Project: Sling
> Issue Type: Improvement
> Affects Versions: Servlet Helpers 1.2.0
> Reporter: David Gonzalez
> Assignee: Stefan Seifert
> Priority: Major
> Labels: test
> Fix For: Servlet Helpers 1.3.0
>
>
> The Sling Engine it is one of the few places which does not extend SlingAdaptable and thus does not cache the results. however, the mock implementation of SlingHttpServletRequest used in the mocks extends from SlingAdaptable an thus does the caching.
> It would be good to remove this caching from the mocked SlingHttpServletRequest to be as close to Sling as possible.
> Issue original reported via: [https://wcm-io.atlassian.net/browse/WTES-46]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)