Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A2DFB200C4B for ; Mon, 20 Mar 2017 23:14:46 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id A1886160B71; Mon, 20 Mar 2017 22:14:46 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E7619160B76 for ; Mon, 20 Mar 2017 23:14:45 +0100 (CET) Received: (qmail 60711 invoked by uid 500); 20 Mar 2017 22:14:45 -0000 Mailing-List: contact dev-help@sling.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sling.apache.org Delivered-To: mailing list dev@sling.apache.org Received: (qmail 60700 invoked by uid 99); 20 Mar 2017 22:14:45 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Mar 2017 22:14:45 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 93B781814DF for ; Mon, 20 Mar 2017 22:14:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.651 X-Spam-Level: X-Spam-Status: No, score=0.651 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id lA_Y4Puf3dUb for ; Mon, 20 Mar 2017 22:14:43 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 2BFFD5FE47 for ; Mon, 20 Mar 2017 22:14:43 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 61DF0E086E for ; Mon, 20 Mar 2017 22:14:42 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id CCCEA254D9 for ; Mon, 20 Mar 2017 22:14:41 +0000 (UTC) Date: Mon, 20 Mar 2017 22:14:41 +0000 (UTC) From: "Oliver Lietz (JIRA)" To: dev@sling.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Closed] (SLING-5980) Duplicate Script Cache Clearing Functionality MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 20 Mar 2017 22:14:46 -0000 [ https://issues.apache.org/jira/browse/SLING-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz closed SLING-5980. ------------------------------- > Duplicate Script Cache Clearing Functionality > --------------------------------------------- > > Key: SLING-5980 > URL: https://issues.apache.org/jira/browse/SLING-5980 > Project: Sling > Issue Type: Bug > Components: Commons, Scripting > Affects Versions: Scripting JSP 2.1.8, Commons ClassLoader 1.3.8, File System ClassLoader 1.0.2 > Reporter: Dan Klco > Assignee: Dan Klco > Fix For: Scripting JSP 2.3.0, Commons ClassLoader 1.4.0, File System ClassLoader 1.0.6 > > > Currently, there are two ways to clear the scripting classloader cache, one in the [JSP Scripting Console](https://svn.apache.org/repos/asf/sling/trunk/bundles/scripting/jsp/src/main/java/org/apache/sling/scripting/jsp/JspScriptEngineFactory.java) (http://localhost:8080/system/console/slingjsp) and on in the [File System ClassLoader Console](https://svn.apache.org/repos/asf/sling/trunk/bundles/commons/fsclassloader/src/main/java/org/apache/sling/commons/fsclassloader/impl/FSClassLoaderWebConsole.java) (http://localhost:8080/system/console/fsclassloader) > Unfortunately these two consoles perform slightly differently: > * JSP Scripting Console - only clears out the JSPs and also destroys the JSP Runtime Context > * 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 (v6.3.15#6346)