Wow! This is a really powerful component! Simple and powerful. I think it should be part of the Tapestry Framework.
On 11/15/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I also needed to cache parts of some pages, and so I created the cache > component of > TapFX ( tapfx.sf.net) which uses EhCache. I use this component a lot in my > own apps. > > However, the latest version for Tapestry 3 contains a bug (so instead get > v0.30) > and the update for Tapestry beta-13 has broken the Tapestry 4 version :) > > I have fixed both in the CVS so, expect a new release later today or tomorrow > morning! > > The idea is that you surround the content to be cached with a <span > jwcid="@Cache" key="report1"> > and then you define the report1 cache in the ehcache.xml configuration file. > The > cache component > also has public static methods for clearing or quering a cache. Finally take a > look at this FAQ: > http://tapfx.sourceforge.net/multiproject/tapfx-components/faq.html > > Hope this helps... > > > From Patrick Casey <[EMAIL PROTECTED]>: > > > > > > > I've got a couple of pages that change very rarely, but are > > rather expensive to generate (lots of conditional logic, db lookups, etc). > > I'd like to have tapestry generate them once, capture the output, and then > > either serve them as static pages, or at least serve them out of internal > > cache rather than going through the whole render cycle over again. > > > > > > > > What's the best way to go about doing this in a Tapestry > > friendly fashion? > > > > > > > > --- Pat > > > > > > > -- > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- /ted --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
