[
http://issues.apache.org/jira/browse/VELOCITY-277?page=comments#action_12360636
]
Randy Watler commented on VELOCITY-277:
---------------------------------------
Jetspeed2 also has this problem while using the tools VelocityViewServlet to
render portal content.
To get around the issue, we manage our own set of VelocityEngine instances and
use them to override/implement these methods:
org.apache.velocity.tools.view.servlet.VelocityViewServlet.getTemplate(java.lang.String)
org.apache.velocity.tools.view.servlet.VelocityViewServlet.getTemplate(java.lang.String,
java.lang.String)
We monitor file modifications dates of the macro files associated with the
VelocityEngine and allocate new instances when the modifification is detected.
Within the portal content templates, the following is used to load the macros:
#parse($decoration.getResource("decorator-macros.vm"))
We have already worked around this issue, but we would like to have this fixed
so that we can let Velocity manage this!
> macros in #parsed files are not refreshed when including page is refreshed
> --------------------------------------------------------------------------
>
> Key: VELOCITY-277
> URL: http://issues.apache.org/jira/browse/VELOCITY-277
> Project: Velocity
> Type: Bug
> Components: Build
> Versions: 1.4
> Environment: Operating System: other
> Platform: Other
> Reporter: Tim White
> Priority: Critical
> Fix For: 1.5
>
> If a template #parses a file containing velocimacros, changes those macros do
> not make it into the including template. This is true whether the file is
> included via the library property or via #parse.
> Although there is the velocimacro.library.autoreload property, it is "not for
> use in production" according to the documentation - and cannot be used with
> template caching.
> Also, often, macros included via #parse do not pick up their macros the first
> time they are compiiled. And with template caching they are only ever called
> once, this leads to situations where changes in templates that include macros
> and are cached do not function in production.
--
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]
