Thanks a lot for replying :) 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.
Based on your answer, I think providing a BeanModelImpl with an overridden PropertyConduitSource is the solution but frankly I don't know what I need to do exactly. I find the BeanModelImpl class complicated enough that I cannot comprehend all it's aspects. I'll start from the PropertyConduitSource source and may be I can accomplish something from there. Hopefully someone with practical past experience can share his knowledge :) On Tue, Feb 12, 2013 at 1:45 PM, Lance Java <lance.j...@googlemail.com>wrote: > Form fields have quite a complex relationship with their enclosing form, I > wouldn't suggest writing to the MarkupWriter. > > BeanEditor and BeanEditForm require a BeanModel. Instead of implementing > all > of the methods in BeanModel, you can instantiate a BeanModelImpl and pass a > custom PropertyConduitSource to it. > > Another option is to create a custom "map:" Binding/BindingFactory to get() > and set() values in the underlying maps. > eg <t:textfield value="map:myMap.someKey" /> > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/t5-3-6-Constructing-Forms-from-Maps-tp5719952p5719971.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 > >
