> Well I don't think providing a custom binding factory is the solution since the map keys will differ so the number of fields is unpredictable, it has to be dynamic.
Your "map:" binding can be as complex as you like. You can parse your own expressions: eg: <t:loop source="fieldNames" value="fieldName"> <t:textfield value="map:someProp.someMap(fieldName)" /> </t:loop> -- View this message in context: http://tapestry.1045711.n5.nabble.com/t5-3-6-Constructing-Forms-from-Maps-tp5719952p5720028.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
