[
https://issues.apache.org/jira/browse/SLING-5597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu resolved SLING-5597.
---------------------------------
Resolution: Fixed
Fixed in
[r1734715|https://svn.apache.org/viewvc?view=revision&revision=1734715].
> Sightly generated Java classes for component scripts might not run correctly
> if the Sightly engine is updated on the instance
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: SLING-5597
> URL: https://issues.apache.org/jira/browse/SLING-5597
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Affects Versions: Scripting Sightly Engine 1.0.4
> Reporter: Radu Cotescu
> Assignee: Radu Cotescu
> Priority: Blocker
> Fix For: Scripting Sightly Engine 1.0.18
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
