[
https://issues.jboss.org/browse/WFLY-3075?page=com.atlassian.jira.plugin....
]
Jeff Mesnil resolved WFLY-3075.
-------------------------------
Resolution: Rejected
the messaging subsystem no longer required this socket-binding for its HA configuration
(leveraging jgroups instead) so I have no longer a valid use case to add supplements to
socket-bindings in the template assembly
add supplement to socket-bindings in template assembly
------------------------------------------------------
Key: WFLY-3075
URL:
https://issues.jboss.org/browse/WFLY-3075
Project: WildFly
Issue Type: Enhancement
Components: Build System
Affects Versions: 8.0.0.Final
Reporter: Jeff Mesnil
Assignee: Tomaz Cerar
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 was sent by Atlassian JIRA
(v6.3.11#6341)