Hi,
You could get/set the bean instance in a page field before rendering the
page. Then you would only perform the expensive get once.
Or you could use @Cached for the bean getter.
--
Chris
On Sun, Apr 28, 2013 at 11:27 AM, John <j...@quivinco.com> wrote:
> I'd like to be able to assign a bean to page scope so that the property
> getter is not repeatedly invoked. I'm guessing this might not be compatible
> with Tapestry practice, but anyway.
>
> I suppose I could assign a member as a persistent property and then switch
> it as required, but I'd like to do something more like this:
>
> <t:useBean id="bean" t:source="prop:beanGetter"/>
>
> ${bean.total}
>
> ${bean.messages}
>
> Sometimes I prefer to provide properties with a get method that I don't
> want repeatedly invoked because of the cost.
>
> John
