That sounds dodgey - if the list size is 100k something is sure to break under load.
Have a look at a ValueEncoder to translate between the client side and server side objects. It sounds similar to what one would do when they want to set an option for a select component. On 06/05/2012, at 1:05 PM, netdawg wrote: > Perhaps - persist the list (results) in your session? You could probably, > then, use Id in the grid > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/getting-the-object-in-a-row-from-a-grid-component-tp5687588p5688732.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
