[jboss-cvs] JBossAS SVN: r95083 - projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/web-service.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Oct 19 00:00:33 EDT 2009
Author: laubai
Date: 2009-10-19 00:00:32 -0400 (Mon, 19 Oct 2009)
New Revision: 95083
Modified:
projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/web-service/README.html
Log:
Updated web-service readme files.
Modified: projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/web-service/README.html
===================================================================
--- projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/web-service/README.html 2009-10-19 03:52:52 UTC (rev 95082)
+++ projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/web-service/README.html 2009-10-19 04:00:32 UTC (rev 95083)
@@ -7,175 +7,108 @@
</head>
<body>
<br>
-<h1>Sending JMS messages from a WebService<br>
-</h1>
+<h1>Sending JMS messages from a WebService</h1>
<h2>Overview</h2>
-<br>
-This example deploys a WebServices that sends messages to a queue.
-The same client will then read the message from the queue, validating
-if the WebService could complete the message send.
-<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>
-This example will also generate client classes using wsdltools from
-JBoss Web Services.<br>
-<br>
+<p>
+ This example deploys a WebService that sends messages to a queue. The same client then reads the message from the queue, confirming that the WebService could complete the message send operation.
+</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>
+<p>
+ This example also generates client classes using <tt>wsdltools</tt> from JBoss Web Services.
+</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:\</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\web-services</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\web-services</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>
-example at example:/workspace/jboss-messaging-1.3.0.GA/examples/web-services$
-ant<br>
-Buildfile: build.xml<br>
- <br>
-identify:<br>
- [echo]
-###########################################################################<br>
- [echo]
-#
-Running the WebServices
-example
-#<br>
- [echo]
-###########################################################################<br>
- [echo] The
-queue: testQueue<br>
- [echo] The client jar:
-../..//jboss-messaging-client.jar<br>
- <br>
-sanity-check:<br>
- <br>
-init:<br>
- <br>
-compile:<br>
- <br>
-war:<br>
- [jar] Building jar:
-/workspace/jboss-messaging-1.3.0.GA/examples/web-services/output/lib/jms-web-service.war<br>
- <br>
-deploy:<br>
- [copy] Copying 1 file to
-/jboss-4.2.0.GA/server/messaging/deploy<br>
- <br>
-sleep:<br>
- [echo] Sleeping for 5 seconds ...<br>
- <br>
-run-wsdl-client:<br>
- [get] Getting:
-http://127.0.0.1:8080/jms-web-service/JMSWebServiceExample?wsdl<br>
- [get] To:
-/workspace/jboss-messaging-1.3.0.GA/examples/web-services/output/service.wsdl<br>
- [wstools] log4j:WARN No appenders could be found for logger
-(org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory).<br>
- [wstools] log4j:WARN Please initialize the log4j system properly.<br>
- <br>
-compile-client:<br>
- [mkdir] Created dir:
-/workspace/jboss-messaging-1.2.0.SP2/examples/web-services/output/client-classes<br>
- [javac] Compiling 5 source files to
-/workspace/jboss-messaging-1.2.0.SP2/examples/web-services/output/client-classes<br>
- <br>
-run:<br>
- <br>
-send-and-receive:<br>
- [java] log4j:WARN No appenders could be found
-for logger
-(org.jboss.ws.metadata.builder.jaxrpc.JAXRPCClientMetaDataBuilder).<br>
- [java] log4j:WARN Please initialize the log4j
-system properly.<br>
- [java] Message was received ok!<br>
- [java]<br>
- [java] #####################<br>
- [java] ###
-SUCCESS! ###<br>
- [java] #####################<br>
- <br>
-undeploy:<br>
- [delete] Deleting:
-/jboss-4.2.0.GA/server/messaging/deploy/jms-web-service.war<br>
- <br>
-BUILD SUCCESSFUL<br>
-Total time: 12 seconds<br>
- <br>
- <br>
+ <td style="vertical-align: top;"><pre>example at example:/workspace/jboss-messaging-1.3.0.GA/examples/web-services$ ant
+Buildfile: build.xml
+
+identify:
+ [echo] ###########################################################################
+ [echo] # Running the WebServices example #
+ [echo] ###########################################################################
+ [echo] The queue: testQueue
+ [echo] The client jar: ../..//jboss-messaging-client.jar
+
+sanity-check:
+
+init:
+
+compile:
+
+war:
+ [jar] Building jar: /workspace/jboss-messaging-1.3.0.GA/examples/web-services/output/lib/jms-web-service.war
+
+deploy:
+ [copy] Copying 1 file to /jboss-4.2.0.GA/server/messaging/deploy
+
+sleep:
+ [echo] Sleeping for 5 seconds ...
+
+run-wsdl-client:
+ [get] Getting: http://127.0.0.1:8080/jms-web-service/JMSWebServiceExample?wsdl
+ [get] To: /workspace/jboss-messaging-1.3.0.GA/examples/web-services/output/service.wsdl
+ [wstools] log4j:WARN No appenders could be found for logger (org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory).
+ [wstools] log4j:WARN Please initialize the log4j system properly.
+
+compile-client:
+ [mkdir] Created dir: /workspace/jboss-messaging-1.2.0.SP2/examples/web-services/output/client-classes
+ [javac] Compiling 5 source files to /workspace/jboss-messaging-1.2.0.SP2/examples/web-services/output/client-classes
+
+run:
+
+send-and-receive:
+ [java] log4j:WARN No appenders could be found for logger (org.jboss.ws.metadata.builder.jaxrpc.JAXRPCClientMetaDataBuilder).
+ [java] log4j:WARN Please initialize the log4j system properly.
+ [java] Message was received ok!
+ [java]
+ [java] #####################
+ [java] ### SUCCESS! ###
+ [java] #####################
+
+undeploy:
+ [delete] Deleting: /jboss-4.2.0.GA/server/messaging/deploy/jms-web-service.war
+
+BUILD SUCCESSFUL
+Total time: 12 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>
-<h3>2. <span style="font-family: monospace;">wstools doesn't work</span></h3>
-You could aways using "ant -debug" to verify what Exceptions wstools is
-generating. A common error is a NullPointerException due to a xerces
-update required by JBoss Web Services. You could have more information
-at this <a
- href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQXercesNPE">page</a>:<br>
-<br>
-<a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQXercesNPE">http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQXercesNPE</a><br>
-<br>
-<br>
-<br>
-<br>
-<hr style="width: 100%; height: 2px;"><br>
-<br>
-<br>
-<br>
-<br>
-<br>
-<br>
-</span>
+<h2>Troubleshooting</h2>
+<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 <tt>messaging</tt> security domain. Follow the instructions in the <emphasis>Installation</emphasis> section of the release documentation.
+</p>
+<h3>2. <span style="font-family: monospace;">wstools</span> does not work</h3>
+<p>
+ Try using <tt>ant -debug</tt> to verify the exceptions that <tt>wstools</tt> is generating. One common error is a <tt>NullPointerException</tt> because of a xerces update required by JBoss Web Services. You can find more information here: <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQXercesNPE">http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQXercesNPE</a>.
+</p>
</body>
</html>
More information about the jboss-cvs-commits
mailing list