[jboss-cvs] JBossAS SVN: r95079 - projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/stateless.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sun Oct 18 23:28:08 EDT 2009
Author: laubai
Date: 2009-10-18 23:28:08 -0400 (Sun, 18 Oct 2009)
New Revision: 95079
Modified:
projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/stateless/README.html
Log:
Updated stateless readme files.
Modified: projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/stateless/README.html
===================================================================
--- projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/stateless/README.html 2009-10-19 03:20:40 UTC (rev 95078)
+++ projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/stateless/README.html 2009-10-19 03:28:08 UTC (rev 95079)
@@ -6,153 +6,102 @@
<title>JBoss Messaging Example - Stateless Session Bean</title>
</head>
<body>
-<br>
-<h1>Sending JMS messages from a Stateless Session Bean<br>
-</h1>
-$Revision: 2751 $
+<h1>Sending JMS messages from a Stateless Session Bean</h1>
+$ Revision: 2751 $
<h2>Overview</h2>
-<br>
-This example deploys a stateless session bean that then sends and
-receives messages from a queue. This is a very simple example that
-demonstrates using JBoss Messaging in a managed environment. The
-session bean sends a message to a test queue and then pulls the message
-from the queue using a different connection. The
-example is considered successful if the message is received correctly.<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 queue, unless a queue
-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>
-<br>
+<p>
+ This example deploys a stateless session bean that sends and receives messages from a queue. This is a simple example that demonstrates using JBoss Messaging in a managed environment. The session bean sends a message to a test queue and then retrieves the message from the queue via a different connection. The example is considered successful if the message is received correctly.
+</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\stateless</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\stateless</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 STATELESS SESSION BEAN
-example
-X<br>
- [echo]
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX<br>
- [echo] The queue: testQueue<br>
- <br>
-sanity-check:<br>
- <br>
-init:<br>
- [mkdir] Created dir:
-C:\work\src\cvs\jboss-head\jms\docs\examples\stateless\output\classes\META-INF<br>
- [mkdir] Created dir:
-C:\work\src\cvs\jboss-head\jms\docs\examples\stateless\output\lib<br>
- <br>
-compile:<br>
- [javac] Compiling 4 source files to
-C:\work\src\cvs\jboss-head\jms\docs\examples\stateless\output\classes<br>
- <br>
-jar:<br>
- [copy] Copying 2 files to
-C:\work\src\cvs\jboss-head\jms\docs\examples\stateless\output\classes\META-INF<br>
- [jar] Building jar:
-C:\work\src\cvs\jboss-head\jms\docs\examples\stateless\output\lib\stateless-example.jar<br>
- <br>
-deploy:<br>
- [copy] Copying 1 file to
-C:\work\src\jboss-4.2.0.GA\build\output\jboss-4.0.3SP1\server\messaging\deploy<br>
- <br>
-sleep:<br>
- [echo] Sleeping for 5 seconds ...<br>
- <br>
-run:<br>
- <br>
-send-and-receive:<br>
- [java] The Hello! message was successfully
-sent to the /queue/testQueue queue<br>
- [java] Queue browse result: Hello!<br>
- [java] Received Hello!<br>
- <br>
- [java] #####################<br>
- [java] ###
-SUCCESS! ###<br>
- [java] #####################<br>
- <br>
-undeploy:<br>
- [delete] Deleting:
-C:\work\src\jboss-4.2.0.GA\build\output\jboss-4.0.3SP1\server\messaging\deploy\stateless-example.jar<br>
- <br>
-BUILD SUCCESSFUL<br>
-Total time: 9 seconds<br>
- <br>
- <br>
+ <td style="vertical-align: top;"><pre>
+$ ant
+Buildfile: build.xml
+
+identify:
+ [echo] XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ [echo] X Running the STATELESS SESSION BEAN example X
+ [echo] XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ [echo] The queue: testQueue
+
+sanity-check:
+
+init:
+ [mkdir] Created dir: C:\work\src\cvs\jboss-head\jms\docs\examples\stateless\output\classes
+ \META-INF
+ [mkdir] Created dir: C:\work\src\cvs\jboss-head\jms\docs\examples\stateless\output\lib
+
+compile:
+ [javac] Compiling 4 source files to C:\work\src\cvs\jboss-head\jms\docs\examples\stateless
+ \output\classes
+
+jar:
+ [copy] Copying 2 files to C:\work\src\cvs\jboss-head\jms\docs\examples\stateless\output
+ \classes\META-INF
+ [jar] Building jar: C:\work\src\cvs\jboss-head\jms\docs\examples\stateless\output\lib
+ \stateless-example.jar
+
+deploy:
+ [copy] Copying 1 file to C:\work\src\jboss-4.2.0.GA\build\output\jboss-4.0.3SP1\server
+ \messaging\deploy
+
+sleep:
+ [echo] Sleeping for 5 seconds ...
+
+run:
+
+send-and-receive:
+ [java] The Hello! message was successfully sent to the /queue/testQueue queue
+ [java] Queue browse result: Hello!
+ [java] Received Hello!
+
+ [java] #####################
+ [java] ### SUCCESS! ###
+ [java] #####################
+
+undeploy:
+ [delete] Deleting: C:\work\src\jboss-4.2.0.GA\build\output\jboss-4.0.3SP1\server\messaging\deploy\
+ stateless-example.jar
+
+BUILD SUCCESSFUL
+Total time: 9 seconds</pre>
</td>
</tr>
</tbody>
</table>
<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