Yes, you are right. But loops are usually inside of components and pages contain those components....but all methods in the page itself could be @Cache methods in my opinion if you do a "component based approach" and always package logical widgets into a component.
-------- Original-Nachricht -------- > Datum: Tue, 25 Mar 2008 13:33:19 +0100 > Von: Francois Armand <[EMAIL PROTECTED]> > An: Tapestry users <users@tapestry.apache.org> > Betreff: Re: @Cached and caching in general > Tobias Marx wrote: > > Wouldn't it be useful to make the @Cache annotation the default > annotation > > for all methods? > > > > I can not imagine a case where it would make sense that during the > rendering of a page returns different results... > > > Just an example : you are in a loop (or grid or a beaneditor any other > looping component) and you get the current value of an object, for the > current iteration. > > -- > Francois Armand > Etudes & Développements J2EE > Groupe Linagora - http://www.linagora.com > Tél.: +33 (0)1 58 18 68 28 > ----------- > InterLDAP - http://interldap.org > FederID - http://www.federid.org/ > Open Source identities management and federation > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
