You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2017/12/21 15:55:00 UTC
[jira] [Updated] (SLING-7321) ChildResourceViaProvider should be
able to deal with SlingHttpServletRequest
[ https://issues.apache.org/jira/browse/SLING-7321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated SLING-7321:
-----------------------------------
Affects Version/s: Sling Models Impl 1.4.6
> ChildResourceViaProvider should be able to deal with SlingHttpServletRequest
> ----------------------------------------------------------------------------
>
> Key: SLING-7321
> URL: https://issues.apache.org/jira/browse/SLING-7321
> Project: Sling
> Issue Type: Improvement
> Affects Versions: Sling Models Impl 1.4.6
> Reporter: Santiago GarcĂa Pimentel
> Priority: Minor
>
> The ForcedResourceType and ResourceSuperType are able to deal with Sling requests by creating a wrapper request that returns a wrapped Request.
> Still, the ChildResourceViaProvider does not offer such possibility. I think that for sake of consistency it should.
> I propose that if the adaptable is a SlingHttpServletRequest the ChildResourceViaProvider should create a request wrapper that returns the child as given in 'value'
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)