[jboss-cvs] JBossAS SVN: r93787 - in projects/docs/enterprise/5.0: JBoss_Messaging_1.4.3/en-US and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sun Sep 20 19:44:40 EDT 2009
Author: laubai
Date: 2009-09-20 19:44:40 -0400 (Sun, 20 Sep 2009)
New Revision: 93787
Removed:
projects/docs/enterprise/5.0/Release_Notes/
Modified:
projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/en-US/Configuration.xml
projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/en-US/Introduction.xml
projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/en-US/Running_Examples.xml
Log:
Beta2 checkin.
Modified: projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/en-US/Configuration.xml
===================================================================
--- projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/en-US/Configuration.xml 2009-09-20 02:24:50 UTC (rev 93786)
+++ projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/en-US/Configuration.xml 2009-09-20 23:44:40 UTC (rev 93787)
@@ -470,7 +470,7 @@
</para>
<para>
- Example configuration files for MySQL, Oracle, PostgreSQL, Microsoft SQL Server or Sybase databases are available in the <filename>examples/config</filename> directory of the release bundle.
+ Example configuration files for MySQL, Oracle, PostgreSQL, Microsoft SQL Server or Sybase databases are available in the <filename>jboss-as/docs/examples/jms</filename> directory of the release bundle.
</para>
<para>
@@ -808,7 +808,7 @@
</warning>
<para>
- JBoss Messaging also ships with Persistence Manager configurations for MySQL, Oracle, PostgreSQL, Sybase, Microsoft SQL Server, and DB2. The example configuration files (<filename>mysql-persistence-service.xml</filename>, <filename>ndb-persistence-service.xml</filename>, etc.) are available from the <filename>examples/config</filename> directory of the release bundle.
+ JBoss Messaging also ships with Persistence Manager configurations for MySQL, Oracle, PostgreSQL, Sybase, Microsoft SQL Server, and DB2. The example configuration files (<filename>mysql-persistence-service.xml</filename>, <filename>ndb-persistence-service.xml</filename>, etc.) are available from the <filename>jboss-as/docs/examples/jms</filename> directory of the release bundle.
</para>
<para>
Modified: projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/en-US/Introduction.xml
===================================================================
--- projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/en-US/Introduction.xml 2009-09-20 02:24:50 UTC (rev 93786)
+++ projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/en-US/Introduction.xml 2009-09-20 23:44:40 UTC (rev 93787)
@@ -21,29 +21,29 @@
<section id="features">
<title>JBoss Messaging Features</title>
- <para>JBoss Messaging provides:</para>
+ <para>JBoss Messaging provides the following features:</para>
<itemizedlist>
<listitem>
<para>
- a Sun-certified implementation of Java Messaging Service 1.1, which currently works with the standard installation of JBoss Enterprise Application Platform version 4.2 or later.
+ A Sun-certified implementation of Java Messaging Service 1.1, which currently works with the standard installation of JBoss Enterprise Application Platform version 4.2 or later.
</para>
</listitem>
<listitem>
<para>
- a strong focus on performance, reliability and scalability with high throughput and low latency.
+ A strong focus on performance, reliability and scalability with high throughput and low latency.
</para>
</listitem>
<listitem>
<para>
- a foundation for JBoss ESB for SOA initiatives. (JBoss ESB uses JBoss Messaging as its default JMS provider.)
+ A foundation for JBoss ESB for SOA initiatives. (JBoss ESB uses JBoss Messaging as its default JMS provider.)
</para>
</listitem>
</itemizedlist>
- <para>JBoss Messaging also includes the following features:</para>
+ <para>JBoss Messaging also includes:</para>
<itemizedlist>
<listitem>
@@ -181,7 +181,7 @@
<title>Compatibility with JBoss MQ</title>
<para>
- JBoss MQ is the JMS implementation currently shipped with JBoss Application Server. Since JBoss Messaging is compatible with both JMS 1.1 and JMS 1.0.2b, the JMS code written against JBoss MQ will run with JBoss Messaging without any further changes.
+ JBoss MQ was the JMS implementation shipped with Enterprise Application Platform 4.2. Since JBoss Messaging is compatible with both JMS 1.1 and JMS 1.0.2b, the JMS code written against JBoss MQ will run with JBoss Messaging without any further changes.
</para>
<para>
@@ -194,4 +194,4 @@
</para>
</important>
</section>
-</chapter>
\ No newline at end of file
+</chapter>
Modified: projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/en-US/Running_Examples.xml
===================================================================
--- projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/en-US/Running_Examples.xml 2009-09-20 02:24:50 UTC (rev 93786)
+++ projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/en-US/Running_Examples.xml 2009-09-20 23:44:40 UTC (rev 93787)
@@ -3,11 +3,11 @@
<title>Running the Examples</title>
<para>
- The <filename>docs/examples</filename> directory contains a set of examples that demonstrate the various aspects of JBoss Messaging at work.
+ The <filename>/docs/examples/jms</filename> directory contains a set of examples that demonstrate the various aspects of JBoss Messaging at work.
</para>
<para>
- Before you run these examples, deploy the <literal>example-destinations</literal> located under <filename>/docs/examples/destinations</filename>.
+ Before you run these examples, deploy the <literal>example-destinations</literal> located under <filename>/docs/examples/jms/destinations</filename>.
</para>
<para>
@@ -16,7 +16,7 @@
<variablelist>
<varlistentry>
- <term><filename>docs/example/queue</filename></term>
+ <term><filename>docs/examples/jms/queue</filename></term>
<listitem>
<para>
This example shows a simple send and receive to a remote queue using a JMS client.
@@ -24,7 +24,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><filename>docs/example/topic</filename></term>
+ <term><filename>docs/examples/jms/topic</filename></term>
<listitem>
<para>
This example shows a simple send and receive to a remote topic using a JMS client.
@@ -32,7 +32,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><filename>docs/example/mdb</filename></term>
+ <term><filename>docs/examples/jms/mdb</filename></term>
<listitem>
<para>
This example demonstrates the use of an Enterprise JavaBean 2.1 MDB with JBoss Messaging.
@@ -40,7 +40,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><filename>docs/example/ejb3mdb</filename></term>
+ <term><filename>docs/examples/jms/ejb3mdb</filename></term>
<listitem>
<para>
This example demonstrates the use of an Enterprise JavaBean 3.0 MDB with JBoss Messaging.
@@ -48,7 +48,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><filename>docs/example/stateless</filename></term>
+ <term><filename>docs/examples/jms/stateless</filename></term>
<listitem>
<para>
This example demonstrates an Enterprise JavaBean 2.1 stateless session bean interacting with JBoss Messaging.
@@ -56,7 +56,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><filename>docs/example/mdb-failure</filename></term>
+ <term><filename>docs/examples/jms/mdb-failure</filename></term>
<listitem>
<para>
This example demonstrates rollback and redelivery within an Enterprise JavaBean 2.1.
@@ -64,7 +64,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><filename>docs/example/secure-socket</filename></term>
+ <term><filename>docs/examples/jms/secure-socket</filename></term>
<listitem>
<para>
This example demonstrates a JMS client interacting with a JBoss Messaging server via SSL-encrypted transport.
@@ -72,7 +72,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><filename>docs/example/http</filename></term>
+ <term><filename>docs/examples/jms/http</filename></term>
<listitem>
<para>
This example demonstrates a JMS client interacting with a JBoss Messaging server by tunneling traffic via HTTP.
@@ -80,7 +80,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><filename>docs/example/web-service</filename></term>
+ <term><filename>docs/examples/jms/web-service</filename></term>
<listitem>
<para>
This example demonstrates the JBoss Webservice interacting with JBoss Messaging.
@@ -88,7 +88,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><filename>docs/example/distributed-queue</filename></term>
+ <term><filename>docs/examples/jms/distributed-queue</filename></term>
<listitem>
<para>
This example demonstrates a JMS client interacting with a JBoss Messaging distributed queue. Two instances of JBoss AS are required to run this example.
@@ -96,7 +96,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><filename>docs/example/distributed-topic</filename></term>
+ <term><filename>docs/examples/jms/distributed-topic</filename></term>
<listitem>
<para>
This example demonstrates a JMS client interacting with a JBoss Messaging distributed topic. Two instances of JBoss AS are required to run this example.
@@ -104,7 +104,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><filename>docs/example/stateless-clustered</filename></term>
+ <term><filename>docs/examples/jms/stateless-clustered</filename></term>
<listitem>
<para>
This example demonstrates a JMS client interacting with a clustered Enterprise JavaBean 2.1 stateless session bean, which interacts in turn with JBoss Messaging. This example uses HAJNDI to locate the connection factory.
@@ -112,7 +112,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><filename>docs/example/bridge</filename></term>
+ <term><filename>docs/examples/jms/bridge</filename></term>
<listitem>
<para>
This example demonstrates the use of a message bridge. It deploys a message bridge within JBoss AS, which moves messages from a source to a target queue.
@@ -123,7 +123,7 @@
<para>We highly recommend that you familiarize yourself with the examples.</para>
- <para>Remember: you must start your server or servers before you run the examples.</para>
+ <important><para>Remember that you must start your server or servers before you run the examples.</para></important>
<para>
The non-clustered examples expect an instance of JBoss AS to be running with all default settings.
More information about the jboss-cvs-commits
mailing list