-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9qBdvLXcfQF3yrNoRAnh/AJ9GeIEiQuh/kFbqjqZ3jSsIVCpdDwCfZ7nn 8lgDM2m572QslbLM64NHorY= =wc6g -----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
