[ https://issues.jboss.org/browse/WFLY-1430?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz commented on WFLY-1430: ------------------------------------------- A note on some changes from the previous implementation. 1. It was felt that the name "subsystem=cluster" was confusing, and after some discussion we have decided to change the name to "subsystem=clustering-monitor". 2. The original implementation was based on using CoreGroupCommunicationService as an cluster-wide RPC mechanism. CoreGroupCommunicationService has now been replaced by CommandDispatcherFactory/CommandDispatcher/Command (in the clustering/api maven module). The new implementation will be based on CommandDispatcher. These are embodied in two services ChannelManagementServiceProvider and CacheManagementServiceProvider which provide channel-specific and cache-specific RPC mechanisms. 3. Along with the subsystem name change, we decided to use better package names (i.e. org.wildfly.extension.clustering.monitor for the subsystem, and org.wildfly.clustering.monitoring for the dispatchers) 4. There was also an issue with the location of services ChannelManagementServiceProvider and CacheManagementServiceProvider. It appears there is no way to selectively import services from a JBoss modules dependency; so the two services mentioned previously need to be kept in a separate module from the cluster subsystem extension. I'm pretty close to finishing the new PR. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira