This is a very informative article which explores situations when Velocity Templates within a cartridge when it becomes complex, which will require the help of Java. Velocity being a Java based template-engine which is becoming very popular as both build-time and run-time though it is not a full-featured language and can be quite complicated at time. So the question is how we can separate between the utilities so that they can be better utilized, used and re-used within other projects!blue lock
rss
This is a very informative
This is a very informative article which explores situations when Velocity Templates within a cartridge when it becomes complex, which will require the help of Java. Velocity being a Java based template-engine which is becoming very popular as both build-time and run-time though it is not a full-featured language and can be quite complicated at time. So the question is how we can separate between the utilities so that they can be better utilized, used and re-used within other projects!blue lock
thanks
V-Macros look fairly straightforward...actually looks easier than XSLT templates in some ways.
Guy; ya sort-of. There are
Guy; ya sort-of. There are macros. See the ref-guide:
http://velocity.apache.org/engine/devel/vtl-reference-guide.html