Replying to myself so quickly - not a good sign. ;-)
Anyway, I found another solution which is to let the event bubble up to the
parent component which needs to do the initialisation of the derived variable
(which is then provided as a source for the sub-component) and do the init in
the event
It makes some sense, but more details would help.
You said that the parameter is redundant: in what way is it redundant?
If the parameter is already passed to the component, then what's the
issue?
If the value is calculated, why can't the component calculate it?
Incidentally, if the component
and so null is passed as a
paremeter to Sub-component for action requests.
Does that make any more sense?
-Original Message-
From: robert zeigler [mailto:[EMAIL PROTECTED] On Behalf Of
Robert Zeigler
Sent: 27 May 2008 18:02
To: Tapestry users
Subject: Re: T5: Components initialising
for action requests.
Does that make any more sense?
-Original Message-
From: robert zeigler [mailto:[EMAIL PROTECTED] On Behalf Of
Robert Zeigler
Sent: 27 May 2008 18:02
To: Tapestry users
Subject: Re: T5: Components initialising derived variables for action
requests
for action requests.
Does that make any more sense?
-Original Message-
From: robert zeigler [mailto:[EMAIL PROTECTED] On Behalf Of
Robert Zeigler
Sent: 27 May 2008 18:02
To: Tapestry users
Subject: Re: T5: Components initialising derived variables for action
requests?
It makes some
Hi Andy,
There's nothing wrong with letting events bubble - this is a core part
of the Tapestry design and you pretty much have to do this when using,
for example, BeanEditForm.
-Filip
On 2008-05-27 18:48, Blower, Andy wrote:
Replying to myself so quickly - not a good sign. ;-)
Anyway, I
