Hi Geoff,
yes, I read those threads and I modeled my CRUD page using the
suggestions listed on your Mk VI page. Thank you.
As I was trying to explain to Jonathan Barker in my previous mail (ah,
my poor english ;^) , my CRUD page already used @Persist("flash") to
store the entity to modify.
The problem was I was trying to do "too much things" in a single page
thinking that the flash persistence could do the job (well, it works
fine, but I had some conditions that were not compatible with that kind
of persistence strategy).
Anyway, I'm going to study Tapestry JumpStart to better understand T5
behaviour and page lifecycle.
Regards,
Luca
Geoff Callender wrote:
Hi Luka,
It's probably best to ditch the mental model of "rewind" and "render" in
T5. I think what you're after is covered in this thread on "Edit page
best practice":
http://thread.gmane.org/gmane.comp.java.tapestry.user/56176/focus=57580
It's discussed and demonstrated in Tapestry JumpStart:
http://files.doublenegative.com.au/jumpstart/
Don't forget that action links throw a curved ball at your page: they
cause a sequence of Action-Redirect-Render, so your onActivate() will
probably get called twice before the page is displayed - once by the
previous page's action handler method and then by the T5 framework after
the redirect. The best practice above takes this into account. There's
a JIRA issue that flowed from it too:
https://issues.apache.org/jira/browse/TAPESTRY-2138
Cheers,
Geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
