You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Henning Petersen (JIRA)" <ji...@apache.org> on 2012/10/22 13:30:14 UTC
[jira] [Created] (TAP5-2016) Scala style properties unnecessarily
require a field with the same name
Henning Petersen created TAP5-2016:
--------------------------------------
Summary: Scala style properties unnecessarily require a field with the same name
Key: TAP5-2016
URL: https://issues.apache.org/jira/browse/TAP5-2016
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-ioc
Affects Versions: 5.2.5, 5.3.6
Reporter: Henning Petersen
The changes introduced with TAP5-1064 allow Scala-style properties to be used. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-2016) Scala style properties unnecessarily
require a field with the same name
Posted by "Henning Petersen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henning Petersen updated TAP5-2016:
-----------------------------------
Description:
The changes introduced with TAP5-1064 allow Scala-style properties to be used from components without the need for Java-style getters and setters. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
This works:
var value: String = _
<input ... t:value="value" />
This does not:
def value(): String = ...
def value_=(value: String) { ... }
<input ... t:value="value" />
A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
Possible workarounds include a dead field in the value class to satisfy the condition in PropertyAccessImpl, and adding Java-style getters and setters for the property.
was:
The changes introduced with TAP5-1064 allow Scala-style properties to be used from components without the need for Java-style getters and setters. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
This works:
{code:title=Scala class}
var value: String = _
{code}
{code:title=Component template}
<input ... t:value="value" />
{code}
This does not:
{code:title=Scala class}
def value(): String = ...
def value_=(value: String) { ... }
{code}
{code:title=Component template}
<input ... t:value="value" />
{code}
A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
Possible workarounds include a dead field in the value class to satisfy the condition in PropertyAccessImpl, and adding Java-style getters and setters for the property.
> Scala style properties unnecessarily require a field with the same name
> -----------------------------------------------------------------------
>
> Key: TAP5-2016
> URL: https://issues.apache.org/jira/browse/TAP5-2016
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.3.6, 5.2.5
> Reporter: Henning Petersen
> Labels: scala
> Attachments: TAP5-2016.patch
>
>
> The changes introduced with TAP5-1064 allow Scala-style properties to be used from components without the need for Java-style getters and setters. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
> This works:
> var value: String = _
> <input ... t:value="value" />
> This does not:
> def value(): String = ...
> def value_=(value: String) { ... }
> <input ... t:value="value" />
> A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
> Possible workarounds include a dead field in the value class to satisfy the condition in PropertyAccessImpl, and adding Java-style getters and setters for the property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-2016) Scala style properties unnecessarily
require a field with the same name
Posted by "Henning Petersen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henning Petersen updated TAP5-2016:
-----------------------------------
Attachment: TAP5-2016.patch
This patch (for the 5.3 branch) allows Scala properties without a corresponding field if there is both a setter and a getter, including a new test case that covers the issue.
It works only for properties with both a getter and a setter, because it is impossible to tell a getter of a read-only property from an ordinary method with a return value in Scala.
To use a read-only property, you'd still use the method call syntax, e.g. ${bean.value()}, while you can use the property syntax for read-write properties (where it matters), e.g. t:value="bean.value".
> Scala style properties unnecessarily require a field with the same name
> -----------------------------------------------------------------------
>
> Key: TAP5-2016
> URL: https://issues.apache.org/jira/browse/TAP5-2016
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.3.6, 5.2.5
> Reporter: Henning Petersen
> Labels: scala
> Attachments: TAP5-2016.patch
>
>
> The changes introduced with TAP5-1064 allow Scala-style properties to be used from components without the need for Java-style getters and setters. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
> A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-2016) Scala style properties unnecessarily
require a field with the same name
Posted by "Henning Petersen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henning Petersen updated TAP5-2016:
-----------------------------------
Description:
The changes introduced with TAP5-1064 allow Scala-style properties to be used from components without the need for Java-style getters and setters. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
was:
The changes introduced with TAP5-1064 allow Scala-style properties to be used. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
> Scala style properties unnecessarily require a field with the same name
> -----------------------------------------------------------------------
>
> Key: TAP5-2016
> URL: https://issues.apache.org/jira/browse/TAP5-2016
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.3.6, 5.2.5
> Reporter: Henning Petersen
> Labels: scala
>
> The changes introduced with TAP5-1064 allow Scala-style properties to be used from components without the need for Java-style getters and setters. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
> A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-2016) Scala style properties unnecessarily
require a field with the same name
Posted by "Henning Petersen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henning Petersen updated TAP5-2016:
-----------------------------------
Attachment: TAP5-2016.patch
This patch (for the 5.3 branch) allows Scala properties without a corresponding field if there is both a setter and a getter, including a new test case that covers the issue.
It works only for properties with both a getter and a setter, because it is impossible to tell a getter of a read-only property from an ordinary method with a return value in Scala.
To use a read-only property, you'd still use the method call syntax, e.g. ${bean.value()}, while you can use the property syntax for read-write properties (where it matters), e.g. t:value="bean.value".
> Scala style properties unnecessarily require a field with the same name
> -----------------------------------------------------------------------
>
> Key: TAP5-2016
> URL: https://issues.apache.org/jira/browse/TAP5-2016
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.3.6, 5.2.5
> Reporter: Henning Petersen
> Labels: scala
> Attachments: TAP5-2016.patch
>
>
> The changes introduced with TAP5-1064 allow Scala-style properties to be used from components without the need for Java-style getters and setters. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
> A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-2016) Scala style properties unnecessarily
require a field with the same name
Posted by "Henning Petersen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henning Petersen updated TAP5-2016:
-----------------------------------
Description:
The changes introduced with TAP5-1064 allow Scala-style properties to be used from components without the need for Java-style getters and setters. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
This works:
var value: String = _
<input ... t:value="value" />
This does not:
def value(): String = ...
def value_=(value: String) { ... }
<input ... t:value="value" />
A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
Possible workarounds include a dead field in the value class to satisfy the condition in PropertyAccessImpl, and adding Java-style getters and setters for the property.
was:
The changes introduced with TAP5-1064 allow Scala-style properties to be used from components without the need for Java-style getters and setters. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
This works:
var value: String = _
<input ... t:value="value" />
This does not:
def value(): String = ...
def value_=(value: String) { ... }
<input ... t:value="value" />
A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
Possible workarounds include a dead field in the value class to satisfy the condition in PropertyAccessImpl, and adding Java-style getters and setters for the property.
> Scala style properties unnecessarily require a field with the same name
> -----------------------------------------------------------------------
>
> Key: TAP5-2016
> URL: https://issues.apache.org/jira/browse/TAP5-2016
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.3.6, 5.2.5
> Reporter: Henning Petersen
> Labels: scala
> Attachments: TAP5-2016.patch
>
>
> The changes introduced with TAP5-1064 allow Scala-style properties to be used from components without the need for Java-style getters and setters. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
> This works:
> var value: String = _
> <input ... t:value="value" />
> This does not:
> def value(): String = ...
> def value_=(value: String) { ... }
> <input ... t:value="value" />
> A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
> Possible workarounds include a dead field in the value class to satisfy the condition in PropertyAccessImpl, and adding Java-style getters and setters for the property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-2016) Scala style properties unnecessarily
require a field with the same name
Posted by "Henning Petersen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henning Petersen updated TAP5-2016:
-----------------------------------
Description:
The changes introduced with TAP5-1064 allow Scala-style properties to be used from components without the need for Java-style getters and setters. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
This works:
var value: String = _
<input ... t:value="value" />
This does not:
def value(): String = ...
def value_=(value: String) { ... }
<input ... t:value="value" />
A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
Possible workarounds include a dead field in the value class to satisfy the condition in PropertyAccessImpl, and adding Java-style getters and setters for the property.
was:
The changes introduced with TAP5-1064 allow Scala-style properties to be used from components without the need for Java-style getters and setters. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
This works:
var value: String = _
<input ... t:value="value" />
This does not:
def value(): String = ...
def value_=(value: String) { ... }
<input ... t:value="value" />
A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
Possible workarounds include a dead field in the value class to satisfy the condition in PropertyAccessImpl, and adding Java-style getters and setters for the property.
> Scala style properties unnecessarily require a field with the same name
> -----------------------------------------------------------------------
>
> Key: TAP5-2016
> URL: https://issues.apache.org/jira/browse/TAP5-2016
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.3.6, 5.2.5
> Reporter: Henning Petersen
> Labels: scala
> Attachments: TAP5-2016.patch
>
>
> The changes introduced with TAP5-1064 allow Scala-style properties to be used from components without the need for Java-style getters and setters. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
> This works:
> var value: String = _
> <input ... t:value="value" />
> This does not:
> def value(): String = ...
> def value_=(value: String) { ... }
> <input ... t:value="value" />
> A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
> Possible workarounds include a dead field in the value class to satisfy the condition in PropertyAccessImpl, and adding Java-style getters and setters for the property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-2016) Scala style properties unnecessarily
require a field with the same name
Posted by "Henning Petersen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henning Petersen updated TAP5-2016:
-----------------------------------
Description:
The changes introduced with TAP5-1064 allow Scala-style properties to be used from components without the need for Java-style getters and setters. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
This works:
{code:title=Scala class}
var value: String = _
{code}
{code:title=Component template}
<input ... t:value="value" />
{code}
This does not:
{code:title=Scala class}
def value(): String = ...
def value_=(value: String) { ... }
{code}
{code:title=Component template}
<input ... t:value="value" />
{code}
A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
Possible workarounds include a dead field in the value class to satisfy the condition in PropertyAccessImpl, and adding Java-style getters and setters for the property.
was:
The changes introduced with TAP5-1064 allow Scala-style properties to be used from components without the need for Java-style getters and setters. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
> Scala style properties unnecessarily require a field with the same name
> -----------------------------------------------------------------------
>
> Key: TAP5-2016
> URL: https://issues.apache.org/jira/browse/TAP5-2016
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.3.6, 5.2.5
> Reporter: Henning Petersen
> Labels: scala
> Attachments: TAP5-2016.patch
>
>
> The changes introduced with TAP5-1064 allow Scala-style properties to be used from components without the need for Java-style getters and setters. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
> This works:
> {code:title=Scala class}
> var value: String = _
> {code}
> {code:title=Component template}
> <input ... t:value="value" />
> {code}
> This does not:
> {code:title=Scala class}
> def value(): String = ...
> def value_=(value: String) { ... }
> {code}
> {code:title=Component template}
> <input ... t:value="value" />
> {code}
> A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
> Possible workarounds include a dead field in the value class to satisfy the condition in PropertyAccessImpl, and adding Java-style getters and setters for the property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-2016) Scala style properties unnecessarily
require a field with the same name
Posted by "Henning Petersen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henning Petersen updated TAP5-2016:
-----------------------------------
Description:
The changes introduced with TAP5-1064 allow Scala-style properties to be used from components without the need for Java-style getters and setters. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
was:
The changes introduced with TAP5-1064 allow Scala-style properties to be used. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
> Scala style properties unnecessarily require a field with the same name
> -----------------------------------------------------------------------
>
> Key: TAP5-2016
> URL: https://issues.apache.org/jira/browse/TAP5-2016
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.3.6, 5.2.5
> Reporter: Henning Petersen
> Labels: scala
>
> The changes introduced with TAP5-1064 allow Scala-style properties to be used from components without the need for Java-style getters and setters. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
> A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-2016) Scala style properties unnecessarily
require a field with the same name
Posted by "Henning Petersen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henning Petersen updated TAP5-2016:
-----------------------------------
Description:
The changes introduced with TAP5-1064 allow Scala-style properties to be used from components without the need for Java-style getters and setters. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
This works:
var value: String = _
<input ... t:value="value" />
This does not:
def value(): String = ...
def value_=(value: String) { ... }
<input ... t:value="value" />
A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
Possible workarounds include a dead field in the value class to satisfy the condition in PropertyAccessImpl, and adding Java-style getters and setters for the property.
was:
The changes introduced with TAP5-1064 allow Scala-style properties to be used from components without the need for Java-style getters and setters. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
This works:
{code:title=Scala class}
var value: String = _
{code}
{code:title=Component template}
<input ... t:value="value" />
{code}
This does not:
{code:title=Scala class}
def value(): String = ...
def value_=(value: String) { ... }
{code}
{code:title=Component template}
<input ... t:value="value" />
{code}
A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
Possible workarounds include a dead field in the value class to satisfy the condition in PropertyAccessImpl, and adding Java-style getters and setters for the property.
> Scala style properties unnecessarily require a field with the same name
> -----------------------------------------------------------------------
>
> Key: TAP5-2016
> URL: https://issues.apache.org/jira/browse/TAP5-2016
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.3.6, 5.2.5
> Reporter: Henning Petersen
> Labels: scala
> Attachments: TAP5-2016.patch
>
>
> The changes introduced with TAP5-1064 allow Scala-style properties to be used from components without the need for Java-style getters and setters. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
> This works:
> var value: String = _
> <input ... t:value="value" />
> This does not:
> def value(): String = ...
> def value_=(value: String) { ... }
> <input ... t:value="value" />
> A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
> Possible workarounds include a dead field in the value class to satisfy the condition in PropertyAccessImpl, and adding Java-style getters and setters for the property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-2016) Scala style properties unnecessarily
require a field with the same name
Posted by "Henning Petersen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henning Petersen updated TAP5-2016:
-----------------------------------
Description:
The changes introduced with TAP5-1064 allow Scala-style properties to be used from components without the need for Java-style getters and setters. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
This works:
{code:title=Scala class}
var value: String = _
{code}
{code:title=Component template}
<input ... t:value="value" />
{code}
This does not:
{code:title=Scala class}
def value(): String = ...
def value_=(value: String) { ... }
{code}
{code:title=Component template}
<input ... t:value="value" />
{code}
A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
Possible workarounds include a dead field in the value class to satisfy the condition in PropertyAccessImpl, and adding Java-style getters and setters for the property.
was:
The changes introduced with TAP5-1064 allow Scala-style properties to be used from components without the need for Java-style getters and setters. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
> Scala style properties unnecessarily require a field with the same name
> -----------------------------------------------------------------------
>
> Key: TAP5-2016
> URL: https://issues.apache.org/jira/browse/TAP5-2016
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.3.6, 5.2.5
> Reporter: Henning Petersen
> Labels: scala
> Attachments: TAP5-2016.patch
>
>
> The changes introduced with TAP5-1064 allow Scala-style properties to be used from components without the need for Java-style getters and setters. The implementation currently requires a field of the same name as the property to exist on the bean, which is unfortunate.
> This works:
> {code:title=Scala class}
> var value: String = _
> {code}
> {code:title=Component template}
> <input ... t:value="value" />
> {code}
> This does not:
> {code:title=Scala class}
> def value(): String = ...
> def value_=(value: String) { ... }
> {code}
> {code:title=Component template}
> <input ... t:value="value" />
> {code}
> A class which delegates property access to a backing bean is not recognized by PropertyAccessImpl as having any valid properties; the same is the case when the field has a different name than the property.
> Possible workarounds include a dead field in the value class to satisfy the condition in PropertyAccessImpl, and adding Java-style getters and setters for the property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira