[jboss-user] [JBoss Messaging] - Re: jboss-messaging-1.4.0.CR3 and jboss-remoting-2.2.2.SP1

We need to change the classpath on the tests to include remoting on client also... The classPath on the examples is using: | <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> | If you add jboss-remoting.jar before jbossall-client.jar, this would be fixed, as jbossall-client.jar includes the old remoting on it. I will also change the examples per your feedback. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088012#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...