Re: [T5] Persistent fields may not be updated until after the page has finished loading

2009-04-22 Thread Felix Gonschorek
My suggestion: care for the initialization in the getters - this works best for me. Like this: public MyBusinessBean getBean() { if (this.bean == null) { this.bean = new MyBusinessBean(); } return this.bean; } works for pages and components... (onActivate!!) Felix Tobias Wehrum schrieb

Re: [T5] Persistent fields may not be updated until after the page has finished loading

2009-04-22 Thread Tobias Wehrum
Does that mean that for every persistent variable you have to write a if (field == null) field = new Anything(); in the SetupRender? Is there no easier way? Cheers, Tobias Marcel Sammut schrieb: I had the same problem when moving to 5.0.16. It was pretty simple for me, since what I was doing

Re: [T5] Persistent fields may not be updated until after the page has finished loading

2008-11-22 Thread Joel Halbert
in relation to this thread - and specifically in relation to using pageAttached() to initialise p[age fields - I raised the following possible bug the other day, https://issues.apache.org/jira/browse/TAP5-374 I was wondering if this was something anyone else had noticed/reproduced? On Fri, 2008

Re: [T5] Persistent fields may not be updated until after the page has finished loading

2008-11-21 Thread Eric Ma
ced in 5.0.16? It completely breaks our >> application. If the benefit is marginal, can we roll back to the >> original behavior? Or alternatively, what is a "better" practice under >> 5.0.16? >> >> Thanks, >> > > -- View this message in co

Re: [T5] Persistent fields may not be updated until after the page has finished loading

2008-11-20 Thread Olle Hallin
TED]> wrote: > > > > > > Why was this restriction introduced in 5.0.16? It completely breaks > our > > > application. If the benefit is marginal, can we roll back to the > > original > > > behavior? Or alternatively, what is a "better"

Re: [T5] Persistent fields may not be updated until after the page has finished loading

2008-11-20 Thread Marcelo Lotif
plication. If the benefit is marginal, can we roll back to the > original > > behavior? Or alternatively, what is a "better" practice under 5.0.16? > > > > Thanks, > > -- > > View this message in context: > http://www.nabble.com/-T5--Persistent-fields-may

Re: [T5] Persistent fields may not be updated until after the page has finished loading

2008-11-20 Thread Howard Lewis Ship
5.0.16? It completely breaks our > application. If the benefit is marginal, can we roll back to the original > behavior? Or alternatively, what is a "better" practice under 5.0.16? > > Thanks, > -- > View this message in context: > http://www.nabble.com/-T5--Persistent-fie

Re: [T5] Persistent fields may not be updated until after the page has finished loading

2008-11-20 Thread Marcel Sammut
this message in context: http://www.nabble.com/-T5--Persistent-fields-may-not-be-updated-until-after-the-page-has-finished-loading-tp20587662p20606832.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe

[T5] Persistent fields may not be updated until after the page has finished loading

2008-11-19 Thread Eric Ma
le.com/-T5--Persistent-fields-may-not-be-updated-until-after-the-page-has-finished-loading-tp20587662p20587662.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For