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 2015/05/21 16:04:00 UTC
[jira] [Commented] (SLING-4734) Sightly should try to instanciate
Sling Models first via SlingHttpServletRequest then via Resource and not
the other way round
[ https://issues.apache.org/jira/browse/SLING-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554313#comment-14554313 ]
Stefan Seifert commented on SLING-4734:
---------------------------------------
+1
> Sightly should try to instanciate Sling Models first via SlingHttpServletRequest then via Resource and not the other way round
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: SLING-4734
> URL: https://issues.apache.org/jira/browse/SLING-4734
> Project: Sling
> Issue Type: Improvement
> Components: Scripting
> Affects Versions: Scripting Sightly Engine 1.0.4, Scripting Sightly Models Use Provider 1.0.0
> Reporter: Konrad Windszus
>
> Currently the {{JavaUseProvider}} first tries to instantiate Sling Models via the {{Resource}} then via the {{SlingHttpServletRequest}}. I would argue that the inverse order makes more sense, because more injections are supported via the {{SlingHttpServletRequest}} for Sling Models.
> This would only matter though, where the same class would be adaptable from both {{Resource}} and {{SlingHttpServletRequest}}. In that case though the instantiation via the {{SlingHttpServletRequest}} would support more injections (e.g. the SlingObjectInjector supports much more with the {{SlingHttpServletRequest}}, compare with SLING-4083)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)