caching every method by default is definitely too error prone, and unexpected for most people.
On Tue, Mar 25, 2008 at 3:23 PM, Francois Armand <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > 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. > > > That means that if forbid the use of loop in page (for example, a loop > through all the high-level widgets of the page) , or at least that the > default behaviour for component's or for page's method is not the > same... In my opinion, it looks like to be very error prone, with things > that just don't work as expected. > > > > -- > 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]
