[jboss-jira] [JBoss JIRA] (WFCORE-384) Server does wrongly reference a list of socket binding groups

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on WFCORE-384:
-----------------------------------------

We can't make this a proper singleton (i.e. with an unchangeable address socket-binding-group=standard sockets) without making an incompatible API change, since currently users can pick the name. However, what can be done:

1) Use the WFCORE-365 solution to correctly report the cardinality of the resource definition (max-occurs=1).

2) The add handler can add a step to validate the cardinality. ValidateModelStepHandler could perhaps even do this globally, although I'm reluctant to take the boot overhead cost to do this kind of check for every resource.

> Server does wrongly reference a list of socket binding groups
> -------------------------------------------------------------
>
>                 Key: WFCORE-384
>                 URL: https://issues.jboss.org/browse/WFCORE-384
>             Project: WildFly Core
>          Issue Type: Feature Request
>          Components: Domain Management
>            Reporter: Heiko Braun
>            Assignee: Ken Wills
>             Fix For: 3.0.0.Beta1
>
>
> hbraun: i see that a server (host=foo/server=bar) can have a list of socket-binding-groups
> [10:59am] hbraun: shouldn't that be a a single socket binding instead?
> [11:00am] emuckenhuber: oh... yeah
> [11:00am] hbraun: maybe it's just the description that's wrong
> [11:00am] emuckenhuber: that sounds similar to the jvm thing we had



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)