Been doing a lot of refactoring, etc. related to ClusterPartition due to using JBoss Cache for state and multiplexer for the Channel. One thing that is confusing me is the distinction between HAPartition, HAPartitionImpl and ClusterPartition. HAPartition is a generic interface that is part of the end user API. No problem. HAPartitionImpl is an internal implementation that uses JGroups as an implementation detail. Again clear. ClusterPartition though doesn't really seem to be part of an end user API. It's function is just to 1) expose an MBean interface so it can accept config attributes from the deployer and pass them on to HAPartitionImpl and 2) create a JChannel and pass it on the HAPartitionImpl. All of these functions are really just part of the implementation details of HAPartitionImpl. It's not clear to me why it's a separate service. I'm thinking the way to go here is to combine the ClusterPartition and HAPartitionImpl classes, with the combined class exposing a management interface that extends HAPartition with the implementation specific config attributes. From the end user point of view, the API is still HAPartition. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3966529#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...