my two cents then,
>
> Kind Regards,
> Peter
>
> - Original Message -
> From: "Geoff Callender"
> To: "Tapestry users"
> Sent: Thursday, 3 September, 2009 18:47:28 GMT +02:00 Athens, Beirut,
> Bucharest, Istanbul
> Subject: Re: [ANN] JumpStar
rut,
Bucharest, Istanbul
Subject: Re: [ANN] JumpStart 4.4 released
Kalle,
I'm really glad you asked this question because it got me thinking,
and I've realised I'm putting too much into onActivate(..). The
problem is that onActivate() is called regardless of whether the user
Kalle,
I'm really glad you asked this question because it got me thinking,
and I've realised I'm putting too much into onActivate(..). The
problem is that onActivate() is called regardless of whether the user
clicks on submit or an ActionLink. The database activity in
onActivate() is not
Thanks Geoff, no can't see any major issues. Agree on the
initialization of roles in setupRender() since they really are used
for rendering only. Heavy use of lazy getter-based initialization has
gotten me into trouble before, but I may revisit my coding best
practice. And that's really the only th
To set the scene: in the EditUser example, the user is displayed in a
form and the user roles are displayed below it in a grid with
ActionLinks for View, Edit, and Delete on each row.
The reason it is OK to get the user roles in setupRender() is because
they are not editable - all we need i
On Tue, Sep 1, 2009 at 11:30 PM, Geoff
Callender wrote:
> The key to it is this snippet: "if the stuff you are setting up is not
> needed for component event requests, consider putting it elsewhere". If I
> understand your example correctly, the object you are creating IS needed for
> a component e
Hi Kalle,
The key to it is this snippet: "if the stuff you are setting up is not
needed for component event requests, consider putting it elsewhere".
If I understand your example correctly, the object you are creating IS
needed for a component event request so DO put it in onActivate(...).
Hi Kalle,
It looks like you need to use onActivate() in your case. Could you
give us a sample code, so we can understand you better?
Regards, Sergey.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional
On Tue, Sep 1, 2009 at 9:50 PM, Geoff
Callender wrote:
> Good question. Yes, it does still seem to me to be best practice and no, I
> don't see it breaking the back button. Can you give an example?
Assuming you use something else than session or client persistence and
you initialize (create) an ob
Hi Kalle,
Good question. Yes, it does still seem to me to be best practice and
no, I don't see it breaking the back button. Can you give an example?
Regards,
Geoff
On 01/09/2009, at 8:37 AM, Kalle Korhonen wrote:
Hey Geoff,
I recall reading at some point that you had recommended not usin
Hey Geoff,
I recall reading at some point that you had recommended not using
onActivate() for all initialization purposes, and sure enough, I dug
it up and at
http://jumpstart.doublenegative.com.au:8080/jumpstart/examples/navigation/onactivateandonpassivate/3
you say "It can be tempting to put lo
Hi all,
JumpStart 4.4 is now available. It's a tidying up release: the
structure's a bit neater and it uses the latest OpenEJB, ie. 3.1.1.
Use it live:
http://jumpstart.doublenegative.com.au:8080/jumpstart/
or download it:
http://jumpstart.doublenegative.com.au
And if
12 matches
Mail list logo
