[jboss-jira] [JBoss JIRA] (WFLY-912) Cardinality constraints on children are not enforced after parsing

[Stuart Douglas (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12961477#comment-12961477 ] 

Stuart Douglas commented on WFLY-912:
-------------------------------------

Is this still relevant? I think that most resources that have a cardinality constrain have it enforced by forcing the resource to be registered under a specific name. 
                
> Cardinality constraints on children are not enforced after parsing
> ------------------------------------------------------------------
>
>                 Key: WFLY-912
>                 URL: https://issues.jboss.org/browse/WFLY-912
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Domain Management
>            Reporter: Brian Stansberry
>            Priority: Minor
>
> The parsers enforce cardinality constraints on child elements in the model, but they aren't enforced thereafter. So, for example, a second "socket-binding-group" could be added to a standalone server via a management operation.

--
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