There's really 3 options: 1. Use the HttpSession 2. Save to the database and pass ids (perhaps a staging table or status= temp) 3. Store values on the client (hidden fields, data attributes, javascript variables, activation context, request parameters) On 14 Aug 2014 16:26, "squallmat ." <squall...@gmail.com> wrote:
> Hi, > > each time on a submit failed the field values associated to a simple string > persist without requiring @Persist annotation. But when you have any other > type of fields, for example a list from an ajaxformloop, or a file > selection, their values doesn't persist naturally, you have to use @Persist > (and even the FLASH one doesn't work). > That's really frustrating and cause you to have to manage some values in > session that force you to use really weird tricks to manage them, for > example when you come back later to a form you failed submit before and you > see a part of old-entered values or fiels of an ajaxformloop still there. > > I would like to know if there is a method, a best practice, to handle the > submitting persistence of values that are not link to simple String > Property. > > Thanks in advance. >
