On Mon, 12 Nov 2012 08:12:27 -0200, Lance Java <lance.j...@googlemail.com>
wrote:
Tapestry considers "prop:" bindings to a method invocation as read-only.
Actually, this isn't correct. prop is a read and write binding. When you
bind a property via the prop binding to a form field component, for
example, the component uses it to write the user-submitted value to the
property.
The solution for this is to bind your form field to a property, something
like ValueType getProperty() and setProperty(ValueType property), where
the methods read and write to the correct key-pair in the map. As always,
this is about moving logic from template to Java code, and that's why I
don't think we need map syntax in the prop binding. And, of course, who
disagrees with me can write your own binding.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
