[jboss-cvs] JBoss Messaging SVN: r7948 - projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US.

[jboss-cvs-commits at lists.jboss.org]

Author: laubai
Date: 2010-02-17 02:22:01 -0500 (Wed, 17 Feb 2010)
New Revision: 7948

Modified:
   projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/Architecture.xml
Log:
Partially corrected Architecture chapter.

Modified: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/Architecture.xml
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/Architecture.xml	2010-02-16 06:25:41 UTC (rev 7947)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/Architecture.xml	2010-02-17 07:22:01 UTC (rev 7948)
@@ -8,33 +8,32 @@
     <section>
         <title>Core Architecture</title>
         <para>JBoss Messaging core is designed simply as set of Plain Old Java Objects
-            (<acronym>POJO</acronym>s).</para>
-        <para>We have also designed it to have as few dependencies on external jars as possible. In
-            fact, JBoss Messaging core has <emphasis role="italic">zero</emphasis> dependencies on
-            any jars other than the standard JDK classes!</para>
-        <para>This allows JBoss Messaging to be easily embedded in your own project, or instantiated
-            in any dependency injection framework such as JBoss Microcontainer, Spring or Google
-            Guice.</para>
+            (<acronym>POJO</acronym>s). It has also been designed to have zero dependencies
+            on external JARs other than the JDK classes. This allows JBoss Messaging to be 
+            easily embedded in your own project, or instantiated
+            in any dependency injection framework such as JBoss Microcontainer or Spring.</para>
         <para>A JBoss Messaging server has its own high performance persistent journal, which it
-            uses for message and other persistence.</para>
-        <para>Using a high performance journal allows exceptional persistence message performance,
-            something not achievable when using a relational database for persistence.</para>
-        <para>JBoss Messaging clients, potentially on different physical machines, interact with the
-            JBoss Messaging server. JBoss Messaging currently provides two APIs for messaging at the
+            uses for message and other persistence. Using a high performance journal allows 
+            exceptional persistence message performance. This is not possible when using
+            a relational database for persistence.</para>
+        <para>JBoss Messaging clients, which can be on separate physical machines, interact with the
+            JBoss Messaging server. JBoss Messaging currently provides two APIs for messaging on the
             client side:</para>
-        <para>
-            <orderedlist>
-                <listitem>
-                    <para>Core client API. This is a simple intuitive Java API that allows the full
-                        set of messaging functionality without some of the complexities of
-                        JMS.</para>
-                </listitem>
-                <listitem>
-                    <para>JMS client API. The standard JMS API is available at the client
-                        side.</para>
-                </listitem>
-            </orderedlist>
-        </para>
+
+        <variablelist>
+          <varlistentry>
+            <term>Core client API</term>
+            <listitem><para>A simple, intuitive Java API that allows the full set of messaging
+                    functionality without some of the complexities of the Java Message Service.</para></listitem>
+          </varlistentry>
+          <varlistentry>
+            <term>JMS client API</term>
+            <listitem><para>The standard Java Message Service API.</para></listitem>
+          </varlistentry>
+        </variablelist>
+
+        <!--hajime-->
+
         <para>JMS semantics are implemented by a thin JMS facade layer on the client side.</para>
         <para>The JBoss Messaging server does not speak JMS and in fact does not know anything about
             JMS, it is a protocol agnostic messaging server designed to be used with multiple