[jboss-cvs] JBoss Messaging SVN: r6838 - branches/Branch_1_4/docs/userguide/en/modules.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon May 18 07:29:23 EDT 2009
Author: gaohoward
Date: 2009-05-18 07:29:23 -0400 (Mon, 18 May 2009)
New Revision: 6838
Modified:
branches/Branch_1_4/docs/userguide/en/modules/configuration.xml
branches/Branch_1_4/docs/userguide/en/modules/installation.xml
branches/Branch_1_4/docs/userguide/en/modules/introduction.xml
Log:
documentation change for 1.4.3.SP3-CP08
-added ordering group feature
-ordering group attributes in ConnectionFactory configuration section
-mention the servlet support in features section
Modified: branches/Branch_1_4/docs/userguide/en/modules/configuration.xml
===================================================================
--- branches/Branch_1_4/docs/userguide/en/modules/configuration.xml 2009-05-18 11:14:20 UTC (rev 6837)
+++ branches/Branch_1_4/docs/userguide/en/modules/configuration.xml 2009-05-18 11:29:23 UTC (rev 6838)
@@ -2289,6 +2289,27 @@
</section>
</section>
+ <section id="conf.connectionfactory.attributes.enableorderinggroup">
+ <title>EnableOrderingGroup</title>
+
+ <para>This parameter controls whether the strict message ordering is enabled or not
+ on the ConnectionFactory. If set to 'true', all messages that are sent from any producers
+ created from this connection factory become ordering group messages.</para>
+
+ <para>The default value is false.</para>
+ </section>
+
+ <section id="conf.connectionfactory.attributes.defaultorderinggroupname">
+ <title>DefaultOrderingGroupName</title>
+
+ <para>the default name for the message ordering group. If absent,
+ the group name will be generated automatically.</para>
+
+ <para>This attribute takes effect only if the EnableOrderingGroup attribute is true.</para>
+ </section>
+
+ </section>
+
<!-- End conf.connectionfactory.attributes -->
</section>
Modified: branches/Branch_1_4/docs/userguide/en/modules/installation.xml
===================================================================
--- branches/Branch_1_4/docs/userguide/en/modules/installation.xml 2009-05-18 11:14:20 UTC (rev 6837)
+++ branches/Branch_1_4/docs/userguide/en/modules/installation.xml 2009-05-18 11:29:23 UTC (rev 6838)
@@ -7,7 +7,7 @@
procedure, you will create a JBoss Messaging configuration that will start a
clustered or non-clustered messaging server.</para>
- <para>Please note that JBoss EAP 4.3 and JBoss 5 comes with JBoss Messaging
+ <para>Please note that JBoss EAP 4.3 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>
@@ -613,7 +613,7 @@
<listitem>
<para>
<note>
- JBoss Messaging 1.4.3.GA requires pecific versions
+ JBoss Messaging 1.4.0.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.
@@ -915,13 +915,15 @@
<itemizedlist>
<listitem>
<para><note>
- 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:
+ This version of JBoss Messaging requires JBoss Remoting 2.2.2.SP12.
+ If you are using EAP 4.3 you will have the required JAR available already.
+
+ Always use the version of JBoss Remoting that comes with the EAP 4.3.
+ If you're using a different version of Application Server you should download it.
+ The patched jar can be found at here
+ [http://repository.jboss.com/jboss/remoting/2.2.2.SP12-brew/lib/].
+ Please download it and make sure this jar is on your classpath *before* jbossall-client.jar.
- <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>
@@ -970,59 +972,6 @@
</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>
Modified: branches/Branch_1_4/docs/userguide/en/modules/introduction.xml
===================================================================
--- branches/Branch_1_4/docs/userguide/en/modules/introduction.xml 2009-05-18 11:14:20 UTC (rev 6837)
+++ branches/Branch_1_4/docs/userguide/en/modules/introduction.xml 2009-05-18 11:29:23 UTC (rev 6838)
@@ -86,6 +86,10 @@
</listitem>
<listitem>
+ <para>Servlet transport to allow messaging through a dedicated servlet.</para>
+ </listitem>
+
+ <listitem>
<para>SSL transport</para>
</listitem>
@@ -102,6 +106,14 @@
<para>Automatic paging of messages to storage. Allows the use of very
large queues - too large to fit in memory at once</para>
</listitem>
+
+ <listitem>
+ <para>Strict message ordering. JBoss Messaging's implementation of strict message ordering
+ is called message ordering groups. Messages in one orddering group obey strict delivering order, which means
+ that messages in an ordering group will be delivered exactly in the order of their arrival at the target queue (FIFO).
+ Ordering groups can be enabled by either programming APIs or configuration.</para>
+ </listitem>
+
</itemizedlist>
<para>Clustering features:</para>
More information about the jboss-cvs-commits
mailing list