Currently, all protocols that do define a module to load the protocol class from are required to provide a FQCN. The loading mechanism in place behaves differently from other protocols residing in org.jgroups and it's dependent modules where the prefix of 'org.jgroups.protocols' is attempted as well.

Moreoever, this is the loading that jgroups itself does and thus all example stacks that work for jgroups plain require further adaptation to WildFly.

This thus behaves differently causing confusion.

]) - failure description: "WFLYCLJG0016: Unable to load protocol class raft.RAFT"

The downside is an extra class load attempt.