[jboss-jira] [JBoss JIRA] (WFLY-32) Outbound-socket-binding configs don't propagate to domain server if socket-binding-group has no normal socket bindings

[Brian Stansberry (JIRA)]

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

Brian Stansberry updated WFLY-32:
---------------------------------

    Git Pull Request: https://github.com/wildfly/wildfly/pull/4416  (was: https://github.com/jbossas/jboss-as/pull/4416)

    
> Outbound-socket-binding configs don't propagate to domain server if socket-binding-group has no normal socket bindings
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-32
>                 URL: https://issues.jboss.org/browse/WFLY-32
>             Project: WildFly
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: 8.0.0.Alpha1
>
>
> With a socket-binding-group config like the following, the outbound-socket-binding=mail-smtp:add op is not included in the list of boot ops sent to domain server.
> {code}
>     <socket-binding-groups>
>         <socket-binding-group name="sockets1" default-interface="public">
>             <outbound-socket-binding name="mail-smtp">
>                 <remote-destination host="localhost" port="1111"/>
>             </outbound-socket-binding>
>         </socket-binding-group>
> {code}

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