Tapestry 5
  1. Tapestry 5
  2. TAP5-632

Property names (in property expressions) should be able to read or update public variables

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.1.0.3, 5.0.18
    • Fix Version/s: 5.2.0
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      This leads to some ambiguities.

      Should we compare the property name to the field name after stripping some punctuation from the field name (i.e., "_", "$").

      Should we list public field names as well as property names (probably) if there is no match?

      Which has higher priority: field name or property (via accessor method)? I think property/accessor method.

      It would also be nice if the PropertyAccess service was made aware of public fields. That would be nice, to allow annotations on the field to be exposed uniformly.

        Activity

        Hide
        Howard M. Lewis Ship added a comment -

        So I think we look for the property name first and then, if not found, look for an exact (caseless) match on the public field name.

        Show
        Howard M. Lewis Ship added a comment - So I think we look for the property name first and then, if not found, look for an exact (caseless) match on the public field name.

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Howard M. Lewis Ship
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development