Yesterday, a couple or our engineers noticed that WebMacro is caching content which has been #include'd when *template* caching is turned on. While this could be useful in some situations (where static content really is static), ours does not happen to be one of them. ;) How does Velocity handle this? IMO, the caching of schmoo should be configurable through a separate property from template cache. -- Daniel Rall <[EMAIL PROTECTED]>
- Re: #include'd schmoo cache Daniel L. Rall
- Re: #include'd schmoo cache jon
- Re: #include'd schmoo cache Daniel L. Rall
- RE: #include'd schmoo cache Geir Magnusson Jr.
- Re: #include'd schmoo cache Daniel L. Rall
- Re: #include'd schmoo cache Gunnar R|nning
- Re: #include'd schmoo cache Geir Magnusson Jr.
