sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Santiago García Pimentel (JIRA) <j...@apache.org>
Subject [jira] [Created] (SLING-7755) JavaUseProvider might attempt to instantiate interfaces
Date Wed, 27 Jun 2018 11:26:00 GMT
Santiago García Pimentel created SLING-7755:
-----------------------------------------------

             Summary: JavaUseProvider might attempt to instantiate interfaces
                 Key: SLING-7755
                 URL: https://issues.apache.org/jira/browse/SLING-7755
             Project: Sling
          Issue Type: Bug
    Affects Versions: Scripting Sightly Engine 1.0.18
            Reporter: Santiago García Pimentel


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)

Mime
View raw message