[ https://issues.apache.org/jira/browse/SLING-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-1631. ------------------------------------- Resolution: Fixed Fixed in revision 982966 The taglib now uses the same logic for detecting taglib changes as the classloader uses for bundles Simplified and fixed the timestamp checking for taglibs. > Classloading problems when taglibs are used. > -------------------------------------------- > > Key: SLING-1631 > URL: https://issues.apache.org/jira/browse/SLING-1631 > Project: Sling > Issue Type: Bug > Components: Scripting > Affects Versions: Scripting JSP 2.0.8 > Reporter: Carsten Ziegeler > Assignee: Carsten Ziegeler > Fix For: Scripting JSP 2.0.10 > > > When taglibs are used together with jsp scripting there are several problems: > 1. The taglib cache does not detect changes to taglibs (contained in bundles) > like the general classloading mechanism through the dynamic classloader - > this can result in inconsistencies and classloading problems. > 2. The last modified check for taglibs does not work as expected. As soon as > tags are used, they are considered as changed which results in recompilation > of the jsp and of the tag where the second invalidates the classloader of the > jsp. This classloader is later on used and then a classloading exception is > thrown -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.