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. On Wed, 2011-04-13 at 04:56 -0700, robnangle wrote: > Richard Hill-7 wrote: > > > > are "add" and "edit" page classes? > > > > > > They are yes.. All values are @Persist, @Property > > So is the only way to get the default value up by setting all players as > sso's? > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/T5-Select-wont-find-selected-value-in-edit-tp4300292p4300407.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 > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
