[
https://issues.apache.org/jira/browse/ISIS-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-1721:
------------------------------
Affects Version/s: 1.10.0
Fix Version/s: 1.16.0
Reporter: Martin Grigorov (was: Dan Haywood)
Description:
(recreated from ISIS-1082, which has got incorrect commits against it).
In a domain entity I wanted to use a property with a default value:
{code}
private boolean flag = true;
// getter & setter
{code}
Surprisingly Isis re-initialized its value to 'false' after creating the
instance by using the setter.
http://isis.apache.org/more-advanced-topics/how-to-07-010-How-to-set-up-the-initial-value-of-a-property-programmatically.html
explains the behavior but maybe we should rething whether Isis should
initialize the properties at all.
was:(recreated from ISIS-1082, which has got incorrect commits against it).
> Isis should optionally not override the default values of entities.
> -------------------------------------------------------------------
>
> Key: ISIS-1721
> URL: https://issues.apache.org/jira/browse/ISIS-1721
> Project: Isis
> Issue Type: Bug
> Affects Versions: 1.10.0
> Reporter: Martin Grigorov
> Priority: Minor
> Fix For: 1.16.0
>
>
> (recreated from ISIS-1082, which has got incorrect commits against it).
> In a domain entity I wanted to use a property with a default value:
> {code}
> private boolean flag = true;
> // getter & setter
> {code}
> Surprisingly Isis re-initialized its value to 'false' after creating the
> instance by using the setter.
> http://isis.apache.org/more-advanced-topics/how-to-07-010-How-to-set-up-the-initial-value-of-a-property-programmatically.html
> explains the behavior but maybe we should rething whether Isis should
> initialize the properties at all.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
