[jboss-cvs] JBoss Messaging SVN: r7949 - projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Feb 18 02:48:59 EST 2010
Author: laubai
Date: 2010-02-18 02:48:59 -0500 (Thu, 18 Feb 2010)
New Revision: 7949
Modified:
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/Architecture.xml
Log:
Partial edit of Architecture.xml.
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-17 07:22:01 UTC (rev 7948)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/Architecture.xml 2010-02-18 07:48:59 UTC (rev 7949)
@@ -24,58 +24,58 @@
<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>
+ functionality without some of the complexities of the Java Message Service (JMS).</para></listitem>
</varlistentry>
<varlistentry>
<term>JMS client API</term>
- <listitem><para>The standard Java Message Service API.</para></listitem>
+ <listitem><para>The standard JMS 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
- different protocols.</para>
+ <para>JMS semantics are implemented by a thin JMS facade layer on the client side. JBoss Messaging
+ itself is not bound to any particular protocol.</para>
<para>When a user uses the JMS API on the client side, all JMS interactions are translated
- into operations on the JBoss Messaging core client API before being transferred over the
- wire using the JBoss Messaging wire format.</para>
- <para>The server simply deals with core API interactions.</para>
- <para>A schematic illustrating this relationship is shown in figure 3.1 below:</para>
+ into operations on the JBoss Messaging core client API before being transferred to the server
+ in the JBoss Messaging wire format. The server itself deals only with core API interactions.</para>
+ <figure id="fig-arch1"><title>Server-client interaction in JBoss Messaging</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/architecture1.png">
+ </imageobject>
+ </mediaobject>
+ </figure>
<para>
- <graphic fileref="images/architecture1.png" align="center"/>
+ <xref linkend="fig-arch1"/> shows two applications interacting with a JBoss Messaging server.
+ User Application 1 is using the JMS API. User Application 2 is using the core client API
+ directly. You can see in the diagram that the JMS API is implemented by a thin facade layer
+ on the client side.
</para>
- <para>Figure 3.1 shows two user applications interacting with a JBoss Messaging server. User
- Application 1 is using the JMS API, while User Application 2 is using the core client
- API directly.</para>
- <para>You can see from the diagram that the JMS API is implemented by a thin facade layer on
- the client side.</para>
</section>
+
<section>
- <title>JBoss Messaging Embedded In Your Own Application</title>
- <para>JBoss Messaging core is designed as a set of simple POJOs so if you have an
- application that requires messaging functionality internally but you do not want to
- expose that as a messaging server you can directly instantiate and embed messaging
- servers in your own application.</para>
+ <title>Embedding JBoss Messaging in your application</title>
+ <para>JBoss Messaging core is designed as a set of simple POJOs. If your application requires
+ messaging functionality internally, but you do not want to expose it as a messaging server,
+ you can directly instantiate and embed messaging servers in your own application.</para>
<para>For more information on embedding JBoss Messaging, see <xref
linkend="embedding-jbm" />.</para>
</section>
+
<section>
- <title>JBoss Messaging Integrated With a JEE Application Server</title>
- <para>JBoss Messaging provides its own fully functional Java Connector Architecture (<acronym>JCA</acronym>)
- adaptor which enables it to be integrated easily into any JEE compliant application
+ <title>Integrating JBoss Messaging with a Java EE Application Server</title>
+ <para>JBoss Messaging provides its own fully-functional Java Connector Architecture (<acronym>JCA</acronym>)
+ adaptor which enables it to be integrated easily into any Java EE (JEE) compliant application
server or servlet engine.</para>
- <para>JEE application servers provide Message Driven Beans (<acronym>MDB</acronym>s), which are a special type
- of Enterprise Java Beans (<acronym>EJB</acronym>s) that can process messages from sources such as JMS
+ <para>JEE application servers provide Message Driven Beans (<acronym>MDB</acronym>s), a special type
+ of Enterprise Java Bean (<acronym>EJB</acronym>) that can process messages from sources such as JMS
systems or mail systems.</para>
<para>Probably the most common use of an MDB is to consume messages from a JMS messaging
system.</para>
<para>According to the JEE specification, a JEE application server uses a JCA adapter to
integrate with a JMS messaging system so it can consume messages for MDBs.</para>
- <para>However, the JCA adapter is not only used by the JEE application server for <emphasis
- role="italic">consuming</emphasis> messages via MDBs, it is also used when sending
- messages to the JMS messaging system, e.g. from inside an EJB or servlet.</para>
+ <para>However, the JCA adapter is not only used by the JEE application server for
+ <emphasis>consuming</emphasis> messages via MDBs. It is also used when sending
+ messages to the JMS messaging system, for example, from inside an EJB or servlet.</para>
<para>When integrating with a JMS messaging system from inside a JEE application server it
is always recommended that this is done via a JCA adaptor.</para>
<para>The application server's JCA service provides extra functionality such as connection
More information about the jboss-cvs-commits
mailing list