[jboss-cvs] JBoss Messaging SVN: r7952 - in projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ: HornetQ_User_Guide and 1 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Feb 22 02:00:00 EST 2010
Author: laubai
Date: 2010-02-22 01:59:59 -0500 (Mon, 22 Feb 2010)
New Revision: 7952
Added:
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_User_Guide/Makefile
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_User_Guide/en-US/
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_User_Guide/publican.cfg
Removed:
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/Makefile
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/publican.cfg
Modified:
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_User_Guide/en-US/AS_Integration.xml
projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_User_Guide/en-US/Architecture.xml
Log:
Moved User Guide files to a User Guide subdirectory.
Copied: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_User_Guide/Makefile (from rev 7951, projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/Makefile)
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_User_Guide/Makefile (rev 0)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_User_Guide/Makefile 2010-02-22 06:59:59 UTC (rev 7952)
@@ -0,0 +1,13 @@
+#Makefile for JBoss_Messaging_User_Guide
+
+XML_LANG = en-US
+BRAND = JBoss
+
+#OTHER_LANGS = as-IN bn-IN de-DE es-ES fr-FR gu-IN hi-IN it-IT ja-JP kn-IN ko-KR ml-IN mr-IN or-IN pa-IN pt-BR ru-RU si-LK ta-IN te-IN zh-CN zh-TW
+
+# Extra Parameters start here
+
+# Extra Parameters stop here
+COMMON_CONFIG = /usr/share/publican
+include $(COMMON_CONFIG)/make/Makefile.common
+
Copied: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_User_Guide/en-US (from rev 7951, projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US)
Modified: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_User_Guide/en-US/AS_Integration.xml
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/AS_Integration.xml 2010-02-22 06:57:23 UTC (rev 7951)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_User_Guide/en-US/AS_Integration.xml 2010-02-22 06:59:59 UTC (rev 7952)
@@ -1,33 +1,34 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="appserver-integration">
<title>Application Server Integration and Java EE</title>
- <para>JBoss Messaging can be easily installed in JBoss Application Server 5.1 or later. For
+ <para>Refer to the <citetitle>JBoss Messaging Quick Start Guide</citetitle> for details on
+ installing JBoss Messaging 2.0.</para>
+<!-- <para>JBoss Messaging can be easily installed in JBoss Application Server 5.1 or later. For
details on installing JBoss Messaging in the JBoss Application Server refer to quick-start
- guide.</para>
- <para>Since JBoss Messaging also provides a JCA adaptor, it should also be possible to integrate
- JBoss Messaging as a JMS provider in other JEE compliant app servers. For instructions on
+ guide.</para>-->
+ <!--<para>Since JBoss Messaging also provides a JCA adaptor, it should also be possible to integrate
+ JBoss Messaging as a JMS provider into other JEE compliant application servers. For instructions on
how to integrate a remote JCA adaptor into another application sever, please consult that
- application server's instructions.</para>
- <para>A JCA Adapter basically controls the incoming of messages to Message Driven Beans and the
- outgoing of messages from other JEE components.</para>
- <para>This section explains the basics behind configuring the different JEE components in the
- AS.</para>
+ application server's instructions.</para>-->
+ <!--<para>A JCA Adapter controls the incoming of messages to Message Driven Beans and the
+ outgoing of messages from other JEE components.</para>-->
+ <para>Read this chapter to learn how to configure some common Java EE components for use with
+ JBoss Messaging.</para>
<section>
<title>Configuring Message Driven Beans</title>
<para>The delivery of messages to an MDB using JBoss Messaging is configured on the JCA
- Adapter via a configuration file <literal>ra.xml</literal> which can be found under in
- the <literal>jms-ra.rar</literal> archive of directory. By default this is configured to
+ Adapter via a configuration file, <filename>ra.xml</filename> which can be found in
+ the <filename>jms-ra.rar</filename> archive of directory. By default this is configured to
consume messages using an InVM connector from the instance of JBoss Messaging running
within the application server. A full list of what is configurable is found later in
- this chapter. </para>
+ this chapter.</para>
<para>All MDB's however need to have the destination type and the destination configured.
The following example shows how this can be done via annotations.</para>
<programlisting>@MessageDriven(name = "MDBExample",
- activationConfig =
- {
- @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
- @ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/testQueue")
- })
+ activationConfig = {
+ @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
+ @ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/testQueue")
+ })
public class MDBExample implements MessageListener
{
public void onMessage(Message message)...
Modified: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_User_Guide/en-US/Architecture.xml
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/en-US/Architecture.xml 2010-02-22 06:57:23 UTC (rev 7951)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_User_Guide/en-US/Architecture.xml 2010-02-22 06:59:59 UTC (rev 7952)
@@ -40,7 +40,7 @@
<figure id="fig-arch1"><title>Server-client interaction in JBoss Messaging</title>
<mediaobject>
<imageobject>
- <imagedata fileref="images/architecture1.png">
+ <imagedata fileref="images/architecture1.png"/>
</imageobject>
</mediaobject>
</figure>
@@ -63,9 +63,9 @@
<section>
<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>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), a special type
of Enterprise Java Bean (<acronym>EJB</acronym>) that can process messages from sources such as JMS
systems or mail systems.</para>
@@ -84,7 +84,7 @@
an EJB, MDB or servlet without going through a JCA adapter, but this is not recommended
since you will not be able to take advantage of the JCA features, such as caching of JMS
sessions, which can result in poor performance.</para>
- <para>Figure 3.2 below shows a JEE application server integrating with a JBoss Messaging
+ <para><xref linkend="fig-arch2"/> shows a JEE application server integrating with a JBoss Messaging
server via the JBoss Messaging JCA adaptor. Note that all communication between EJB
sessions or entity beans and Message Driven beans go through the adaptor and not
directly to JBoss Messaging.</para>
@@ -92,25 +92,29 @@
the JBoss Messaging server. This is not recommended as you will most likely end up
creating a new connection and session every time you want to interact from the EJB,
which is an anti-pattern.</para>
- <para>
- <graphic fileref="images/architecture2.png"/>
- </para>
+ <figure id="fig-arch2"><title>Java EE integration with JBoss Messaging JCA adaptor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/architecture2.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
<para>For more information on using the JCA adaptor, please see <xref
linkend="appserver-integration" />.</para>
</section>
<section>
<title>JBoss Messaging Stand-Alone Server</title>
- <para>JBoss Messaging can also be deployed as a stand-alone server. This means a fully
- independent messaging server not dependent on a JEE application server.</para>
+ <para>JBoss Messaging can also be deployed as a stand-alone server; a completely
+ independent messaging server not dependent on a Java EE application server.</para>
<para>The standard stand-alone messaging server configuration comprises a core messaging
server, a JMS service and a JNDI service.</para>
- <para>The role of the JMS Service is to deploy any JMS Queues, Topics and ConnectionFactory
- instances from any server side <literal>jbm-jms.xml</literal> configuration files. It also
- provides a simple management API for creating and destroying Queues, Topics and
+ <para>The role of the JMS Service is to deploy any JMS Queue, Topic or ConnectionFactory
+ instances from any server side <filename>jbm-jms.xml</filename> configuration files. It also
+ provides a simple management API for creating and destroying Queue, Topic and
ConnectionFactory instances which can be accessed via JMX or the connection. It is a
separate service to the JBoss Messaging core server, since the core server is JMS
- agnostic. If you do not want to deploy any JMS Queues, Topics and ConnectionFactory
- instances via server side XML configuration and do not require a JMS management API on the
+ agnostic. If you do not want to deploy any JMS Queue, Topic or ConnectionFactory
+ instances via server-side XML configuration and do not require a JMS management API on the
server side then you can disable this service.</para>
<para>We also include a JNDI server as JNDI is a common requirement when using JMS to
lookup Queues, Topics and ConnectionFactory instances. If you do not require JNDI then
@@ -120,11 +124,15 @@
<para>The stand-alone server configuration uses JBoss Microcontainer to instantiate and
enforce dependencies between the components. JBoss Microcontainer is a very lightweight
POJO bootstrapper.</para>
- <para>The stand-alone server architecture is shown in figure 3.3 below:</para>
- <para>
- <graphic fileref="images/architecture3.png"/>
- </para>
- <para>For more information on server configuration files see <xref linkend="server.configuration" />.
+ <para>The stand-alone server architecture is shown in <xref linkend="fig-arch3"/>:</para>
+ <figure id="fig-arch3"><title>Stand-alone server architecture</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/architecture3.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>For more information on server configuration files see <xref linkend="server.configuration"/>.
$ </para>
</section>
</chapter>
Copied: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_User_Guide/publican.cfg (from rev 7951, projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/publican.cfg)
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_User_Guide/publican.cfg (rev 0)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/HornetQ_User_Guide/publican.cfg 2010-02-22 06:59:59 UTC (rev 7952)
@@ -0,0 +1,7 @@
+# Config::Simple 4.59
+# Tue Feb 16 15:48:57 2010
+
+debug: 1
+xml_lang: en-US
+brand: JBoss
+
Deleted: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/Makefile
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/Makefile 2010-02-22 06:57:23 UTC (rev 7951)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/Makefile 2010-02-22 06:59:59 UTC (rev 7952)
@@ -1,13 +0,0 @@
-#Makefile for JBoss_Messaging_User_Guide
-
-XML_LANG = en-US
-BRAND = JBoss
-
-#OTHER_LANGS = as-IN bn-IN de-DE es-ES fr-FR gu-IN hi-IN it-IT ja-JP kn-IN ko-KR ml-IN mr-IN or-IN pa-IN pt-BR ru-RU si-LK ta-IN te-IN zh-CN zh-TW
-
-# Extra Parameters start here
-
-# Extra Parameters stop here
-COMMON_CONFIG = /usr/share/publican
-include $(COMMON_CONFIG)/make/Makefile.common
-
Deleted: projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/publican.cfg
===================================================================
--- projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/publican.cfg 2010-02-22 06:57:23 UTC (rev 7951)
+++ projects/eap-docs/tags/JBoss_Messaging_User_Guide_EAP_5_0_1/HornetQ/publican.cfg 2010-02-22 06:59:59 UTC (rev 7952)
@@ -1,7 +0,0 @@
-# Config::Simple 4.59
-# Tue Feb 16 15:48:57 2010
-
-debug: 1
-xml_lang: en-US
-brand: JBoss
-
More information about the jboss-cvs-commits
mailing list