My response is not directly related to your question, by the way... in
previous version of T5 it was possible to initiliaze the value of persistent
variables at declaration time. And this value was considered as the default
value. This feature was the cause of session conflicts, more precisely, i
think it was javassist that was the root cause, thus the ability to
initialize variable at declaration time has been forbidden.
Maybe plastic will change the deal, but i currently haven't had the time to
look into this promising project.
Christophe.
2011/4/12 Adam Zimowski <zimowsk...@gmail.com>
> Maybe I'm over-thinking here... I find a lot of times I have to do this:
>
> @Property
> private AddressUiBean address;
>
> @SetupRender
> void init() {
> if(address == null) address = new AddressUiBean();
> }
>
> What would be super nice, following the spirit of @SessionState, is this:
>
> @Property(create=true)
> private AddressUiBean address;
>
> I realize that @Property could be a non-bean in which case there is no
> guarantee for a no-arg constructor, perhaps that's why this isn't
> there, but maybe documentation could explicitly require it?
>
> Maybe I'm off base here...
>
> Adam
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
--
Regards,
Christophe Cordenier.
Committer on Apache Tapestry 5
Co-creator of wooki @wookicentral.com
