Uploaded image for project: '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
    • Status: Closed
    • Priority: 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.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: