On Thu, 12 Aug 2010 18:56:44 -0300, Darren Williams <dar...@livetime.com>
wrote:
Thanks Thiago,
Hi!
we were trying to avoid rebuilding the beanModelSource on each render,
because it is backed by a large dataset.
I can't see the relation between a large data set and the BeanModel
creation. The same BeanModel instance is used to process all the objects
shown in the grid.
We have modified your suggestion as shown below. Is this the best
technique to persist this value like we have here, instead of constantly
creating?
If you're using Tapestry 5.1.0.5 or below, you can annotate the beanModel
field with @Retain and keep your getBeanModel() method as is. This way,
the BeanModel instance will be created. You could also keep the BeanModel
in a static field.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
