> The thing is that "VALUES" serializes the "device" object using toString That's not entirely true. Tapestry uses a ValueEncoder to serialize / deserialize your values. If you don't provide an "encoder" parameter to the loop, it will use the ValueEncoderSource to find on which is ultimately backed by the TypeCoercer.
http://tapestry.apache.org/type-coercion.html -- View this message in context: http://tapestry.1045711.n5.nabble.com/5-3-6-Saving-loop-generated-checkbox-values-between-requests-tp5719034p5719041.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
