sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Lietz (JIRA)" <>
Subject [jira] [Closed] (SLING-5980) Duplicate Script Cache Clearing Functionality
Date Mon, 20 Mar 2017 22:14:41 GMT


Oliver Lietz closed SLING-5980.

> Duplicate Script Cache Clearing Functionality
> ---------------------------------------------
>                 Key: SLING-5980
>                 URL:
>             Project: Sling
>          Issue Type: Bug
>          Components: Commons, Scripting
>    Affects Versions: Scripting JSP 2.1.8, Commons ClassLoader 1.3.8, File System ClassLoader
>            Reporter: Dan Klco
>            Assignee: Dan Klco
>             Fix For: Scripting JSP 2.3.0, Commons ClassLoader 1.4.0, File System ClassLoader
> Currently, there are two ways to clear the scripting classloader cache, one in the [JSP
Scripting Console](
(http://localhost:8080/system/console/slingjsp) and on in the [File System ClassLoader Console](
> Unfortunately these two consoles perform slightly differently:
>  * JSP Scripting Console - only clears out the JSPs and also destroys the JSP Runtime
>  * FS ClassLoader - Clears out all script compiled files including JSP, Sightly, etc
> I'm thinking about doing the following:
>  * Removing the JSP Scripting Console
>  * Adding a method into the ClassLoaderWriter for scripting providers to register and
unregister a listener for classloader cache flushes
> Consolidating the functionality will make the use of the console clearer. With the callback,
the JSP Script Engine (or any other scripting engine for that matter) could react to a cache
clear and perform the appropriate actions. 

This message was sent by Atlassian JIRA

View raw message