As no one replied to this I quess one should get rid of each and every
@Retain + change the associated initialization code to cope.
- Ville
9902468 wrote:
>
> Ok,
>
> the live 5.1 docs still point to the nightly docs @ formos, which is out
> of date, which I used when I upgraded. That clarifies some findings
> nicely.
>
> Is it ok to use @Retain with
>
> @Retain
> private BeanModel<User> _model;
> {
> _model = _beanModelSource.createDisplayModel(User.class,
> messages);
> _model.add("impersonate", null);
> }
>
> used by a grid, or should these be initialized in a getter also? I never
> change or touch that after initialization, only the grid.
>
> - Ville
>
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/T5-2-Upgrade-issues-tp2638940p2639472.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
