[jboss-cvs] JBossAS SVN: r95007 - projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/http.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri Oct 16 03:18:03 EDT 2009
Author: laubai
Date: 2009-10-16 03:18:03 -0400 (Fri, 16 Oct 2009)
New Revision: 95007
Modified:
projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/http/README.html
Log:
Corrected http readme.
Modified: projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/http/README.html
===================================================================
--- projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/http/README.html 2009-10-16 06:53:02 UTC (rev 95006)
+++ projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/http/README.html 2009-10-16 07:18:03 UTC (rev 95007)
@@ -6,86 +6,43 @@
<title>JBoss Messaging Example - HTTP Transport</title>
</head>
<body>
-<br>
+
<h1>JBoss Messaging HTTP Transport Example</h1>
-$Revision: 5394 $
+$ Revision: 5394 $
<h2>Overview</h2>
<p>
-This example shows how to configure a ConnectionFactory to send
-messages using the HTTP protocol. The example will use
-such a ConnectionFactory to create two JMS connections: the first one
-to send a message to the queue and the second one to read the message
-from the queue. In both cases, the message will be sent over
-an HTTP connection. The example is considered successful
-if the client receives without any error the message that was
-previously sent to the queue.</p>
+ This example demonstrates how to configure a ConnectionFactory to send messages with the HTTP protocol.
+</p>
<p>
-This example needs to have 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.
+ The example uses a ConnectionFactory to create two Java Message Service connections. The first connection sends a message to the queue; the second connection reads the message from the queue. In both cases, the message will be sent via a HTTP connection. This example is considered successful if the client receives, without error, the message that was sent to the queue.
</p>
-<br>
-This example also needs to have 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>
-<br>
+<p>
+ This example requires access to a running instance of JBoss Messaging, which must be installed and started according to the <emphasis>Installation</emphasis> section in the release documentation. The example will automatically deploy its own queue unless a queue with the same name is already deployed.
+</p>
+<p>
+ Finally, this example requires access to the <span style="font-family: monospace;">jboss-messaging-client.jar</span> archive included with the release bundle. If you run this example from an unzipped installation bundle, the example's run script is configured with the archive's path. Otherwise, you must modify the example's <span style="font-family: monospace;">build.xml</span> to reflect the path 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\messaging\deploy,</span>
-then your JBOSS_HOME value should be <span
- style="font-family: monospace;">C:\jboss-4.2.0.GA</span><br>
-<br>
-2. Go to the example's home directory<br>
-<br>
-<div style="margin-left: 40px;"><br>
-</div>
+<ol>
+ <li>
+ <p>
+ Set the JBOSS_HOME environment variable to point to the JBoss Application Server instance 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>
+ <span style="font-family: monospace;">cd ...\examples\http</span>
+ </li>
+ <li>
+ <p>Run the example:</p>
+ <span style="font-family: monospace;">ant</span>
+ </li>
+</ol>
+<p>
+ A successful run should have output similar to the following:
+</p>
+
<table
- style="width: 90%; text-align: left; font-family: monospace; margin-left: 40px; background-color: rgb(255, 255, 255);"
- border="1" cellpadding="2" cellspacing="2">
- <tbody>
- <tr>
- <td style="vertical-align: top;"><br>
- <span style="font-family: monospace;">cd
-...\examples\http</span><br>
- <br>
- </td>
- </tr>
- </tbody>
-</table>
-<span style="font-family: monospace;"></span><br>
-3. Run the example:<br>
-<br>
-<div style="margin-left: 40px;"><br>
-</div>
-<table
- style="width: 90%; text-align: left; font-family: monospace; margin-left: 40px; background-color: rgb(255, 255, 255);"
- border="1" cellpadding="2" cellspacing="2">
- <tbody>
- <tr>
- <td style="vertical-align: top;"><br>
- <span style="font-family: monospace;">ant</span><br>
- <br>
- </td>
- </tr>
- </tbody>
-</table>
-<div style="margin-left: 40px;"><br>
-</div>
-<br>
-The output of a successful run should be similar to:<br>
-<div style="margin-left: 40px;"><br>
-</div>
-<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>
@@ -141,26 +98,9 @@
</div>
<br>
<h2>Troubleshooting</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>
-<br>
-<br>
-<hr style="width: 100%; height: 2px;"><br>
-<br>
-<br>
-<br>
-<br>
-<br>
-<br>
+<h3>1. I get a <span style="font-family: monospace;">"javax.jms.JMSSecurityException: User null is NOT authenticated"</span> exception</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 <span style="font-family: courier new,courier,monospace;">messaging</span> security domain. Follow the instructions from the <emphasis>Installation</emphasis> section of the release documentation.
+</p>
</body>
</html>
More information about the jboss-cvs-commits
mailing list