[ https://issues.apache.org/jira/browse/SLING-9715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radu Cotescu resolved SLING-9715. --------------------------------- Resolution: Fixed Fixed in: * [commit 960d9cd|https://github.com/apache/sling-org-apache-sling-scripting-sightly/commit/960d9cd] * [commit f266d23|https://github.com/apache/sling-org-apache-sling-scripting-sightly-testing/commit/f266d23] * [commit 20f1108|https://github.com/apache/sling-org-apache-sling-scripting-sightly-testing-content/commit/20f1108] > 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 > Assignee: Radu Cotescu > 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)