> > So - did I miss something or is there currently facility for > caching content from velocity based portlets?
The VelocityPortlet always goes to the template to merge the content, currently no caching > And if not, anyone interested in me add this as an optional (off by > default) feature to the existing VelocityPortlet? No problem with you adding this feature, perhaps create a subclass 'CacheableVelocityPortlet' Will you do the same for the JSP portlet ? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
