[jboss-jira] [JBoss JIRA] (WFCORE-2253) Some AttributeDefinition instances are configured with default values but say they are required

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFCORE-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated WFCORE-2253:
-------------------------------------
    Description: 
An AD with a default value does not require the user to set it, so configuring it with required = true fka allowNull = false is incorrect. WFCORE-2252 proposes to reject these. This is to clean them up first. 

Note that for any such attributes, if they existed in a previous release a transformer must be written to go along with a change to required=false. Even though they had a default before, the required=true setting made it as if it didn't exist, so this change is the same as adding a default


  was:
An AD with a default value does not require the user to set it, so configuring it with required = true fka allowNull = false is incorrect. WFCORE-2252 proposes to reject these. This is to clean them up first.

Hopefully these will mostly be in test cases where people are less cautious about configuring ADs.



> Some AttributeDefinition instances are configured with default values but say they are required
> -----------------------------------------------------------------------------------------------
>
>                 Key: WFCORE-2253
>                 URL: https://issues.jboss.org/browse/WFCORE-2253
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>
> An AD with a default value does not require the user to set it, so configuring it with required = true fka allowNull = false is incorrect. WFCORE-2252 proposes to reject these. This is to clean them up first. 
> Note that for any such attributes, if they existed in a previous release a transformer must be written to go along with a change to required=false. Even though they had a default before, the required=true setting made it as if it didn't exist, so this change is the same as adding a default



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)