All bindings are set during page load. Connected properties are set inside prepareForRender(), which is invoked just before renderComponent().
Connected properties are only valid while the component itself is rendering; component values are cleared immediately after renderComponent() by cleanupAfterRender(). In the case where two components must coordinate and one doesn't wrap around the other, you must use "custom" parameters (i.e., dereference the value through the binding object). ----- Original Message ----- From: "Neil Clayton" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, October 12, 2002 11:56 AM Subject: Re: [Tapestry-developer] Order of parameter binding -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 So it is guaranteed that all parameters will be bound (both to the component, and to those that the component declares in it's specification to other components) BEFORE either a rewind or render takes place (via prepareForRender()) ? Neil On Saturday 12 Oct 2002 1:55 pm, Howard M. Lewis Ship wrote: > I wouldn't count on the order that parameters are bound. It is not > defined. > > Parameters, whether represented by IBinding (for "custom" direction > parameters) or an object value (for "in" and "form") should be simple. > > Your logic for dealing with the bindings and values should be in the method > prepareForRender() or renderComponent(). > > ----- Original Message ----- > From: "Neil Clayton" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Saturday, October 12, 2002 8:37 AM > Subject: Re: [Tapestry-developer] Order of parameter binding > > > Never mind:-) > > I think I have the answer. > Is it correct to say that the order of binding is driven completely by the > order in which parameters are defined on the template? > > On Saturday 12 Oct 2002 12:58 pm, Neil Clayton wrote: > > What controls the order in which parameters are bound to a form? > > > > I've found myself in the situation whereby I need binding to occur in a > > certain order, so that previous information (stored as hidden fields) is > > availble to some other component when it is bound. > > > > That is, the act of binding a parameter to one of the components causes > > it to perform some work (lookup from DB and creation of a > > PropertySelectionModel to match). The value for the lookup has to exist > > beforehand, else it will fail. > > > > Anyway to ensure some parameters are bound before others? > > Or am I going about this in a non-Tapestry way? > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer - -- Regards, Neil Clayton (PS: If you see strange text you don't understand underneath my email, don't worry - it's just my PGP signature) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9qEYuLXcfQF3yrNoRAsI/AJ4w4ue3mfpL20DQVYNhnMBnsV/0GACfVGl1 hPS2gFnWbnVE4Y6i/1E960o= =NKKQ -----END PGP SIGNATURE----- ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
