I've used @Retain in several places.
It is a good idea :-) I hope you don't have plans to deprecate it.
-Original Message-
From: Howard Lewis Ship [mailto:hls...@gmail.com]
Sent: 24 June 2009 22:11
To: Tapestry users
Subject: Re: Difference between @Retain and static
any potential issues using static attributes instead?
> If the attribute can be calculated already at class-loading time, there is no
> issue. Except if calculating that attribute is time consuming or may fail.
> That would slow down or even block loading of the page class.
>
> Regar
cept if calculating that attribute is time consuming or may fail. That
would slow down or even block loading of the page class.
Regards, nillehammer
==
----- original Nachricht ----
Betreff: Difference between @Retain and static attributes?
Gesendet: Mi, 24. Jun 2009
Von: Kalle Korhonen
&g
Em Wed, 24 Jun 2009 18:11:28 -0300, Howard Lewis Ship
escreveu:
@Retain are per-instance which can be much different than a static.
@Retain looked like a good idea at the time, but I have never used it in
a project.
I use it to cache some class-specific values got from services in generi
@Retain are per-instance which can be much different than a static.
@Retain looked like a good idea at the time, but I have never used it in a
project.
Chances are, if you have some global state that needs to be shared between
users, neither @Retain or a static field is correct ... a shared servi
I was using @Retain for some fields that only needed to be initialized
once on a page. However, I see that they are reset after some time has
passed. How does the page pool work - are less used pages removed from
the pool only when other pages push them out or is the cache cleared
periodically? Are
