[
https://issues.apache.org/jira/browse/TAP5-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship reassigned TAP5-632:
-----------------------------------------
Assignee: Howard M. Lewis Ship
> Property names (in property expressions) should be able to read or update
> public variables
> ------------------------------------------------------------------------------------------
>
> Key: TAP5-632
> URL: https://issues.apache.org/jira/browse/TAP5-632
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.1.0.3, 5.0.18
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
