Decorator Velocity Template/Macro Cache Permanent
-------------------------------------------------
Key: JS2-331
URL: http://issues.apache.org/jira/browse/JS2-331
Project: Jetspeed 2
Type: Bug
Components: Layout
Versions: 2.0-M4
Reporter: Randy Watler
Assigned to: Randy Watler
Priority: Minor
Fix For: 2.0-M4
Limitiation of Velocity webapp loader that does not support template/macro
modification detection causes decorator templates/macros to be cached
permanently. A Tomcat restart or disabling of cache is required during
decorator development to support hotdeploy.
This is to be fixed by switching back to a file based loader and configuring
the base path using spring system property injection already in place for
applicationRoot. When complete, decorator and template modification should be
picked up every 10 seconds. The current Velocity Engine management logic may be
changed to rely on this functionality to detect macro modifications if it can
be made reliable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
