[
https://issues.apache.org/jira/browse/SLING-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13985420#comment-13985420
]
Carsten Ziegeler commented on SLING-3486:
-----------------------------------------
[~mhaack] With SLING-3509 I've added a web console plugin which allows to
remove the compiled classes through the web console
I think this should be all we're doing in this respect and maybe add a sentence
to the metatype description of the configuration that changes only take effect
for newly compiled jsps.
I can imagine that there are situations where you don't want to remove the
compiled classes when you change the configuration.
The only other option I see is to calculate a hash of the configuration set,
persist it and compare it with the hash of the new configuraiton. If it's
different, remove the compiled classes.
> Configuration changes like jasper.trimSpaces only work after cleaning
> /var/classes and bundle restart
> -----------------------------------------------------------------------------------------------------
>
> Key: SLING-3486
> URL: https://issues.apache.org/jira/browse/SLING-3486
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Affects Versions: Scripting JSP 2.0.28
> Reporter: Markus Haack
> Labels: jsp, scripting
>
> Enabling jasper.trimSpaces of org.apache.sling.scripting.jsp has not
> immediately effect and therefor does not work.
> "Fix" is to clean /var/classes and restart the instance, then it works.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
