[jboss-jira] [JBoss JIRA] (WFLY-6008) CommandDispatcher commands execute using wrong TCCL

[ https://issues.jboss.org/browse/WFLY-6008?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-6008: ------------------------------- Description: A command containing the following code: {noformat} public class MyCommand implements Command<Void, Void> { public Void execute(Void context) throws Exception { Thread.currentThread().getClassLoader().loadClass(this.getClass().getName()); } } {noformat} currently throws a ClassNotFoundException. A command executed with the command dispatcher should be able to load application classes using the TCCL. In fact, the following application callbacks from the clustering API all use the wrong TCCL: * CommandDispatcher command execution * CommandDispatcherFactory cluster membership listener * Cache topology membership listener * Registry listener * ServiceProviderRegistry listener * Singleton election policy and listener was: A command containing the following code: {noformat} public class MyCommand implements Command<Void, Void> { public Void execute(Void context) throws Exception { Thread.currentThread().getClassLoader().loadClass(this.getClass().getName()); } } {noformat} currently throws a ClassNotFoundException. A command executed with the command dispatcher should be able to load application classes using the TCCL. In fact, the following application callbacks from the clustering API all use the wrong TCCL: * CommandDispatcher command execution * CommandDispatcherFactory cluster membership listener * Cache topology membership listener * Registry listener * ServiceProviderRegistry listener -- This message was sent by Atlassian Jira (v7.13.5#713005)