After you de-reference a value from a list, you end up knowing only type java.lang.Object which contains no accessible properties. Generics is a fiction enforced at compile time, but there is some runtime information that Tapestry might be able to leverage to allow this kind of reference.
On 3/22/07, Bogdan Calmac <[EMAIL PROTECTED]> wrote:
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]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
