Hi Howard,

Is there any plan to support List and Map access in the prop: binding
for the final release of Tapestry 5? This would be nice and save a lot
of boilerplate code in the page classes, because lists an maps appear
quite frequently in the data model for a page. I'm thinking of
something like:

list: "questions[5].text"
map: "persons[jim].height" or even "persons.jim.height" if it is
possible to determine that persons is a Map when building the conduit.

Thanks,

Bogdan Calmac.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to