Macro caching and other caching

Bradley Wagner <[email protected]>
Newsgroups gmane.comp.jakarta.velocity.user
Message-ID <CAEbivYXKOS9aHAtgcBrd=1JmhiQLzLPtJYktTrfQHEKWN68rFw@mail.gmail.com>
Hi,

We recently made some changes to our software to use just a single
VelocityEngine as per recommendations on this group.

We ran into an issue where macros were all of the sudden being shared
across template renders because we had not
specified: velocimacro.permissions.allow.inline.local.scope = true.
However, we also had not ever turned on caching in our props file
with: class.resource.loader.cache = true.

Does this mean that macros are cached separately from whatever is being
cached in the class.resource.loader.cache cache? Is there any way to
control that caching or is just using this property the
way: velocimacro.permissions.allow.inline.local.scope = true

One side effect of our recent changes is that the app seems to have an
increased mem footprint. We're not *sure* it can be attributed to velocity
but I was trying to see what kinds of things Velocity could be hanging on
to and how much memory they might be taking up.

Thanks!
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.