[jboss-cvs] JBossAS SVN: r94664 - projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Oct 12 03:10:40 EDT 2009
Author: benlc
Date: 2009-10-12 03:10:40 -0400 (Mon, 12 Oct 2009)
New Revision: 94664
Modified:
projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/en-US/Bridge.xml
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/JBoss_Messaging_User_Guide.xml
projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/en-US/Running_Examples.xml
Log:
'committing changes as per JBPAPP-2472'
Modified: projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/en-US/Bridge.xml
===================================================================
--- projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/en-US/Bridge.xml 2009-10-12 07:09:01 UTC (rev 94663)
+++ projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/en-US/Bridge.xml 2009-10-12 07:10:40 UTC (rev 94664)
@@ -18,7 +18,7 @@
</para>
<para>
- The example in <filename>docs/example/bridge</filename> demonstrates a simple bridge deployed in JBoss Application Server and moving messages from the source to the target destination.
+ The example in <filename>/doc/examples/jboss-messaging-examples/bridge/</filename> demonstrates a simple bridge deployed in JBoss Application Server and moving messages from the source to the target destination.
</para>
<para>
@@ -59,7 +59,7 @@
</listitem>
<listitem>
- <para>QOS_ONCE_AND_ONLY_ONCE</para>
+ <para><literal>QOS_ONCE_AND_ONLY_ONCE</literal></para>
<para>
This mode specifies that messages will arrive exactly once. When the message source and destination are on the same JBoss Messaging server instance, the message can be sent and received in the same local transaction. If the source and destination are on different servers, you can enlist the sending and consuming sessions in a JTA transaction controlled by JBoss Transactions JTA implementation, which provides high durability. If JTA is required, both connection factories must be <literal>XAConnectionFactory</literal> implementations.
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-10-12 07:09:01 UTC (rev 94663)
+++ projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/en-US/Configuration.xml 2009-10-12 07:10:40 UTC (rev 94664)
@@ -1947,7 +1947,7 @@
</para>
<para>
- Remoting configuration details can be seen in <filename>$JBOSS_HOME/server/$SERVER/deploy/jboss-messaging.sar/remoting-bisocket-service.xml</filename>. The following code is an example of a bisocket remoting configuration:
+ Remoting configuration details can be seen in <filename>$JBOSS_HOME/server/$SERVER/deploy/jboss-messaging/remoting-bisocket-service.xml</filename>. The following code is an example of a bisocket remoting configuration:
</para>
<programlisting>
<config>
Modified: projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/en-US/JBoss_Messaging_User_Guide.xml
===================================================================
--- projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/en-US/JBoss_Messaging_User_Guide.xml 2009-10-12 07:09:01 UTC (rev 94663)
+++ projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/en-US/JBoss_Messaging_User_Guide.xml 2009-10-12 07:10:40 UTC (rev 94664)
@@ -11,9 +11,9 @@
<xi:include href="Running_Examples.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="C_Configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Recovery_Configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <!-- Chapter below commented out as applicable to EAP4.3 and not EAP5.0 -->
+ <!-- <xi:include href="Recovery_Configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
<xi:include href="Bridge.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <index />
</book>
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-10-12 07:09:01 UTC (rev 94663)
+++ projects/docs/enterprise/5.0/JBoss_Messaging_1.4.3/en-US/Running_Examples.xml 2009-10-12 07:10:40 UTC (rev 94664)
@@ -3,11 +3,11 @@
<title>Running the Examples</title>
<para>
- The <filename>/docs/examples/jms</filename> directory contains a set of examples that demonstrate the various aspects of JBoss Messaging at work.
+ The <filename>/doc/examples/jboss-messaging-examples/</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/jms/destinations</filename>.
+ Before you run these examples, deploy the <literal>jbm-examples-destinations-service</literal> located under <filename>/doc/examples/jboss-messaging-examples/destinations/</filename>.
</para>
<para>
@@ -16,7 +16,7 @@
<variablelist>
<varlistentry>
- <term><filename>docs/examples/jms/queue</filename></term>
+ <term><filename>/doc/examples/jboss-messaging-examples/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/examples/jms/topic</filename></term>
+ <term><filename>/doc/examples/jboss-messaging-examples/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/examples/jms/mdb</filename></term>
+ <term><filename>/doc/examples/jboss-messaging-examples/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/examples/jms/ejb3mdb</filename></term>
+ <term><filename>/doc/examples/jboss-messaging-examples/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/examples/jms/stateless</filename></term>
+ <term><filename>/doc/examples/jboss-messaging-examples/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/examples/jms/mdb-failure</filename></term>
+ <term><filename>/doc/examples/jboss-messaging-examples/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/examples/jms/secure-socket</filename></term>
+ <term><filename>/doc/examples/jboss-messaging-examples/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/examples/jms/http</filename></term>
+ <term><filename>/doc/examples/jboss-messaging-examples/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/examples/jms/web-service</filename></term>
+ <term><filename>/doc/examples/jboss-messaging-examples/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/examples/jms/distributed-queue</filename></term>
+ <term><filename>/doc/examples/jboss-messaging-examples/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/examples/jms/distributed-topic</filename></term>
+ <term><filename>/doc/examples/jboss-messaging-examples/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/examples/jms/stateless-clustered</filename></term>
+ <term><filename>/doc/examples/jboss-messaging-examples/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/examples/jms/bridge</filename></term>
+ <term><filename>/doc/examples/jboss-messaging-examples/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.
More information about the jboss-cvs-commits
mailing list