[jboss-cvs] JBossAS SVN: r75815 - projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Jul 14 22:19:37 EDT 2008
Author: irooskov at redhat.com
Date: 2008-07-14 22:19:37 -0400 (Mon, 14 Jul 2008)
New Revision: 75815
Modified:
projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US/Important_Features.xml
projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US/bridge.xml
projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US/configuration.xml
projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US/introduction.xml
projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US/recoveryconfig.xml
projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US/runningexamples.xml
Log:
correctly changed JBoss AS appearances to JBoss EAP where appropriate. In response to JBPAPP-980 - though this does not close this JIRA
Modified: projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US/Important_Features.xml
===================================================================
--- projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US/Important_Features.xml 2008-07-15 01:59:44 UTC (rev 75814)
+++ projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US/Important_Features.xml 2008-07-15 02:19:37 UTC (rev 75815)
@@ -29,7 +29,7 @@
</para>
<note>
<para>
- <emphasis>JMS compliance</emphasis>: A fully compatible and Sun certified JMS 1.1 implementation, that currently works with JBoss Enterprise Application Platform 4.3 or JBoss Application Server version 4.2 or later.
+ <emphasis>JMS compliance</emphasis>: A fully compatible and Sun certified JMS 1.1 implementation, that currently works with JBoss Enterprise Application Platform 4.3 or later.
</para>
</note>
<para>
Modified: projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US/bridge.xml
===================================================================
--- projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US/bridge.xml 2008-07-15 01:59:44 UTC (rev 75814)
+++ projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US/bridge.xml 2008-07-15 02:19:37 UTC (rev 75815)
@@ -11,14 +11,14 @@
cluster which makes bridging suitable for reliably sending messages from
one cluster to another, for instance across a WAN, and where the
connection may be unreliable.</para>
- <para>A bridge is deployed inside a JBoss AS instance. The instance can
+ <para>A bridge is deployed inside a JBoss EAP instance. The instance can
be the same instance as either the source or target server. Or could be
- on a third, separate JBoss AS instance.</para>
- <para>A bridge is deployed as an MBean inside JBoss AS. Deployment is
+ on a third, separate JBoss EAP instance.</para>
+ <para>A bridge is deployed as an MBean inside JBoss EAP. Deployment is
trivial - just drop the MBean descriptor into the deploy directory of a
JBoss configuration which contains JBoss Messaging.</para>
<para>An example in docs/example/bridge demonstrates a simple bridge
- being deployed in JBoss AS, and moving messages from the source to the
+ being deployed in JBoss EAP, and moving messages from the source to the
target destination</para>
<para>The bridge can also be used to bridge messages from other non
JBoss Messaging JMS servers, as long as they are JMS 1.1
@@ -87,7 +87,7 @@
<section id="bridge.deployment">
<title>Bridge deployment</title>
<para>A message bridge is easily deployed by dropping the MBean
- descriptor in the deploy directory of your JBoss AS installation which
+ descriptor in the deploy directory of your JBoss EAP installation which
contains JBoss Messaging</para>
</section>
<section id="bridge.configuration">
@@ -181,7 +181,7 @@
<para>This is the object name of the JMSProviderLoader MBean that the
bridge will use to lookup the source connection factory and source
destination.</para>
- <para>By default JBoss AS ships with one JMSProviderLoader, deployed
+ <para>By default JBoss EAP ships with one JMSProviderLoader, deployed
in the file <filename>jms-ds.xml</filename> - this is the default
local JMSProviderLoader. (This would be in
<filename>hajndi-jms-ds.xml</filename> in a clustered
@@ -203,9 +203,9 @@
<para>This is the object name of the JMSProviderLoader MBean that the
bridge will use to lookup the target connection factory and target
destination.</para>
- <para>By default JBoss AS ships with one JMSProviderLoader, deployed
+ <para>By default JBoss EAP ships with one JMSProviderLoader, deployed
in the file <filename>jms-ds.xml</filename> - this is the default
- local JMSProviderLoader. (This would be in
+ local JMSProviderLoader. JBoss EAP(This would be in
<filename>hajndi-jms-ds.xml</filename> in a clustered
configuration)</para>
<para>If your target destination is on a different server or even
Modified: projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US/configuration.xml
===================================================================
--- projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US/configuration.xml 2008-07-15 01:59:44 UTC (rev 75814)
+++ projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US/configuration.xml 2008-07-15 02:19:37 UTC (rev 75815)
@@ -800,7 +800,7 @@
corresponds to the database name. By default, Messaging ships with a
<filename>hsqldb-persistence-service.xml</filename>, which configures
the Messaging server to use the in-VM Hypersonic database instance that
- comes by default with any JBossAS instance.</para>
+ comes by default with any EAP instance.</para>
<warning>
<para>The default persistence manager works out of the box with Hypersonic. However, it must be stressed that Hypersonic should not be used in a production environment, mainly due to its limited support for transaction isolation, and its propensity to behave erratically under high load.</para>
<para>The <ulink
@@ -2001,7 +2001,7 @@
<!-- end conf.connector -->
<section id="conf.servicebindingmanager">
<title>ServiceBindingManager</title>
- <para>If you are using the JBoss AS ServiceBindingManager to provide
+ <para>If you are using the JBoss EAP ServiceBindingManager to provide
different servers with different port ranges, then you must make sure
that the JBoss Messaging remoting configuration specified in the JBoss
Messaging section of the ServiceBindingManager xml file exactly matches
Modified: projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US/introduction.xml
===================================================================
--- projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US/introduction.xml 2008-07-15 01:59:44 UTC (rev 75814)
+++ projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US/introduction.xml 2008-07-15 02:19:37 UTC (rev 75815)
@@ -31,8 +31,8 @@
<itemizedlist>
<listitem>
<para>A fully compatible and Sun certified JMS 1.1 implementation,
- that currently works with a standard 4.2 or later JBoss
- Application Server installation.</para>
+ that currently works with a standard 4.3 or later JBoss
+ Application Platform installation.</para>
</listitem>
<listitem>
@@ -180,7 +180,7 @@
<title>Compatibility with JBossMQ</title>
<para>JBoss MQ is the JMS implementation currently shipped within JBoss
- AS. Since JBoss Messaging is JMS 1.1 and JMS 1.0.2b compatible, the JMS
+ EAP 4.2. Since JBoss Messaging is JMS 1.1 and JMS 1.0.2b compatible, the JMS
code written against JBossMQ will run with JBoss Messaging without any
changes.</para>
Modified: projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US/recoveryconfig.xml
===================================================================
--- projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US/recoveryconfig.xml 2008-07-15 01:59:44 UTC (rev 75814)
+++ projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US/recoveryconfig.xml 2008-07-15 02:19:37 UTC (rev 75815)
@@ -2,7 +2,7 @@
<chapter id="recovery">
<title>JBoss Messaging XA Recovery Configuration</title>
<para>This section describes how to configure JBoss Transactions in JBoss
- AS 4.2.0 to handle XA recovery for JBoss Messaging resources.</para>
+ EAP to handle XA recovery for JBoss Messaging resources.</para>
<para>JBoss Transactions recovery manager can easily be configured to
continually poll for and recover JBoss Messaging XA resources, this
provides an extremely high level of durability of transactions.</para>
@@ -34,7 +34,7 @@
<para>In the above example the recovery manager will attempt to recover JMS
resources using the JMSProviderLoader "DefaultJMSProvider"</para>
<para>DefaultJMSProvider is the default JMS provider loader that ships with
- JBoss AS and is defined in jms-ds.xml (or hajndi-jms-ds.xml in a clustered
+ JBoss EAP and is defined in jms-ds.xml (or hajndi-jms-ds.xml in a clustered
configuration). If you want to recovery using a different JMS provider
loader - e.g. one corresponding to a remote JMS provider then just add
another line and instead of DefaultJMSProvider specify the name of the
Modified: projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US/runningexamples.xml
===================================================================
--- projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US/runningexamples.xml 2008-07-15 01:59:44 UTC (rev 75814)
+++ projects/docs/enterprise/4.3.2/Messaging/JBoss_Messaging_User_Guide/en-US/runningexamples.xml 2008-07-15 02:19:37 UTC (rev 75815)
@@ -72,7 +72,7 @@
<para>docs/example/distributed-queue</para>
<para>This example demonstrates a JMS client interacting with a JBoss
- Messaging distributed queue - it requires two JBoss AS instances to be
+ Messaging distributed queue - it requires two JBoss EAP instances to be
running</para>
</listitem>
@@ -80,7 +80,7 @@
<para>docs/example/distributed-topic</para>
<para>This example demonstrates a JMS client interacting with a JBoss
- Messaging distributed topic - it requires two JBoss AS instances to be
+ Messaging distributed topic - it requires two JBoss EAP instances to be
running</para>
</listitem>
@@ -97,7 +97,7 @@
<para>docs/example/bridge</para>
<para>This example demonstrates using a message bridge. It deploys a
- message bridge in JBoss AS which then proceeds to move messages from a
+ message bridge in JBoss EAP which then proceeds to move messages from a
source to a target queue</para>
</listitem>
</itemizedlist></para>
@@ -108,10 +108,10 @@
<para>Make sure you start the JBoss server(s) before running the
examples!</para>
- <para>The non clustered examples expect a JBoss AS instance to be running
+ <para>The non clustered examples expect a JBoss EAP instance to be running
with all the default settings</para>
- <para>The clustered examples expect two JBoss AS instances to running with
+ <para>The clustered examples expect two JBoss EAP instances to running with
ports settings as per ports-01 and ports-02.</para>
<para>For each example, you can always override the default ports it will
More information about the jboss-cvs-commits
mailing list