Richard Hill-7 wrote: > > It depends. If you have a static list of players then you can store your > select model in the session. If it's dynamic, you prob want to reload > from the db each time. > > To be honest I'm not sure that storing stuff like this as an SSO is > best-practice - it's more for user session state. And you want to limit > what you store in the session anyway as it contributes to your > application's overhead - small objects, primitive data types, not huge > lists of complex objects. These should come from the db. > > Although a more experienced Tapestry dev can confirm. >
Yes thats what I thought. What is strange is that it works for editing user details? But wont for editing the team. Thats why I thought it was to do with the way im adding the team(keeper...). As i change the string value when adding it to the database. prep.setString(3, work(keeper)); // the work method changes the string to say 'Steven Gerrard' team.setKeeper(keeper); // this is the whole value 'Liverpool - Steven Gerrard' Does this changes things? -- View this message in context: http://tapestry.1045711.n5.nabble.com/T5-Select-wont-find-selected-value-in-edit-tp4300292p4300442.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
