On Thu, 14 Aug 2014 12:25:40 -0300, squallmat . <squall...@gmail.com>
wrote:
Hi,
Hi!
My best practices for persisting fields is this: just do it when there's
no way of avoiding it.
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,
Any process using more than one render request and one action request
(form submission, event links, etc) will need some kind of persistence.
or a file selection, their values doesn't persist naturally,
I don't think HTML supports giving an <input type="file"> an initial value.
you have to use @Persist (and even the FLASH one doesn't work).
You missed the point here. The problem isn't simple string vs list. It's
one request vs multiple ones.
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 don't like AjaxFormLoop, to be honest, so I don't use it.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
