Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-79

Improve Tapestry's property expression language to include OGNL-like features

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.15
    • Fix Version/s: 5.1.0.0
    • Component/s: None
    • Labels:
      None

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                hlship Howard M. Lewis Ship
                Reporter:
                hagios17 Dan Adams
              • Votes:
                6 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: