You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/12/28 14:38:49 UTC
[jira] [Resolved] (SLING-5404) Recursive taglibs overwrite
generated java/class file
[ https://issues.apache.org/jira/browse/SLING-5404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-5404.
-------------------------------------
Resolution: Fixed
Fixed in rev 1721916 by using different class names for the recursive/inner tag libs. These class files are not removed after the generation as they are already loaded by the class loader which would mark the class loader as dirty
> Recursive taglibs overwrite generated java/class file
> -----------------------------------------------------
>
> Key: SLING-5404
> URL: https://issues.apache.org/jira/browse/SLING-5404
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Affects Versions: Scripting JSP 2.1.6
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Scripting JSP 2.1.8
>
>
> When a taglib is using itself recursively, the recursive call results in a stup java tag file being generated overwriting/clashing with the outer java file. The class is loaded as well, resulting in a stup class being loaded through the class loader first.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)