[
https://issues.apache.org/jira/browse/SLING-7755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16531641#comment-16531641
]
Radu Cotescu commented on SLING-7755:
-------------------------------------
[~santiagozky], the PR looks okay. Could you please provide some tests with it
too? You'd have to provide some Java code in [1] (the abstract class or
interface) and a test in [2].
[1] -
[https://github.com/apache/sling-org-apache-sling-scripting-sightly-testing-content]
[2] -
[https://github.com/apache/sling-org-apache-sling-scripting-sightly-testing]
> JavaUseProvider might attempt to instantiate interfaces
> -------------------------------------------------------
>
> Key: SLING-7755
> URL: https://issues.apache.org/jira/browse/SLING-7755
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Affects Versions: Scripting Sightly Engine 1.0.18
> Reporter: Santiago García Pimentel
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If you have a data-sly-use which receives a FQN of an interface or abstract
> class, the Java Use provider will not make any checks and will try to
> instantiate it anyway, causing a java.lang.NoSuchMethodException
> com.example.InterfaceName.<init>().
> This is a problem when your code base normally relies in an adapter factory
> to get implementation of an interface and the adaptTo returns null, causing
> sightly to try the java Use provider
> The Java Use provider should not attempt to instantiate blindly classes that
> it receives.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
