I believe self-calls are handled; you can use @Cached on non-public
methods as well.
On Thu, Mar 26, 2009 at 12:54 PM, Geoffrey Wiseman
wrote:
> Does tapestry manipulate the page class enough that @Cached affects
> self-calls?
>
> That is, if I wrote this code:
>
> @Cached
> List getSomeExpensive
Does tapestry manipulate the page class enough that @Cached affects
self-calls?
That is, if I wrote this code:
@Cached
List getSomeExpensiveResult() { ... }
String getSummary() {
if( getSomeExpensiveResult().isEmpty() )
return "nothing";
else {
String summary = "";
for( Object item
