[jboss-cvs] JBoss Messaging SVN: r2750 - in trunk/docs/examples: http/etc and 3 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri Jun 1 08:45:00 EDT 2007
Author: sergeypk
Date: 2007-06-01 08:45:00 -0400 (Fri, 01 Jun 2007)
New Revision: 2750
Modified:
trunk/docs/examples/http/README.html
trunk/docs/examples/http/etc/messaging-http-service.xml
trunk/docs/examples/mdb-failure/README.html
trunk/docs/examples/mdb/README.html
trunk/docs/examples/queue/README.html
Log:
Example documentation updates.
Modified: trunk/docs/examples/http/README.html
===================================================================
--- trunk/docs/examples/http/README.html 2007-06-01 12:32:41 UTC (rev 2749)
+++ trunk/docs/examples/http/README.html 2007-06-01 12:45:00 UTC (rev 2750)
@@ -2,31 +2,32 @@
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
- http-equiv="content-type">
- <title>JBoss Messaging Example - JMS Queue</title>
+ http-equiv="content-type">
+ <title>JBoss Messaging Example - HTTP Transport</title>
</head>
<body>
<br>
-<h1>JBoss Messaging Secure Socket Connection Example</h1>
+<h1>JBoss Messaging HTTP Transport Example</h1>
$Revision$
<h2>Overview</h2>
-<br>
-This example shows how to use a secure ConnectionFactory, which creates
-a SSL socket connection between client and server. The example will use
+<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 securely sent over
-an encrypted connection. The example is considered successful
+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.<br>
-<br>
+previously sent to the queue.</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. <br>
+the same name is already deployed.
+</p>
<h3 style="margin-left: 40px;">Warning</h3>
<div style="margin-left: 40px;">A service configuration bug that exists
in all JBoss versions prior to 4.0.4.RC1 prevents this example from
@@ -48,9 +49,9 @@
<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.0.4.GA\server\messaging\deploy,</span>
+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.0.4.GA</span><br>
+ style="font-family: monospace;">C:\jboss-4.2.0.GA</span><br>
<br>
2. Go to the example's home directory<br>
<br>
@@ -97,62 +98,49 @@
border="1" cellpadding="2" cellspacing="2">
<tbody>
<tr>
- <td style="vertical-align: top;"><br>
-$ ant<br>
-Buildfile: build.xml<br>
- <br>
-identify:<br>
- [echo]
-############################################################################<br>
- [echo]
-#
-Running the SECURE SOCKET
-example
-#<br>
- [echo]
-############################################################################<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\secure-socket\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 1 source file to
-C:\work\src\cvs\jboss-head\jms\docs\examples\secure-socket\output<br>
- <br>
-deploy:<br>
- [copy] Copying 1 file to
-C:\jboss-4.0.4.GA\server\messaging\deploy\jboss-messaging.sar<br>
- [copy] Copying 1 file to
-C:\jboss-4.0.4.GA\server\messaging\deploy<br>
- <br>
-sleep:<br>
- [echo] Sleeping for 10 seconds ...<br>
- <br>
-run:<br>
- [java] Queue /queue/testQueue exists<br>
- [java] The message was successfully sent to
-the testQueue queue<br>
- [java] Received message: Hello!<br>
- [java] The example connected to JBoss
-Messaging version 1.0.1.GA (1.0)<br>
- <br>
- [java] #####################<br>
- [java] ###
-SUCCESS! ###<br>
- [java] #####################<br>
- <br>
-BUILD SUCCESSFUL<br>
-Total time: 15 seconds<br>
- <br>
- <br>
+ <td style="vertical-align: top;">
+<pre>
+$ ant
+Buildfile: build.xml
+
+identify:
+ [echo] ############################################################################
+ [echo] # Running the HTTP example #
+ [echo] ############################################################################
+ [echo] The queue: testQueue
+ [echo] The client jar: ../../../output/lib/jboss-messaging-client.jar
+
+sanity-check:
+
+init:
+ [mkdir] Created dir: C:\java\messaging\docs\examples\http\output\classes
+ [mkdir] Created dir: C:\java\messaging\docs\examples\common\output\classes
+
+compile:
+ [javac] Compiling 5 source files to C:\java\messaging\docs\examples\common\output\classes
+ [javac] Compiling 1 source file to C:\java\messaging\docs\examples\http\output\classes
+
+deploy:
+ [copy] Copying 1 file to C:\jboss-4.2.0.GA\server\messaging\deploy
+
+sleep:
+ [echo] Sleeping for 10 seconds ...
+
+run:
+ [java] Queue /queue/testQueue exists
+ [java] The message was successfully sent to the testQueue queue
+ [java] Received message: Hello!
+ [java] The example connected to JBoss Messaging version 1.3.0.GA (1.3)
+ [java]
+ [java] #####################
+ [java] ### SUCCESS! ###
+ [java] #####################
+
+undeploy:
+ [delete] Deleting: C:\jboss-4.2.0.GA\server\messaging\deploy\messaging-http-service.xml
+
+BUILD SUCCESSFUL
+Total time: 14 seconds</pre>
</td>
</tr>
</tbody>
@@ -163,16 +151,13 @@
<h2>Configuration details</h2>
<br>
The example client looks up a specially-configured connection factory (<span
- style="font-family: monospace;">"/SecureConnectionFactory"</span>)
-that is deployed by the example run script. The secure
-ConnectionFactory relies on a "secured" Remoting Connector to provide
-the SSL connection. The definition of the required services is
-specified in the <span style="font-family: monospace;">etc/messaging-secure-socket-service.xml
+ style="font-family: monospace;">"/HttpConnectionFactory"</span>)
+that is deployed by the example run script. The HTTP
+ConnectionFactory relies on a HTTP Remoting Connector to provide
+the connection. The definition of the required services is
+specified in the <span style="font-family: monospace;">etc/messaging-http-service.xml
</span>deployment descriptor. The deployment descriptor, as used by the
-example, is listed below. Note that all services (the Connector, the
-secure ConnectionFactory, the SSLServerSocketFactoryService and the
-SSLSocketBuilder) are deployed in the same class loading domain as the
-messaging server:<br>
+example, is listed below.<br>
<br>
<br>
<div style="margin-left: 40px;"><br>
@@ -182,267 +167,56 @@
border="1" cellpadding="2" cellspacing="2">
<tbody>
<tr>
- <td style="vertical-align: top;"><br>
-<?xml version="1.0" encoding="UTF-8"?><br>
- <br>
-<!--<br>
- Secure Socket Transport Example: the
-deployment descriptor for the secure socket factory<br>
- service, secure connector and secure
-connection factory.<br>
- <br>
- $Id: remoting-service.xml,v 1.2 2006/05/08
-21:35:35 ovidiu Exp $<br>
- --><br>
- <br>
-<server><br>
- <br>
-
-<loader-repository>jboss.messaging:loader=ScopedLoaderRepository<br>
-
-<loader-repository-config>java2ParentDelegation=false</loader-repository-config><br>
- </loader-repository><br>
- <br>
- <mbean code="org.jboss.remoting.transport.Connector"<br>
-
-name="jboss.messaging:service=Connector,transport=SSLSocket"<br>
-
-display-name="SSL Socket Transport Connector"><br>
- <attribute name="Configuration"><br>
- <config><br>
-
-<invoker transport="sslsocket"><br>
-
-<attribute name="marshaller"<br>
-
-
-isParam="true">org.jboss.jms.server.remoting.JMSWireFormat</attribute><br>
-
-<attribute name="unmarshaller"<br>
-
-isParam="true">org.jboss.jms.server.remoting.JMSWireFormat</attribute><br>
-
-<attribute name="serializationtype"
-isParam="true">jboss</attribute><br>
-
-<attribute name="dataType" isParam="true">jms</attribute><br>
-
-<attribute name="socket.check_connection"
-isParam="true">false</attribute><br>
-
-<attribute name="timeout">0</attribute><br>
-
-<attribute
-name="serverBindAddress">${jboss.bind.address}</attribute><br>
-
-<attribute name="serverBindPort">5457</attribute><br>
-
-<attribute name="leasePeriod">20000</attribute><br>
-
-<attribute name="serverSocketFactory"><br>
-
-jboss.messaging:service=ServerSocketFactory,type=SSL<br>
-
-</attribute><br>
-
-</invoker><br>
-
-<handlers><br>
-
-<handler subsystem="JMS"><br>
-
-org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler><br>
-
-</handlers><br>
- </config><br>
- </attribute><br>
-
-<depends>jboss.messaging:service=ServerSocketFactory,type=SSL</depends><br>
- </mbean><br>
- <br>
- <mbean
-code="org.jboss.jms.server.connectionfactory.ConnectionFactory"<br>
-
-name="jboss.messaging.destination:service=SecureConnectionFactory"<br>
-
-xmbean-dd="xmdesc/ConnectionFactory-xmbean.xml"><br>
- <depends
-optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends><br>
- <depends
-optional-attribute-name="Connector"><br>
-
-jboss.messaging:service=Connector,transport=SSLSocket<br>
- </depends><br>
- <attribute name="JNDIBindings"><br>
- <bindings><br>
-
-<binding>/SecureConnectionFactory</binding><br>
- </bindings><br>
- </attribute><br>
- </mbean><br>
- <br>
- <!-- This section is for custom (SSL) server socket
-factory --><br>
- <br>
- <!--<br>
- The server socket factory
-mbean to be used as attribute to socket invoker (see<br>
- serverSocketFactory
-attribute above for where it is used). This service provides the exact<br>
- same API as the
-ServerSocketFactory, so can be set as an attribute of that type on any<br>
- MBean requiring an
-ServerSocketFactory.<br>
- --><br>
- <mbean
-code="org.jboss.remoting.security.SSLServerSocketFactoryService"<br>
-
-name="jboss.messaging:service=ServerSocketFactory,type=SSL"<br>
-
-display-name="SSL Server Socket Factory"><br>
- <depends
-optional-attribute-name="SSLSocketBuilder"<br>
-
-proxy-type="attribute">jboss.messaging:service=SocketBuilder,type=SSL</depends><br>
- </mbean><br>
- <br>
- <!--<br>
- This service is used to build the
-SSL Server socket factory. This will be where all the<br>
- store/trust information will be
-set. If do not need to make any custom configurations,<br>
- no extra attributes need to be set
-for the SSLSocketBuilder and just need to set the<br>
- javax.net.ssl.keyStore and
-javax.net.ssl.keyStorePassword system properties.<br>
- <br>
- This can be done by just adding
-something like the following to the run script for JBoss<br>
- (this one is for run.bat):<br>
- set
-JAVA_OPTS=-Djavax.net.ssl.keyStore=.keystore <br>
-
--Djavax.net.ssl.keyStorePassword=opensource %JAVA_OPTS%<br>
- <br>
- Otherwise, if want to customize
-the attributes for SSLSocketBuilder, will need to uncomment<br>
- them below.<br>
- --><br>
- <mbean
-code="org.jboss.remoting.security.SSLSocketBuilder"<br>
-
-name="jboss.messaging:service=SocketBuilder,type=SSL"<br>
-
-display-name="SSL Server Socket Factory Builder"><br>
- <!--<br>
- IMPORTANT
-- If making ANY customizations, this MUST be set to false.<br>
- Otherwise,
-will used default settings and the following attributes will be ignored.<br>
- --><br>
- <attribute
-name="UseSSLServerSocketFactory">false</attribute><br>
- <!-- This is the url string to the
-key store to use --><br>
- <attribute
-name="KeyStoreURL">messaging.keystore</attribute><br>
- <!-- The password for the key store
---><br>
- <attribute
-name="KeyStorePassword">secureexample</attribute><br>
- <!-- The password for the keys (will
-use KeystorePassword if this is not set explicitly. --><br>
- <attribute
-name="KeyPassword">secureexample</attribute><br>
- <!-- The protocol for the SSLContext.
-Default is TLS. --><br>
- <attribute
-name="SecureSocketProtocol">TLS</attribute><br>
- <!-- The algorithm for the key
-manager factory. Default is SunX509. --><br>
- <attribute
-name="KeyManagementAlgorithm">SunX509</attribute><br>
- <!--<br>
- The type
-to be used for the key store.<br>
- Defaults
-to JKS. Some acceptable values are JKS (Java Keystore - Sun's keystore
-format),<br>
- JCEKS
-(Java Cryptography Extension keystore - More secure version of JKS), and<br>
- PKCS12
-(Public-Key Cryptography Standards #12 keystore - RSA's Personal
-Information<br>
- Exchange
-Syntax Standard). These are not case sensitive.<br>
- --><br>
- <attribute
-name="KeyStoreType">JKS</attribute><br>
- </mbean><br>
- <br>
-</server><br>
- <br>
+ <td style="vertical-align: top;">
+<pre><?xml version="1.0" encoding="UTF-8"?>
+
+<!--
+ HTTP Transport Example.
+
+ $Id$
+ -->
+
+<server>
+
+ <mbean code="org.jboss.remoting.transport.Connector"
+ name="jboss.messaging:service=Connector,transport=http"
+ display-name="HTTP transport Connector">
+ <attribute name="Configuration">
+ <config>
+ <invoker transport="http">
+ <attribute name="marshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
+ <attribute name="unmarshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
+ <attribute name="dataType" isParam="true">jms</attribute>
+ <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
+ <attribute name="serverBindPort">4458</attribute>
+ <attribute name="leasePeriod">10000</attribute>
+ <attribute name="callbackStore">org.jboss.remoting.callback.CallbackStore</attribute>
+ <attribute name="callbackPollPeriod" isParam="true">100</attribute>
+ </invoker>
+ <handlers>
+ <handler subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler>
+ </handlers>
+ </config>
+ </attribute>
+ </mbean>
+
+ <mbean code="org.jboss.jms.server.connectionfactory.ConnectionFactory"
+ name="jboss.messaging.destination:service=HttpConnectionFactory"
+ xmbean-dd="xmdesc/ConnectionFactory-xmbean.xml">
+ <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
+ <depends optional-attribute-name="Connector">jboss.messaging:service=Connector,transport=http</depends>
+ <attribute name="JNDIBindings">
+ <bindings>
+ <binding>/HttpConnectionFactory</binding>
+ </bindings>
+ </attribute>
+ </mbean>
+
+</server></pre>
</td>
</tr>
</tbody>
</table>
-<div style="margin-left: 40px;"><br>
-</div>
-<br>
-The SSLSocketBuilder needs a keystore with a public/private key pair.
-The example provides one (<span style="font-family: monospace;">etc/messaging.keystore</span>)
-which is deployed with the rest of the artifacts. In case you need to
-create your own keystore, this is how you do it:<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>
- <pre> keytool -genkey -alias messaging.keypair -keyalg RSA -keystore messaging.keystore -validity 3650</pre>
- <br>
- </td>
- </tr>
- </tbody>
-</table>
-<div style="margin-left: 40px;"><br>
-</div>
-<br>
-<p>By default, the client will try to contact a Certificate Authority
-to
-insure the authenticity of the public key it uses to encrypt the
-communication. However, the example's certificate is self-signed, so no
-Certificate Authority will
-recognize it. In order to get the SSL client to trust it and the
-example to complete successfully, we use a client truststore (<span
- style="font-family: monospace;">/etc/messaging.truststore</span>). In
-case you need to create your own truststore, this is how you do it:<br>
-</p>
-<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>
- <pre> keytool -export -alias messaging.keypair -keystore messaging.keystore -rfc -file messaging.cer<br> keytool -import -alias messaging.keypair -file messaging.cer -keystore messaging.truststore</pre>
- <br>
- </td>
- </tr>
- </tbody>
-</table>
-<div style="margin-left: 40px;"><br>
-</div>
-<p> </p>
-<p>In order for the truststore to be recognized, the client's
-environment must contain the <tt>javax.net.ssl.trustStore</tt> and <tt>javax.net.ssl.trustStorePassword</tt>
-properties.<br>
-</p>
-<br>
<h2>Troubleshooting</h2>
<h3>1. I get <span style="font-family: monospace;">"javax.jms.JMSSecurityException:
User null is NOT authenticated" <br>
Modified: trunk/docs/examples/http/etc/messaging-http-service.xml
===================================================================
--- trunk/docs/examples/http/etc/messaging-http-service.xml 2007-06-01 12:32:41 UTC (rev 2749)
+++ trunk/docs/examples/http/etc/messaging-http-service.xml 2007-06-01 12:45:00 UTC (rev 2750)
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<!--
- HTTPt Transport Example.
+ HTTP Transport Example.
$Id$
-->
Modified: trunk/docs/examples/mdb/README.html
===================================================================
--- trunk/docs/examples/mdb/README.html 2007-06-01 12:32:41 UTC (rev 2749)
+++ trunk/docs/examples/mdb/README.html 2007-06-01 12:45:00 UTC (rev 2750)
@@ -51,10 +51,10 @@
<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.0.3SP1\server\default\deploy,</span>
+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.0.3SP1.</span><br>
+ 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>
@@ -78,75 +78,55 @@
<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 MDB
-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\mdb\output\classes\META-INF<br>
- [mkdir] Created dir:
-C:\work\src\cvs\jboss-head\jms\docs\examples\mdb\output\lib\META-INF<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\mdb\output\classes<br>
- <br>
-jar:<br>
- [copy] Copying 2 files to
-C:\work\src\cvs\jboss-head\jms\docs\examples\mdb\output\classes\META-INF<br>
- [jar] Building jar:
-C:\work\src\cvs\jboss-head\jms\docs\examples\mdb\output\lib\mdb-example.jar<br>
- <br>
-deploy:<br>
- [copy] Copying 1 file to
-C:\work\src\jboss-4.0.3SP1-src\build\output\jboss-4.0.3SP1\server\messaging\deploy<br>
- <br>
-sleep:<br>
- [echo] Sleeping for 5 seconds ...<br>
- <br>
-run:<br>
- <br>
-send:<br>
- [java] Queue /queue/testQueue exists<br>
- [java] The Hello! message was successfully
-sent to the testQueue queue<br>
- [java] Received message: !olleH<br>
- [java] The example connected to JBoss
-Messaging version 1.0.1.GA (1.0)<br>
- <br>
- [java] #####################<br>
- [java] ###
-SUCCESS! ###<br>
- [java] #####################<br>
- <br>
-undeploy:<br>
- [delete] Deleting:
-C:\work\src\jboss-4.0.3SP1-src\build\output\jboss-4.0.3SP1\server\messaging\deploy\mdb-example.jar<br>
- <br>
-BUILD SUCCESSFUL<br>
-Total time: 10 seconds<br>
- <br>
- <br>
+<pre>$ ant
+Buildfile: build.xml
+
+identify:
+ [echo] ###########################################################################
+ [echo] # Running the MDB example #
+ [echo] ###########################################################################
+ [echo] The queue: testQueue
+ [echo] The client jar: ../../../output/lib/jboss-messaging-client.jar
+
+sanity-check:
+
+init:
+ [mkdir] Created dir: C:\java\messaging\docs\examples\mdb\output\classes\META-INF
+ [mkdir] Created dir: C:\java\messaging\docs\examples\mdb\output\lib\META-INF
+ [mkdir] Created dir: C:\java\messaging\docs\examples\common\output\classes
+
+compile:
+ [javac] Compiling 5 source files to C:\java\messaging\docs\examples\common\output\classes
+ [javac] Compiling 2 source files to C:\java\messaging\docs\examples\mdb\output\classes
+
+jar:
+ [copy] Copying 2 files to C:\java\messaging\docs\examples\mdb\output\classes\META-INF
+ [jar] Building jar: C:\java\messaging\docs\examples\mdb\output\lib\mdb-example.jar
+
+deploy:
+ [copy] Copying 1 file to C:\jboss-4.2.0.GA\server\messaging\deploy
+
+sleep:
+ [echo] Sleeping for 5 seconds ...
+
+run:
+
+send:
+ [java] Queue /queue/testQueue exists
+ [java] The Hello! message was successfully sent to the testQueue queue
+ [java] Received message: !olleH
+ [java] The example connected to JBoss Messaging version 1.3.0.GA (1.3)
+ [java]
+ [java] #####################
+ [java] ### SUCCESS! ###
+ [java] #####################
+
+undeploy:
+ [delete] Deleting: C:\jboss-4.2.0.GA\server\messaging\deploy\mdb-example.jar
+
+BUILD SUCCESSFUL
+Total time: 10 seconds
+</pre>
</td>
</tr>
</tbody>
Modified: trunk/docs/examples/mdb-failure/README.html
===================================================================
--- trunk/docs/examples/mdb-failure/README.html 2007-06-01 12:32:41 UTC (rev 2749)
+++ trunk/docs/examples/mdb-failure/README.html 2007-06-01 12:45:00 UTC (rev 2750)
@@ -62,10 +62,9 @@
<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.0.3SP1\server\default\deploy,</span>
+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.0.3SP1.</span><br>
+ style="font-family: monospace;">C:\jboss-4.2.0.GA</span><br>
<span style="font-family: monospace;"></span><br>
2. Go to the example's home directory<br>
<br>
@@ -89,79 +88,61 @@
<tbody>
<tr>
<td style="vertical-align: top;">
- <div style="margin-left: 40px;"><br>
- </div>
-$ ant<br>
-Buildfile: build.xml<br>
- <br>
-identify:<br>
- [echo]
-###########################################################################<br>
- [echo]
-#
-Running the MDB Failure
-example
-#<br>
- [echo]
-###########################################################################<br>
- [echo] The
-queue: testQueue<br>
- [echo] The client jar:
-../../../output/lib/jboss-messaging-client.jar<br>
- <br>
-sanity-check:<br>
- <br>
-init:<br>
- [mkdir] Created dir:
-C:\work\src\svn\messaging-Branch_1_0_1_SP\docs\examples\mdb-failure\output\classes\META-INF<br>
- [mkdir] Created dir:
-C:\work\src\svn\messaging-Branch_1_0_1_SP\docs\examples\mdb-failure\output\lib\META-INF<br>
- [mkdir] Created dir:
-C:\work\src\svn\messaging-Branch_1_0_1_SP\docs\examples\common\output<br>
- <br>
-compile:<br>
- [javac] Compiling 2 source files to
-C:\work\src\svn\messaging-Branch_1_0_1_SP\docs\examples\common\output<br>
- [javac] Compiling 2 source files to
-C:\work\src\svn\messaging-Branch_1_0_1_SP\docs\examples\mdb-failure\output\classes<br>
- <br>
-jar:<br>
- [copy] Copying 2 files to
-C:\work\src\svn\messaging-Branch_1_0_1_SP\docs\examples\mdb-failure\output\classes\META-INF<br>
- [jar] Building jar:
-C:\work\src\svn\messaging-Branch_1_0_1_SP\docs\examples\mdb-failure\output\lib\mdb-failure-example.jar<br>
- <br>
-deploy:<br>
- [copy] Copying 1 file to
-C:\work\src\jboss-4.0.5.GA-src\build\output\jboss-4.0.5.GA\server\messaging\deploy<br>
- <br>
-sleep:<br>
- [echo] Sleeping for 5 seconds ...<br>
- <br>
-run:<br>
- <br>
-send:<br>
- [java] Queue /queue/testQueue exists<br>
- [java] The "Hello!" message was successfully
-sent to the testQueue queue<br>
- [java] Received message: !olleH<br>
- [java] The example connected to JBoss
-Messaging version 1.0.1.SP4 (1.0)<br>
- <br>
- [java] #####################<br>
- [java] ###
-SUCCESS! ###<br>
- [java] #####################<br>
- <br>
-undeploy:<br>
- [delete] Deleting:
-C:\work\src\jboss-4.0.5.GA-src\build\output\jboss-4.0.5.GA\server\messaging\deploy\mdb-failure-example.jar<br>
- <br>
-BUILD SUCCESSFUL<br>
-Total time: 9 seconds<br>
- <br>
- <br>
- <br>
+<pre>
+$ ant
+Buildfile: build.xml
+
+identify:
+ [echo] ###########################################################################
+ [echo] # Running the MDB Failure example #
+ [echo] ###########################################################################
+ [echo] The queue: testQueue
+ [echo] The client jar: ../../../output/lib/jboss-messaging-client.jar
+
+sanity-check:
+
+init:
+ [mkdir] Created dir: C:\java\messaging\docs\examples\mdb-failure\output\classes\META-INF
+ [mkdir] Created dir: C:\java\messaging\docs\examples\mdb-failure\output\lib\META-INF
+ [mkdir] Created dir: C:\java\messaging\docs\examples\common\output\classes
+
+compile:
+ [javac] Compiling 5 source files to C:\java\messaging\docs\examples\common\output\classes
+ [javac] Compiling 2 source files to C:\java\messaging\docs\examples\mdb-failure\output\classes
+ [javac] Note: C:\java\messaging\docs\examples\mdb-failure\src\org\jboss\example\jms\mdbfailure\MDBFailureExample.java uses unchecked or unsafe operations.
+ [javac] Note: Recompile with -Xlint:unchecked for details.
+
+jar:
+ [copy] Copying 2 files to C:\java\messaging\docs\examples\mdb-failure\output\classes\META-INF
+ [jar] Building jar: C:\java\messaging\docs\examples\mdb-failure\output\lib\mdb-failure-example.jar
+
+deploy:
+ [copy] Copying 1 file to C:\jboss-4.2.0.GA\server\messaging\deploy
+
+sleep:
+ [echo] Sleeping for 5 seconds ...
+
+run:
+
+send:
+ [java] Queue /queue/testQueue exists
+ [java] The "Hello!" message was successfully sent to the testQueue queue
+ [java] Received message: !olleH
+ [java] The example connected to JBoss Messaging version 1.3.0.GA (1.3)
+ [java]
+ [java] #####################
+ [java] ### SUCCESS! ###
+ [java] #####################
+
+sleep:
+ [echo] Sleeping for 10 seconds ...
+
+undeploy:
+ [delete] Deleting: C:\jboss-4.2.0.GA\server\messaging\deploy\mdb-failure-example.jar
+
+BUILD SUCCESSFUL
+Total time: 19 seconds
+</pre>
</td>
</tr>
</tbody>
Modified: trunk/docs/examples/queue/README.html
===================================================================
--- trunk/docs/examples/queue/README.html 2007-06-01 12:32:41 UTC (rev 2749)
+++ trunk/docs/examples/queue/README.html 2007-06-01 12:45:00 UTC (rev 2750)
@@ -39,10 +39,10 @@
<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.0.3SP1\server\messaging\deploy,</span>
+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.0.3SP1</span><br>
+ style="font-family: monospace;">jboss-4.2.0.GA</span><br>
<span style="font-family: monospace;"></span><span
style="font-family: monospace;"></span><br>
2. Go to the example's home directory<br>
@@ -67,54 +67,39 @@
<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 QUEUE
-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\queue\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 1 source file to
-C:\work\src\cvs\jboss-head\jms\docs\examples\queue\output<br>
- <br>
-run:<br>
- [java] Queue /queue/testQueue exists<br>
- [java] The message was successfully sent to
-the testQueue queue<br>
- [java] Received message: Hello!<br>
- [java] The example connected to JBoss
-Messaging version 1.0.1.GA (1.0)<br>
- <br>
- [java] #####################<br>
- [java] ###
-SUCCESS! ###<br>
- [java] #####################<br>
- <br>
-BUILD SUCCESSFUL<br>
-Total time: 5 seconds<br>
- <br>
- <br>
+<pre>
+Buildfile: build.xml
+
+identify:
+ [echo] ###########################################################################
+ [echo] # Running the QUEUE example #
+ [echo] ###########################################################################
+ [echo] The queue: testQueue
+ [echo] The client jar: ../../../output/lib/jboss-messaging-client.jar
+
+sanity-check:
+
+init:
+ [mkdir] Created dir: C:\java\messaging\docs\examples\queue\output\classes
+ [mkdir] Created dir: C:\java\messaging\docs\examples\common\output\classes
+
+compile:
+ [javac] Compiling 5 source files to C:\java\messaging\docs\examples\common\output\classes
+ [javac] Compiling 1 source file to C:\java\messaging\docs\examples\queue\output\classes
+
+run:
+ [java] Queue /queue/testQueue exists
+ [java] The message was successfully sent to the testQueue queue
+ [java] Received message: Hello!
+ [java] The example connected to JBoss Messaging version 1.3.0.GA (1.3)
+ [java]
+ [java] #####################
+ [java] ### SUCCESS! ###
+ [java] #####################
+
+BUILD SUCCESSFUL
+Total time: 4 seconds
+</pre>
</td>
</tr>
</tbody>
More information about the jboss-cvs-commits
mailing list