[jira] [Resolved] (SLING-4692) Decouple Sightly from the JCR Compiler

["Radu Cotescu (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radu Cotescu resolved SLING-4692.
---------------------------------
    Resolution: Fixed

Fixed in [r1677848|https://svn.apache.org/r1677848].

> Decouple Sightly from the JCR Compiler
> --------------------------------------
>
>                 Key: SLING-4692
>                 URL: https://issues.apache.org/jira/browse/SLING-4692
>             Project: Sling
>          Issue Type: Improvement
>          Components: Scripting
>    Affects Versions: Scripting Sightly Engine 1.0.2
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>             Fix For: Scripting Sightly Engine 1.0.4
>
>
> The current implementation of the Sightly scripting engine depends on the JCR Compiler for generating Java classes from the Sightly script files. However, the JCR Compiler can be slow on some systems due to JCR's locking mechanisms.
> Since Sling also provides the {{org.apache.sling.commons.fsclassloader}}, which implements a faster filesystem-based {{ClassLoaderWriter}}, it would be better to use a more generic approach for generating Java classes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)