[jira] [Commented] (SLING-7581) Using data-sly-use with two classes with same name will generate uncompilable code

["Radu Cotescu (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-7581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16568183#comment-16568183 ] 

Radu Cotescu commented on SLING-7581:
-------------------------------------

Next week turned to be one month and a half later. Sorry for that, it slipped under the radar before my holiday. On it now.

> Using data-sly-use with two classes with same name will generate uncompilable code
> ----------------------------------------------------------------------------------
>
>                 Key: SLING-7581
>                 URL: https://issues.apache.org/jira/browse/SLING-7581
>             Project: Sling
>          Issue Type: Bug
>          Components: Scripting
>    Affects Versions: Scripting HTL Java Compiler 1.0.16
>            Reporter: Santiago García Pimentel
>            Assignee: Radu Cotescu
>            Priority: Major
>             Fix For: Scripting HTL Java Compiler 1.0.26-1.4.0
>
>
> If you have an HTL file with two data-sly-use with classes with the same name HTL will generate a java file which cannot be compiled.
> e.g.
> {code}
> data-sly-use.first="com.adobe.cq.wcm.core.components.models.Page"
> data-sly-use.second="com.client.project.Page"
> {code}
>  
> Will generate
> {code}
> import com.client.project.Page;
> import com.adobe.cq.wcm.core.components.models.Page;
>  ...
>  ...
>  _global_first= renderContext.call("use", Page.class.getName(), obj());
>  _global_second = renderContext.call("use", Page.class.getName(), obj());
> {code} 
> Causing a compilation error as Page is not fully qualified in the code and therefore an ambiguous reference (due to the two imports of same class names)
> This seems to have been introduced by SLING-7205 .



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)