i don't have an exact explanation till i view your source code.
i'm glad it works, so maybe you can do some more research to see why the volatile makes the difference for the ticked/unticked issue of yours. your understanding of volatile is incorrect. in fact, with volatile="false" the For component serliazes your domain objects and sends them to the client as hidden fields. with volatile="true" the for component evaluates from your source list every time. you have to thus ensure that your source list is consistent for the render and rewind. you can see this difference by viewing the HTML source with and without the volatile to see the difference in the source. On 8/20/06, zqzuk <[EMAIL PROTECTED]> wrote:
hi, thanks so much! it works! could you please explain why is this? i read the link, it says "Determines whether to avoid creating hidden fields within a form. Using this parameter may make the form structure different during render and rewind, and cause exceptions as a result. Please use with caution. " by setting volatile=true i suppose it allows hidden fields in the form? i dont have a hidden component at all, so does FOR component creates such a component automatically? for what purpose? again thanks very much! -- View this message in context: http://www.nabble.com/hi%2C-is-it-possible-to-do-this-with-tapestry...-tf2126696.html#a5894560 Sent from the Tapestry - User forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Thanks, Karthik
