[jboss-cvs] JBoss Messaging SVN: r6006 - in branches/Branch_1_4/docs: userguide/en/modules and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Mar 5 06:13:22 EST 2009
Author: gaohoward
Date: 2009-03-05 06:13:22 -0500 (Thu, 05 Mar 2009)
New Revision: 6006
Modified:
branches/Branch_1_4/docs/README.html
branches/Branch_1_4/docs/userguide/en/modules/about.xml
branches/Branch_1_4/docs/userguide/en/modules/installation.xml
Log:
Release Notes for 1.4.3.GA
Modified: branches/Branch_1_4/docs/README.html
===================================================================
--- branches/Branch_1_4/docs/README.html 2009-03-05 10:56:05 UTC (rev 6005)
+++ branches/Branch_1_4/docs/README.html 2009-03-05 11:13:22 UTC (rev 6006)
@@ -3,26 +3,22 @@
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="content-type">
- <title>Release Notes - JBoss Messaging - Version 1.4.2.GA-SP1.</title>
+ <title>Release Notes - JBoss Messaging - Version 1.4.3.GA</title>
</head>
<body>
-<h1>Release Notes - JBoss Messaging - Version 1.4.2.GA-SP1</h1>
+<h1>Release Notes - JBoss Messaging - Version 1.4.3.GA</h1>
<br>
-<h2>12 February 2009</h2>
+<h2>5 March 2009</h2>
-These are the release notes for JBoss Messaging 1.4.2.GA-SP1.<br><br>
+<p>JBoss Messaging Version 1.4.3.GA is a release made and tested exclusively for the <b>JBoss AS 5.1.0.Beta1 only</b> and it should be part of the JBoss 5 download bundle.</p>
-For full description of the contents please see the <a href="https://jira.jboss.org/jira/secure/ReleaseNote.jspa?version=12313241&styleName=Html&projectId=12310061">JBoss Messaging project JIRA.</a><br><br>
+<p>For the full description of this release, see the <a href="https://jira.jboss.org/jira/secure/ReleaseNote.jspa?version=12313042&styleName=Html&projectId=12310061">JBoss Messaging project JIRA.</a></p>
-When upgrading an existing installation be sure to update all the configuration files in server/<server name>/deploy/jboss-messaging.sar with the newer versions and replace jboss-messaging.jar in server/<server name>/lib and on the client classpath. <br><br>
+<p>Enjoy!</p>
-This release of JBoss Messaging also requires specific versions of JBoss Remoting, JBoss AOP and Javassist. For the correct versions see the user-guide installation section. Be sure that server/<server name>/lib contains these jar and they are also present as the first entry on the client classpath. This is critical to ensure proper operation of JBoss Messaging!<br><br>
-
-Enjoy!<br><br>
-
</body>
</html>
Modified: branches/Branch_1_4/docs/userguide/en/modules/about.xml
===================================================================
--- branches/Branch_1_4/docs/userguide/en/modules/about.xml 2009-03-05 10:56:05 UTC (rev 6005)
+++ branches/Branch_1_4/docs/userguide/en/modules/about.xml 2009-03-05 11:13:22 UTC (rev 6006)
@@ -6,7 +6,7 @@
is a complete rewrite of JBossMQ, the legacy JBoss JMS provider.</para>
<para>JBoss Messaging is the default JMS provider in JBoss Enterprise Application Platform version 4.3 or later, and JBoss SOA Platform.
- It is also the default JMS provider in JBoss Application Server 5, and is the default JMS provider for JBoss ESB.</para>
+ It is also the default JMS provider in JBoss Application Server 5, and is the default JMS provider for JBoss ESB.</para>
<para>JBoss Messaging is an integral part of Red Hat's strategy for
messaging.</para>
Modified: branches/Branch_1_4/docs/userguide/en/modules/installation.xml
===================================================================
--- branches/Branch_1_4/docs/userguide/en/modules/installation.xml 2009-03-05 10:56:05 UTC (rev 6005)
+++ branches/Branch_1_4/docs/userguide/en/modules/installation.xml 2009-03-05 11:13:22 UTC (rev 6006)
@@ -9,7 +9,7 @@
<para>Please note that JBoss EAP 4.3 and JBoss 5 comes with JBoss Messaging
pre-installed as default JMS provider so if you are using that, there is no need to manually
- install JBoss Messaging.</para>
+ install JBoss Messaging</para>
<para>By default, JBoss AS 4.2 ships with JBossMQ as default JMS provider.
In order to use the JBoss AS instance with JBoss Messaging, you need to
@@ -175,7 +175,12 @@
<listitem>
<para>If you want to run multiple JBoss Messaging nodes on the same
box using the same IP address, e.g. for development purposes, then
- you can use the ServiceBindingManager to do this as follows:</para>
+ you can use the ServiceBindingManager to do this as follows:</para>
+
+ <para><warning>JBoss5 has introduced a much simpler ServiceBindingManager.
+ You should refer to the JBoss5 documentation about how to administer the new bindingManager if you are using JBoss5.
+ </warning></para>
+
<itemizedlist>
<listitem>
@@ -256,8 +261,8 @@
may be out of date and you will need to copy the config from
<literal>remoting-bisocket-service.xml. DO NOT just copy and
paste from the above example - copy it from the JBoss Messaging
- distribution.</literal>.
- </warning>
+ distribution.</literal>. On JBoss5 the ports are controlled by
+ system-property substitution hence you don't need to worry about copying the config into bindings.xml</warning>
<para>You should ensure that each node is configured to use a
different ports range.</para>
@@ -608,16 +613,17 @@
<listitem>
<para>
<note>
- JBoss Messaging 1.4 requires a patched version of jboss-remoting.jar. This version is available
- and can be downloaded from <ulink url="http://repository.jboss.com/jboss/remoting/2.2.2.SP11-brew/"> here</ulink>.
- The version is JBoss Remoting 2.2.2.SP11-brew. Please download it and copy it into the
- <literal>$JBOSS_HOME/server/<your server name>/lib</literal> directory of any server profiles that use JBoss
- Messaging. If you are using JBoss Messaging from a standalone client also make sure this jar is on your
- classpath *before* jbossall-client.jar.
- </note>
+ JBoss Messaging 1.4.3.GA requires pecific versions
+ of jboss-remoting.jar if used outside of JBoss 5. If you are installing JBoss Messaging 1.4.3.GA at JBoss 4.2+, you should use this version:
+ <ulink url="http://repository.jboss.com/jboss/remoting/2.5.0.SP2/ ">Remoting 2.5.0.SP2</ulink>.
+ If you are using JBoss5 you don't need to take any extra steps on the remoting installation.
+ </note>
</para>
</listitem>
+ <para>You should also make these changes on any configuration you
+ choose, to remove all references to the old JBossMQ:</para>
+
<listitem>
<para>Edit <literal>$JBOSS_CONFIG/deploy/jms-ds.xml</literal> and
replace jboss.mq by jboss.messaging on every occurrence</para>
@@ -909,11 +915,14 @@
<itemizedlist>
<listitem>
<para><note>
- JBoss Messaging 1.4 requires a patched version of jboss-remoting.jar. The version is JBoss Remoting
- 2.2.2.SP11-brew. This version is available on JBoss EAP 4.3, so if you're using a different version you
- should download it. The patched jar can be found at <ulink url="http://repository.jboss.com/jboss/remoting/2.2.2.SP11-brew/lib/">here</ulink>.
- Please download it and make sure this jar is on your classpath *before* jbossall-client.jar.
- </note></para>
+ If you are using JBoss Messaging 1.4.3.GA outiside of JBoss 4.2 or EAP 4.3, you need to make sure you use a JBoss Remoting 2.5.0.SP2. If you are using JBoss5 or EAP 4.3 you will have the required JAR available already:
+ The version could be found at:
+
+ <ulink
+ url="http://repository.jboss.com/jboss/remoting/2.5.0.SP2/lib/">here</ulink>
+
+ . Please download it and make sure this jar is on your classpath *before* jbossall-client.jar.
+ </note></para>
</listitem>
<listitem>
@@ -929,9 +938,9 @@
<listitem>
<para>$JBOSS_HOME/server/<SERVER_NAME>/deploy/jboss-aop.deployer/jboss-aop.jar</para>
- <para>JBoss AOP 1.5.5.GA_CP03-brew</para>
+ <para>JBoss AOP 2.0.1.GA</para>
- <para><ulink url="http://repository.jboss.com/jboss/aop/1.5.5.GA_CP03-brew/lib/">http://repository.jboss.com/jboss/aop/1.5.5.GA_CP03-brew/lib/</ulink></para>
+ <para><ulink url="http://repository.jboss.com/jboss/aop/2.0.1.GA/lib/">http://repository.jboss.com/jboss/aop/2.0.1.GA/lib/</ulink></para>
<para>(For AOP, sometimes you have to use a specific JAR according to
your JVM of choice. Use the most convenient for you)</para>
@@ -940,19 +949,19 @@
<listitem>
<para>$JBOSS_HOME/server/<SERVER_NAME>/lib/javassist.jar</para>
- <para>Javassist 3.8.0.GA</para>
+ <para>Javassist 3.9.0.GA</para>
<para><ulink
- url="http://repository.jboss.com/javassist/3.8.0.GA-brew/lib/">http://repository.jboss.com/javassist/3.8.0.GA-brew/lib/</ulink></para>
+ url="http://repository.jboss.com/javassist/3.9.0.GA/lib/">http://repository.jboss.com/javassist/3.9.0.GA/lib/</ulink></para>
</listitem>
<listitem>
<para>$JBOSS_HOME/server/<SERVER_NAME>/lib/trove.jar</para>
- <para>trove 1.0.2-brew</para>
+ <para>trove 1.0.2</para>
<para><ulink
- url="http://repository.jboss.com/trove/1.0.2-brew/lib/">http://repository.jboss.com/trove/1.0.2-brew/lib/</ulink></para>
+ url="http://repository.jboss.com/trove/1.0.2/lib/">http://repository.jboss.com/trove/1.0.2/lib/</ulink></para>
</listitem>
<listitem>
@@ -961,6 +970,59 @@
</itemizedlist>
</section>
+ <section id="inst.remoteclient.jb5">
+ <title>Accessing JBoss Messaging from a remote client - JBoss 5.0</title>
+
+ <para>In order to access JBoss Messaging from a client outside the JBoss
+ app server, you will need to ensure the following jar files are on the
+ client classpath:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>$JBOSS_HOME/client/jnp-client.jar</para>
+ </listitem>
+ <listitem>
+ <para>$JBOSS_HOME/client/jboss-javaee.jar</para>
+ </listitem>
+ <listitem>
+ <para>$JBOSS_HOME/client/jboss-messaging.jar</para>
+ </listitem>
+ <listitem>
+ <para>$JBOSS_HOME/client/jboss-remoting.jar</para>
+ </listitem>
+ <listitem>
+ <para>$JBOSS_HOME/client/jboss-serialization.jar</para>
+ </listitem>
+ <listitem>
+ <para>$JBOSS_HOME/client/javassist.jar</para>
+ </listitem>
+ <listitem>
+ <para>$JBOSS_HOME/client/jboss-aop-client.jar</para>
+ </listitem>
+ <listitem>
+ <para>$JBOSS_HOME/client/trove.jar</para>
+ </listitem>
+ <listitem>
+ <para>$JBOSS_HOME/client/log4j.jar</para>
+ </listitem>
+ <listitem>
+ <para>$JBOSS_HOME/client/jboss-logging-spi.jar</para>
+ </listitem>
+ <listitem>
+ <para>$JBOSS_HOME/client/jboss-logging-log4j.jar</para>
+ </listitem>
+ <listitem>
+ <para>$JBOSS_HOME/client/jboss-common-core.jar</para>
+ </listitem>
+ <listitem>
+ <para>$JBOSS_HOME/client/jboss-mdr.jar</para>
+ </listitem>
+ <listitem>
+ <para>$JBOSS_HOME/client/concurrent.jar</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
<section id="inst.mqmessagemigration">
<title>Migrating Messages from JBoss MQ to JBoss Messaging</title>
More information about the jboss-cvs-commits
mailing list