Here's the scenario; we have a framework that allows us to reload the Velocity runtime so that we can tinker with caching etc at runtime. We normally run development with template caching turned off and deliver to the client with caching turned on.
There is a problem with inline macros (probably macro libraries too, not sure) whereby they will behave differently once they are compiled and cached then when they are interpreted at runtime. It is all to do with the re-assignment of parameter variables within the macro.
Here is a very simple example;
#set($FieldNames="ingredient." + $FieldNames.replaceAll(",",",ingredient."))
This works fine when the template is not cached - as soon as you turn on caching, the macro becomes unreliable.
My original prognosis was that we were upsetting the variable types by converting strings into lists but as you can see, that isn't the case in this example. The problem is solved by changing the assignment to;
#set($Names="ingredient." + $FieldNames.replaceAll(",",",ingredient."))
I can appreciate that maybe this type of "re-assignment" of parameters might be an issue, but the real problem is the inconsistency between the cached and non-cached behaviours.
- is related to
VELOCITY-681 [regression] Changes on the macro parameters are not persisted outside the macro call