2 Replies Latest reply on Feb 22, 2007 12:31 AM by ovidiu.feodorov

    JBoss Messaging 1.2.0.CR1 Released

    ovidiu.feodorov

      JBoss Messaging 1.2.0.CR1 has been released and it is available for download on jboss.org (http://labs.jboss.com/portal/jbossmessaging/downloads) and sourceforge (http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=157261).

      1.2.0.CR1 is functionally equivalent with Beta2, the only notable addition being the JBoss Remoting "bisocket" transport, which replaces the unidirectional "socket" as default Messaging transport. This new transport eliminates the need for a ServerSocket on the client side. I would like to use this opportunity to thank Ron Sigal from the Remoting team, for the effort he put into integrating and testing the "bisocket" layer.

      Aside from that, the rest of the changes are mostly bug fixes. The complete list of fixes introduced by this release is available here: http://jira.jboss.org/jira/secure/ReleaseNote.jspa?version=12310920&styleName=Html&projectId=12310061.

      We will be waiting for community feedback for a while before releasing the GA, which is scheduled for the end of this month (Feb 28).

      The Messaging road map is available here: http://jira.jboss.org/jira/browse/JBMESSAGING?report=com.atlassian.jira.plugin.system.project:roadmap-panel.

        • 1. Re: JBoss Messaging 1.2.0.CR1 Released
          bander

          Just a quick note to mention the installation process now requires Ant 1.6.3 or higher.

          Our project is using Ant 1.6.2 and I received the following error:

          C:\jboss-messaging-1.2.0.CR1\util\release-admin.xml:45: The following error occurred while executing this line:
          C:\jboss-messaging-1.2.0.CR1\util\release-admin.xml:680: Class org.apache.tools.ant.taskdefs.ConditionTask doesn't support the nested "length" element.

          The nested "length" element was introduced in 1.6.3 :)

          • 2. Re: JBoss Messaging 1.2.0.CR1 Released
            ovidiu.feodorov

            Thanks

            I will add this observation to the GA release notes.

            We have this http://jira.jboss.org/jira/browse/JBMESSAGING-725, which will insure the build process fails quicky and with a self-explanatory message if ant is too old. Better yet, we should ship our own embedded ant.

            I don't know if this is something that is generally known, but anybody can pick an open task and send a patch for it :)