[jboss-jira] [JBoss JIRA] (WFLY-12430) The docs/examples/configs/standalone-gossip-[full-ha].xml examples use a TCPGOSSIP config that will persist differently

[Brian Stansberry (Jira)]

Brian Stansberry created WFLY-12430:
---------------------------------------

             Summary: The docs/examples/configs/standalone-gossip-[full-ha].xml examples use a TCPGOSSIP config that will persist differently
                 Key: WFLY-12430
                 URL: https://issues.jboss.org/browse/WFLY-12430
             Project: WildFly
          Issue Type: Bug
          Components: Clustering
            Reporter: Brian Stansberry
            Assignee: Brian Stansberry


Minor thing I want to sort to make legacy feature-pack-driven builds as consistent as possible with galleon-driven ones....

The docs/examples/configs/standalone-gossip-[full-ha].xml examples configure a TCPGOSSIP protocol but without the required outbound-socket-bindings attribute. Compatibility code in the subsystem handles this by converting the address value to 'org.jgroups.protocols.TCPGOSSIP', which in turn has a different resource registration and Galleon feature spec.  Upshot is when the resource is persisted the xml will read org.jgroups.protocols.TCPGOSSIP. To clarify this, rather than relying on magic compatibility code the inputs for generating the configs should explicitly use 'org.jgroups.protocols.TCPGOSSIP'.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)