You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2009/04/07 22:55:15 UTC
[jira] Created: (TAP5-632) Property names (in property expressions)
should be able to read or update public variables
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.0.18, 5.1.0.3
Reporter: 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.
[jira] Updated: (TAP5-632) Property names (in property expressions)
should be able to read or update public variables
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-632:
--------------------------------------
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.
> 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.
[jira] Closed: (TAP5-632) Property names (in property expressions)
should be able to read or update public variables
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-632.
-------------------------------------
Resolution: Fixed
Fix Version/s: 5.2.0
> 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
> Fix For: 5.2.0
>
>
> 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.
[jira] Assigned: (TAP5-632) Property names (in property
expressions) should be able to read or update public variables
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Closed: (TAP5-632) Property names (in property expressions)
should be able to read or update public variables
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-632.
-------------------------------------
Resolution: Fixed
Fix Version/s: 5.2.0
> 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
> Fix For: 5.2.0
>
>
> 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.
[jira] Updated: (TAP5-632) Property names (in property expressions)
should be able to read or update public variables
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-632:
--------------------------------------
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.
> 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.
[jira] Assigned: (TAP5-632) Property names (in property
expressions) should be able to read or update public variables
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ 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.