[ https://issues.apache.org/jira/browse/TAP5-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-79. ------------------------------------ Resolution: Fixed Fix Version/s: 5.1.0.0 I think the PE is quite good for what it is, and with the error checks I just added is quite sufficient. Further work on it will be covered in new issues. > Improve Tapestry's property expression language to include OGNL-like features > ----------------------------------------------------------------------------- > > Key: TAP5-79 > URL: https://issues.apache.org/jira/browse/TAP5-79 > Project: Tapestry 5 > Issue Type: Improvement > Affects Versions: 5.0.15 > Reporter: Dan Adams > Assignee: Howard M. Lewis Ship > Fix For: 5.1.0.0 > > > 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.