Also, if you are running any of the examples make sure you add the new jboss-remoting.jar ahead of the jbossall-client.jar in the classpath. This is because the jbossall-client.jar contains the old remoting classes. This can be done by editing the build.xml for each example, it currently looks something like the following: | <path id="execution.classpath"> | <pathelement path="./etc"/> | <pathelement path="../common/output/classes"/> | <pathelement path="./output/classes"/> | <fileset file="${messaging.client.jar.path}/${messaging.client.jar.name}"/> | <fileset file="${jboss.home}/client/jbossall-client.jar"/> | <fileset file="${jboss.home}/server/${jboss.configuration}/lib/log4j.jar"/> | <fileset file="${jboss.home}/server/${jboss.configuration}/lib/javassist.jar"/> | <fileset file="${jboss.home}/server/${jboss.configuration}/deploy/jboss-aop-jdk50.deployer/jboss-aop-jdk50.jar"/> | <fileset file="${jboss.home}/server/${jboss.configuration}/deploy/jboss-aop-jdk50.deployer/trove.jar"/> | </path> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088289#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...