yes, the VelocityViewTag does not currently do any caching of the template/tag body, so it must be reparsed for each render. Once Velocity Engine 1.6 is released, we will be able to properly use the new StringResourceLoader to easily provide that caching. until that time, VelocityViewTag will only perform well when it loads templates via a template="foo.vm" attribute, rather than having the template as its body.
On Mon, Aug 25, 2008 at 9:33 PM, bluejoe <[EMAIL PROTECTED]> wrote: > Dear developers, > > > > Sorry to bother you! > > > > I am a user of VelocityTools from China, and I want to rewrite some JSP pages > in Velocity template language. I have no idea whether to use > VelocityViewServlet or VelocityViewTag, then I choosed VelocityViewTag, > considering some JSP features, such as taglib or fragment, may be used. > > > > I use resin as J2EE container, when I use VelocityViewTag in the page, I > found the page displayed so slowly in web browser. Maybe the compilation of > Velocity template requires much time, I think. So, can you give me some > advice on how to improve the speed? > > > > Thank you very much and expect your early reply! > > > > Best Regards, > > > > bluejoe > > > 2008-8-26 > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
