You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (Jira)" <ji...@apache.org> on 2020/09/01 08:45:00 UTC

[jira] [Updated] (SLING-9715) The JavaUseProvider does not properly handle the adaptable argument for Sling Model classes

     [ https://issues.apache.org/jira/browse/SLING-9715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radu Cotescu updated SLING-9715:
--------------------------------
    Summary: The JavaUseProvider does not properly handle the adaptable argument for Sling Model classes  (was: Sling models JavaUseProvider does not properly handle the adaptable argument for Sling Model classes)

> The JavaUseProvider does not properly handle the adaptable argument for Sling Model classes
> -------------------------------------------------------------------------------------------
>
>                 Key: SLING-9715
>                 URL: https://issues.apache.org/jira/browse/SLING-9715
>             Project: Sling
>          Issue Type: Bug
>          Components: Sling Models
>    Affects Versions: Scripting HTL Engine 1.4.0-1.4.0
>            Reporter: Paul Bjorkstrand
>            Priority: Major
>
> When Sling Models instantiation was added in SLING-9320 ([commit|https://github.com/apache/sling-org-apache-sling-scripting-sightly/commit/bcd46027e09182911c55bb244d42debb1bd367c7]), it did not treat the {{adaptable}} argument the same for all types of instantiations (Sling Models vs basic Sling Adaptable). This fixes that by rearranging the instantiation attempt order, which puts the argument provided adaptable through {{ModelFactory#createModel}} just like the request and resource would be.
> This is a subtle semantic change, and likely warrants a minor version update.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)