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 2018/08/14 15:44:00 UTC

[jira] [Assigned] (SLING-7755) JavaUseProvider might attempt to instantiate interfaces

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

Radu Cotescu reassigned SLING-7755:
-----------------------------------

    Assignee: Radu Cotescu

> 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
>            Assignee: Radu Cotescu
>            Priority: Major
>          Time Spent: 0.5h
>  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)