[jboss-cvs] JBossAS SVN: r95081 - projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/topic.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sun Oct 18 23:49:15 EDT 2009
Author: laubai
Date: 2009-10-18 23:49:15 -0400 (Sun, 18 Oct 2009)
New Revision: 95081
Modified:
projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/topic/README.html
Log:
Updated topic readme files.
Modified: projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/topic/README.html
===================================================================
--- projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/topic/README.html 2009-10-19 03:40:42 UTC (rev 95080)
+++ projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/topic/README.html 2009-10-19 03:49:15 UTC (rev 95081)
@@ -8,136 +8,84 @@
<body>
<br>
<h1>JBoss Messaging Topic Example</h1>
-$Revision: 2751 $
+$ Revision: 2751 $
<h2>Overview</h2>
-<br>
-This example creates a JMS Connection to a JBoss Messaging instance
-and uses it to create a session, a publisher and a subscriber. The
-publisher sends a message to the topic. The example is considered
-successful
-if the topic subscriber receives the message.<br>
-<br>
-This example relies on having access to a running JBoss Messaging
-instance.
-The JBoss Messaging instance must be installed and started according to
-the
-"Installation" paragraph from the release documentation. However,
-the example will automatically deploy its own topic, unless a topic
-with the same name is already deployed. <br>
-<br>
-This example also relies on having access to <span
- style="font-family: monospace;">jboss-messaging-client.jar</span>
-archive that comes with the release bundle. If you run this example
-from
-an unzipped installation bundle, the example run script is correctly
-configured to find the client jar. Otherwise, you must modify example's
-<span style="font-family: monospace;">build.xml</span> accordingly.<br>
-<span style="font-style: italic;"></span><br>
+<p>
+ This example creates a Java Message Service (JMS) connection to a JBoss Messaging instance and uses it to create a session, a publisher, and a subscriber. The publisher sends a message to the topic. The example is considered successful if the subscriber receives the message.
+</p>
+<p>
+ This example requires access to a running JBoss Messaging instance that was installed and started according to the <emphasis>Installation</emphasis> section in the JBoss Messaging User Guide. The example automatically deploys its own queue unless a queue with the same name is already deployed.
+</p>
+<p>
+ This example also requires access to the <span style="font-family: monospace;">jboss-messaging-client.jar</span> archive included in the release bundle. If you run this example from an unzipped installation bundle, the example's run script is already configured to locate the archive. Otherwise, you must modify the example's <span style="font-family: monospace;">build.xml</span> to specify the location of the archive.
+</p>
+
<h2>Running the example</h2>
-1. Set up the JBOSS_HOME environment variable to point to the JBoss
-instance you deployed JBoss Messaging into. For example, if you
-deployed JBoss Messaging in <span style="font-family: monospace;">C:\jboss-4.2.0.GA\server\default\deploy,</span>
-then your JBOSS_HOME value should be <span
- style="font-family: monospace;">C:\</span><span
- style="font-family: monospace;">jboss-4.2.0.GA.</span><br>
-<span style="font-family: monospace;"></span><br>
-2. Go to the example's home directory<br>
-<br>
-<div style="margin-left: 40px;"><span style="font-family: monospace;">cd
-...\examples\topic</span><br>
-</div>
-<br>
-3. Run the example:<br>
-<br>
-<div style="margin-left: 40px;"><span style="font-family: monospace;">ant</span>
-<br>
-<br>
-<br>
-</div>
-The output of a successful run should be similar to:<br>
-<div style="margin-left: 40px;"><br>
-</div>
+<ol>
+ <li>
+ <p>Set the JBOSS_HOME environment variable to point to the instance of JBoss Application Server into which you deployed JBoss Messaging. If you deployed JBoss Messaging into <span style="font-family: monospace;">C:\jboss-4.2.0.GA\server\messaging\deploy</span>, your JBOSS_HOME value should be <span style="font-family: monospace;">C:\jboss-4.2.0.GA</span>.</p>
+ </li>
+ <li>
+ <p>Go to the example's home directory:</p>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">cd ...\examples\topic</span></div>
+ </li>
+ <li>
+ <p>Run the example:</p>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">ant</span></div>
+ </li>
+</ol>
+<p>
+ A successful run should have output similar to the following:
+</p>
+
+
<table
style="width: 90%; text-align: left; font-family: monospace; background-color: rgb(204, 204, 204); margin-left: 40px;"
border="1" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td style="vertical-align: top;">
- <div style="margin-left: 40px;"><br>
- </div>
-$ ant<br>
-Buildfile: build.xml<br>
- <br>
-identify:<br>
- [echo]
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX<br>
- [echo]
-X
-Running the TOPIC
-example
-X<br>
- [echo]
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX<br>
- [echo] The topic: testTopic<br>
- <br>
-sanity-check:<br>
- <br>
-init:<br>
- [mkdir] Created dir:
-C:\work\src\cvs\jboss-head\jms\docs\examples\topic\output<br>
- [mkdir] Created dir:
-C:\work\src\cvs\jboss-head\jms\docs\examples\common\output<br>
- <br>
-compile:<br>
- [javac] Compiling 2 source files to
-C:\work\src\cvs\jboss-head\jms\docs\examples\common\output<br>
- [javac] Compiling 2 source files to
-C:\work\src\cvs\jboss-head\jms\docs\examples\topic\output<br>
- <br>
-run:<br>
- [java] Topic /topic/testTopic exists<br>
- [java] The message was successfully published
-on the topic<br>
- [java] Received message: Hello!<br>
- [java] The example connected to JBoss
-Messaging version 1.2.0.GA (1.2)<br>
- <br>
- [java] #####################<br>
- [java] ###
-SUCCESS! ###<br>
- [java] #####################<br>
- <br>
-BUILD SUCCESSFUL<br>
-Total time: 4 seconds<br>
- <br>
- <br>
+ <div style="margin-left: 40px;"><pre>$ ant
+Buildfile: build.xml
+
+identify:
+ [echo] XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ [echo] X Running the TOPIC example X
+ [echo] XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ [echo] The topic: testTopic
+
+sanity-check:
+
+init:
+ [mkdir] Created dir: C:\work\src\cvs\jboss-head\jms\docs\examples\topic\output
+ [mkdir] Created dir: C:\work\src\cvs\jboss-head\jms\docs\examples\common\output
+
+compile:
+ [javac] Compiling 2 source files to C:\work\src\cvs\jboss-head\jms\docs\examples\common\output
+ [javac] Compiling 2 source files to C:\work\src\cvs\jboss-head\jms\docs\examples\topic\output
+
+run:
+ [java] Topic /topic/testTopic exists
+ [java] The message was successfully published on the topic
+ [java] Received message: Hello!
+ [java] The example connected to JBoss Messaging version 1.2.0.GA (1.2)
+
+ [java] #####################
+ [java] ### SUCCESS! ###
+ [java] #####################
+
+BUILD SUCCESSFUL
+Total time: 4 seconds</pre>
</td>
</tr>
</tbody>
</table>
<div style="margin-left: 40px;"><br>
</div>
-<br>
-<br>
-<h2>Troublesooting</h2>
-<h3>1. I get <span style="font-family: monospace;">"javax.jms.JMSSecurityException:
-User null is NOT authenticated" <br>
-</span></h3>
-You probably didn't install JBoss Messaging correctly. A fresh JBoss
-Messaging installation requires changes in the security configuration
-of a <span style="font-family: monospace;">default </span>JBoss
-instance, specifically a properly configured "<small><span
- style="font-family: courier new,courier,monospace;">messaging</span></small>"
-security domain. Follow the instructions from the "Installation"
-paragraph of the release documentation. <br>
-<br>
-<br>
-<hr style="width: 100%; height: 2px;"><br>
-<br>
-<br>
-<br>
-<br>
-<br>
-<br>
+<h2>Troubleshooting</h2>
+<h3>1. I get a <span style="font-family: monospace;">"javax.jms.JMSSecurityException: User null is NOT authenticated" exception</span></h3>
+<p>
+ JBoss Messaging may not have been installed correctly. A fresh JBoss Messaging installation requires changes to the security configuration of a <span style="font-family: monospace;">default</span> JBoss Application Server instance. In particular it requires a properly configured <tt>messaging</tt> security domain. Follow the instructions in the <emphasis>Installation</emphasis> section of the release documentation.
+</p>
</body>
</html>
More information about the jboss-cvs-commits
mailing list