[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:comment-tabpanel&focusedCommentId=13638111#comment-13638111 ] 

Paul Ferraro commented on WFLY-10339:
-------------------------------------

[~mnovak] 
{quote}As broadcast-group and discovery-group must be still present because of backward compatibility reasons I'm not sure if this makes life easier as there will be 3 types of discovery and broadcast groups (2 new and 1 old).{quote}

The old broadcast/discovery-group resources will be present, but deprecated, in the new version of the model.  They will not be present in the new version of the schema.  Each new resource will still provide the same capabilities.

{quote}From user perspective it makes sense to have capibilities \[sic] on current attributes of broadcast-group and discovery-group.{quote}

The purpose of this jira is to correct ambiguities in the messaging management model that complicate the corresponding feature specs for these resources in galleon.  There are already capability constraints on the existing attributes.  These are the source of the ambiguous requirement specs.

> 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: Paul Ferraro
>
> 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)