[
https://issues.jboss.org/browse/WFCORE-2669?page=com.atlassian.jira.plugi...
]
Brian Stansberry updated WFCORE-2669:
-------------------------------------
Description:
Let's discuss before doing anything on this.
For lists and maps, the builder call to setValidator is really a call to
setElementValidator, with a call to set[List|Map]Validator being necessary if some special
validation of the overall list/map is desired.
We should deprecate setValidator to help emphasize to people that really
setElementValidator is what is happening.
was:
For lists and maps, the builder call to setValidator is really a call to
setElementValidator, with a call to set[List|Map]Validator being necessary if some special
validation of the overall list/map is desired.
We should deprecate setValidator to help emphasize to people that really
setElementValidator is what is happening.
Deprecate setValidator method in builders for ListAttributeDefinition
and MapAttributeDefinition
------------------------------------------------------------------------------------------------
Key: WFCORE-2669
URL:
https://issues.jboss.org/browse/WFCORE-2669
Project: WildFly Core
Issue Type: Enhancement
Components: Domain Management
Reporter: Brian Stansberry
Priority: Minor
Fix For: 4.0.0.Beta1
Let's discuss before doing anything on this.
For lists and maps, the builder call to setValidator is really a call to
setElementValidator, with a call to set[List|Map]Validator being necessary if some special
validation of the overall list/map is desired.
We should deprecate setValidator to help emphasize to people that really
setElementValidator is what is happening.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)