[SLING-5597] Sightly generated Java classes for component scripts might not run correctly if the Sightly engine is updated on the instance

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: Scripting Sightly Engine 1.0.4
• Fix Version/s: Scripting Sightly Engine 1.0.18
• Component/s: Scripting
• Assignee: Radu Cotescu
• Reporter: Radu Cotescu
• Created: 10/Mar/16 15:04
• Updated: 15/Jun/16 15:49
• Resolved: 13/Mar/16 17:41

Description

When upgrading the Sightly scripting engine on a Sling instance the engine will not recompile Java classes generated for component scripts unless the component scripts are modified or the Java classes are manually deleted from the org.apache.sling.commons.fsclassloader bundle's data folder.

This can lead to issues during those classes' execution since the engine's internals might change from one version to the other.

The Sightly scripting engine should generate its Java classes similar to the JSP scripting engine, by prefixing the classes' packages with a Sightly specific package name (e.g. org.apache.sling.scripting.sightly) and wipe this file-system backed folder upon startup if the classes were generated by a previous version of the engine.

Issue Links

• is duplicated by: SLING-5766 Sightly: Automatically clear all compiled scripts when the Sightly Engine Bundle was updated