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

[Jeff Mesnil (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-10339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13638526#comment-13638526 ] 

Jeff Mesnil commented on WFLY-10339:
------------------------------------

>From the messaging point of view, we have one resource to represent discovery-group.

The whole point of this resource is to delegate the actual discovery mechanism to other resources (wether it is internal with Artemis UDP stack, JGroups resources or any future resources from the discovery subsystem).

I don't understand why we should multiply resources in Artemis for every supported mechanisms.

Capabilities and requirements based on attributes should be sufficient:
* if socket-binding is defined, it requires a socket-binding capability
* if jgroups-xxx attribute is defined, it requires a JGroups capability
* etc.

[~aloubyansky] is that something that Galleon can modelize? I looked at http://docs.wildfly.org/galleon/#_features but that was not clear to me if Galleon supports 'alternative' requirements for a single resource (depending on which attribute is defined, it requires capability A or B).

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