1 Reply Latest reply on Sep 25, 2007 3:34 AM by Andy Taylor

    JBoss Messaging 1.4.0.CR3 released

    Tim Fox Master

      JBoss Messaging 1.4.0.CR3 has been released and is available for download.

      http://labs.jboss.com/jbossmessaging/downloads/jboss-messaging-1.4.0.CR3.zip

      This is a candidate release for JBoss Messaging 1.4.0.

      Please see the release notes for the description of the release.

      Important note! This release of JBoss Messaging relies a patched jboss-remoting.jar (2.2.2.SP1) which is available in the repository. See the installation guide for more information.

      JBoss Messaging 1.4.0 is also Java 5 only. This is because we build against JBoss AS 4.2 whose libraries are built against Java 5 only. We need to have our libraries synched up with AS 4.2 in order to be fully integrated with it.

        • 1. Re: JBoss Messaging 1.4.0.CR3 released
          Andy Taylor Master

          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>