[
https://issues.jboss.org/browse/WFLY-10339?page=com.atlassian.jira.plugin...
]
ehsavoie Hugonnet commented on WFLY-10339:
------------------------------------------
We could solve it the #2 way by setting a static capability reference on the
jgroups-cluster attribute and keep the dynamic one on the jgroups-channel.
This seems to work with the Galleon change and our current test suite
Broadcast/discovery-group resources have ambiguous requirement specs
--------------------------------------------------------------------
Key: WFLY-10339
URL:
https://issues.jboss.org/browse/WFLY-10339
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 12.0.0.Final
Reporter: Paul Ferraro
Assignee: ehsavoie Hugonnet
Currently, the broadcast/discovery-group resources have messy requirement specs, as the
capabilities that they require are dependent whether or not the jgroups-cluster attribute
is defined.
I suggest splitting these resources into 2:
{code}/subsystem=messaging-activemq/server=*/jgroups-broadcast-group=*{code}
{code}/subsystem=messaging-activemq/server=*/jgroups-discovery-group=*{code}
which requires clustering capabilities
and
{code}/subsystem=messaging-activemq/server=*/socket-broadcast-group=*{code}
{code}/subsystem=messaging-activemq/server=*/socket-discovery-group=*{code}
which requires a socket-binding capability.
This results in clearer requirement specs - which helps simplify the introspection of
this subsystem for provisioning purposes.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)