[TAP5-79] Improve Tapestry's property expression language to include OGNL-like features

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0.15
• Fix Version/s: 5.1.0.0
• Assignee: Howard Lewis Ship
• Reporter: Dan Adams
• Created: 02/Jul/07 14:11
• Updated: 31/Jan/09 22:50
• Resolved: 31/Jan/09 22:50

Description

While I really the use of prop and it's typesafeness, I still find myself frequently in need of more complicated expressions enough that I would be willing to pay the speed penalty of reflection in order to not have to define a public getter for it. In some situations, you can't actually make an equivilent getter. For instance, in integrations tests I've had more than one situation where I wanted to call a setter with a specific value from the template. With OGNL this is easy but with prop it's impossible. I would very much like to see prop remain the default binding but have OGNL available when it's needed. I think not having it would be a severe limitation of T5.

Issue Links

• incorporates: TAP5-62 Range of integers parameter semantics should resolve symbols