Hello Jeffrey, Thanks for your reply. :)
>And you say if you use any render phase the value is not persisted. >Persists to where? I mean to say that when I don't use any render phase or event it [the select component] persists the value after page is been called on action.[In this case I used constructor to fetch database values] >Do you just mean, in the action request, the value is correctly set to a variable in your page? No, the selected option value persists in action request but it doesn't get set to select component. Means select component shows first default option after action performed though there is a persisted value from previous request in variable. I can't set this value to select component again. I tried everything in my knowledge to do that. Did you got the problem now? jeffrey ai wrote: > > Hi Ritesh, > > I am not quite clear of your problem. > >> When I don't use any render phase or event it persists the value > > And you say if you use any render phase the value is not persisted. > Persists to where? Do you just mean, in the action request, the value is > correctly set to a variable in your page? > > Jeffrey Ai > -- View this message in context: http://www.nabble.com/T5-persisting-select-component-selection-after-form-submission-tf4843731.html#a13871490 Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
