[jboss-jira] [JBoss JIRA] (WFLY-3075) add supplement to socket-bindings in template assembly

[Jeff Mesnil (JIRA)]

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

Jeff Mesnil updated WFLY-3075:
------------------------------

    Description: 
The messaging.xml subsystem configuration defines a "ha" supplement used to build the standalone-full-ha.xml.

This supplement requires to have a socket-binding for multicast:

{noformat}
   <socket-binding name="messaging-group" port="0" multicast-address="${jboss.messaging.group.address:231.7.7.7}" multicast-port="${jboss.messaging.group.port:9876}"/>
{noformat}

However, this socket-binding is *always* added even when the "ha" supplement is not used.
We end up with a standalone-full.xml configuration with the regular messaging subsystem (no ha parts) *and* the messaging-group socket binding.

Ideally, this socket-binding should only be added when the ha supplement is used.
One way to achieve this would be to allow <socket-binding> definitions inside the <supplement>/<replacement> elements.



  was:
The messaging.xml subsystem configuration defines a "ha" supplement used to build the standalone-full-ha.xml.

This supplement requires to have a socket-binding for multicast:

   <socket-binding name="messaging-group" port="0" multicast-address="${jboss.messaging.group.address:231.7.7.7}" multicast-port="${jboss.messaging.group.port:9876}"/>

However, this socket-binding is *always* added even when the "ha" supplement is not used.
We end up with a standalone-full.xml configuration with the regular messaging subsystem (no ha parts) *and* the messaging-group socket binding.

Ideally, this socket-binding should only be added when the ha supplement is used.
One way to achieve this would be to allow <socket-binding> definitions inside the <supplement>/<replacement> elements.




    
> add supplement to socket-bindings in template assembly
> ------------------------------------------------------
>
>                 Key: WFLY-3075
>                 URL: https://issues.jboss.org/browse/WFLY-3075
>             Project: WildFly
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Build System
>    Affects Versions: 8.0.0.Final
>            Reporter: Jeff Mesnil
>            Assignee: Paul Gier
>             Fix For: 9.0.0.CR1
>
>
> The messaging.xml subsystem configuration defines a "ha" supplement used to build the standalone-full-ha.xml.
> This supplement requires to have a socket-binding for multicast:
> {noformat}
>    <socket-binding name="messaging-group" port="0" multicast-address="${jboss.messaging.group.address:231.7.7.7}" multicast-port="${jboss.messaging.group.port:9876}"/>
> {noformat}
> However, this socket-binding is *always* added even when the "ha" supplement is not used.
> We end up with a standalone-full.xml configuration with the regular messaging subsystem (no ha parts) *and* the messaging-group socket binding.
> Ideally, this socket-binding should only be added when the ha supplement is used.
> One way to achieve this would be to allow <socket-binding> definitions inside the <supplement>/<replacement> elements.

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