You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Justin Edelson (Jira)" <ji...@apache.org> on 2020/10/05 11:31:00 UTC
[jira] [Updated] (SLING-9674) Allow SlingHttpServletRequest based
adaptations for ChildResourceInjector
[ https://issues.apache.org/jira/browse/SLING-9674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Edelson updated SLING-9674:
----------------------------------
Fix Version/s: (was: Sling Models Impl 1.4.14)
Sling Models Impl 1.4.16
Sling Models Impl 1.4.16
> Allow SlingHttpServletRequest based adaptations for ChildResourceInjector
> -------------------------------------------------------------------------
>
> Key: SLING-9674
> URL: https://issues.apache.org/jira/browse/SLING-9674
> Project: Sling
> Issue Type: Improvement
> Components: Sling Models
> Reporter: Konrad Windszus
> Priority: Major
> Fix For: Sling Models Impl 1.4.16
>
>
> The {{ChildResourceInjector}} always returns one/multiple Resource objects which makes it impossible to use those return values with another Sling Model requiring the adaptable {{SlingHttpServletRequest}}.
> A solution from ACS Commons introduced https://adobe-consulting-services.github.io/acs-aem-commons/features/sling-model-injectors/child-resource-from-request/index.html in https://github.com/Adobe-Consulting-Services/acs-aem-commons/pull/1920. There should be a solution built into Sling which allows for easier Sling Model aggregation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)