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 2018/03/05 12:25:00 UTC

[jira] [Closed] (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 ]

Stefan Seifert closed SLING-7321.
---------------------------------

> 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
>          Components: Extensions
>    Affects Versions: Sling Models Impl 1.4.6
>            Reporter: Santiago García Pimentel
>            Assignee: Justin Edelson
>            Priority: Minor
>             Fix For: Sling Models Impl 1.4.8
>
>
> 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
(v7.6.3#76005)