On Fri, 04 Oct 2013 07:01:32 -0300, Lance Java <lance.j...@googlemail.com>
wrote:
On second thought, you are better to contribute a ValueEncoder to the
ValueEncoderSource.
In this case, the Loop doesn't contain anything to be edited, so adding a
ValueEncoder here wouldn't be the best choice, because it solves a problem
him didn't have. formState="none" is the best solution here, in my humble
opinion. If the loop had form fields, then a ValueEncoder would be needed.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
