[prev in list] [next in list] [prev in thread] [next in thread]
List: tapestry-user
Subject: Re: [5.3.6] Saving loop-generated checkbox values between requests
From: Muhammad Gelbana <m.gelbana () gmail ! com>
Date: 2012-12-28 21:07:37
Message-ID: CAOjiMm63sW0HzTZJB-xwz7+Mmr8LCUqSvL9DX_LdQU3b=+bahQ () mail ! gmail ! com
[Download RAW message or body]
You are correct, I'll have to lookup the whole objects from the database
again and providing a value encoder sounds like the most seamless approach.
Thanks a lot for your help :)
On Fri, Dec 28, 2012 at 12:30 PM, Lance Java <lance.java@googlemail.com>wrote:
> The problem with ITERATION is that you need to lookup the values when the
> form is posted. If these came from a database there is a chance that the
> list has changed between rendering the form and posting the form.
>
> I suggest that you either pass an "encoder" parameter to the loop or you
> contribute to the ValueEncoderSource or TypeCoercer.
>
>
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/5-3-6-Saving-loop-generated-checkbox-values-between-requests-tp5719034p5719042.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic