[jboss-jira] [JBoss JIRA] (WFLY-10339) Broadcast/discovery-group resources have ambiguous requirement specs

[Paul Ferraro (JIRA)]

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

Paul Ferraro updated WFLY-10339:
--------------------------------
    Description: 
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}/server=*/jgroups-broadcast-group=*{code}
{code}/server=*/jgroups-discovery-group=*{code}
which requires clustering capabilities

and

{code}/server=*/socket-broadcast-group=*{code}
{code}/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.

  was:
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:
/server=*/jgroups-broadcast-group=*
/server=*/jgroups-discovery-group=*
which requires clustering capabilities

and

/server=*/socket-broadcast-group=*
/server=*/socket-discovery-group=*
which requires a socket-binding capability.

This results in clearer requirement specs - which helps simplify the introspection of this subsystem for provisioning purposes.



> 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: Jeff Mesnil
>
> 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}/server=*/jgroups-broadcast-group=*{code}
> {code}/server=*/jgroups-discovery-group=*{code}
> which requires clustering capabilities
> and
> {code}/server=*/socket-broadcast-group=*{code}
> {code}/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)