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

Konrad Windszus updated SLING-7581:
-----------------------------------
    Description: 
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 .

  was:
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.
 

The import com.adobe.cq.wcm.core.components.models.Page collides with another 
import statement.

This seems to have been introduced by SLING-7205 .


> 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
>    Affects Versions: Scripting HTL Compiler 1.0.16
>            Reporter: Santiago García Pimentel
>            Priority: Major
>
> 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)

Reply via email to