[jboss-jira] [JBoss JIRA] (AS7-4396) Consider validating interface refs on domain controller

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on AS7-4396:
---------------------------------------

In CommonXml, parseSocketBinding already does some validation that any specified "interface" actually exists. So, we already enforce that requirement in the parser; enforcing it in the OSH would not be adding a new requirement. The only new requirement would be validating the "default-interface" attribute on socket-binding-group.

Note that when doing this we need to check the parser-level validation to make sure it is properly dealing with expressions. Basically the parser cannot validate expressions.
                
> Consider validating interface refs on domain controller
> -------------------------------------------------------
>
>                 Key: AS7-4396
>                 URL: https://issues.jboss.org/browse/AS7-4396
>             Project: Application Server 7
>          Issue Type: Sub-task
>          Components: Domain Management
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: 7.1.2.Final-redhat1
>
>
> The fix for the parent JIRA rejects refs to non-existent interfaces in socket-binding-group and socket-binding configs *on servers*. The check is not applied on the domain controller. Rationale for that is it is possible to defer specification of the interface to host.xml (where it would vary on each host), and not specify it at all at the domain level.
> The configuration schema supports an "unspecified" interface config for domain.xml (i.e. the interface is just declared as a named placeholder with the requirement that the binding criteria exist in host.xml.) The design intent was this would be used in this sort of situation. So it's valid to do the reference check on the DC as well; I just didn't because I wasn't sure I was willing to break existing configs that didn't do things properly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira