7:44 a.m.
Author: jmesnil
Date: 2010-01-08 08:44:27 -0500 (Fri, 08 Jan 2010)
New Revision: 8778
Modified:
trunk/examples/core/embedded-remote/readme.html
trunk/examples/core/embedded/readme.html
trunk/examples/javaee/ejb-jms-transaction/readme.html
trunk/examples/javaee/hajndi/readme.html
trunk/examples/javaee/jca-config/readme.html
trunk/examples/javaee/jms-bridge/readme.html
trunk/examples/javaee/mdb-bmt/readme.html
trunk/examples/javaee/mdb-cmt-setrollbackonly/readme.html
trunk/examples/javaee/mdb-cmt-tx-local/readme.html
trunk/examples/javaee/mdb-cmt-tx-not-supported/readme.html
trunk/examples/javaee/mdb-cmt-tx-required/readme.html
trunk/examples/javaee/mdb-message-selector/readme.html
trunk/examples/javaee/mdb-tx-send/readme.html
trunk/examples/javaee/servlet-ssl/readme.html
trunk/examples/javaee/servlet-transport/readme.html
trunk/examples/jms/applet/readme.html
trunk/examples/jms/application-layer-failover/readme.html
trunk/examples/jms/bridge/readme.html
trunk/examples/jms/browser/readme.html
trunk/examples/jms/client-side-load-balancing/readme.html
trunk/examples/jms/clustered-durable-subscription/readme.html
trunk/examples/jms/clustered-grouping/readme.html
trunk/examples/jms/clustered-queue/readme.html
trunk/examples/jms/clustered-standalone/readme.html
trunk/examples/jms/clustered-topic/readme.html
trunk/examples/jms/consumer-rate-limit/readme.html
trunk/examples/jms/delayed-redelivery/readme.html
trunk/examples/jms/divert/readme.html
trunk/examples/jms/durable-subscription/readme.html
trunk/examples/jms/http-transport/readme.html
trunk/examples/jms/instantiate-connection-factory/readme.html
trunk/examples/jms/interceptor/readme.html
trunk/examples/jms/jmx/readme.html
trunk/examples/jms/large-message/readme.html
trunk/examples/jms/last-value-queue/readme.html
trunk/examples/jms/management/readme.html
trunk/examples/jms/message-group/readme.html
trunk/examples/jms/message-group2/readme.html
trunk/examples/jms/message-priority/readme.html
trunk/examples/jms/no-consumer-buffering/readme.html
trunk/examples/jms/non-transaction-failover/readme.html
trunk/examples/jms/paging/readme.html
trunk/examples/jms/pre-acknowledge/readme.html
trunk/examples/jms/producer-rate-limit/readme.html
trunk/examples/jms/queue-message-redistribution/readme.html
trunk/examples/jms/queue-requestor/readme.html
trunk/examples/jms/queue-selector/readme.html
trunk/examples/jms/queue/readme.html
trunk/examples/jms/reattach-node/readme.html
trunk/examples/jms/request-reply/readme.html
trunk/examples/jms/scheduled-message/readme.html
trunk/examples/jms/security/readme.html
trunk/examples/jms/send-acknowledgements/readme.html
trunk/examples/jms/ssl-enabled/readme.html
trunk/examples/jms/static-selector-jms/readme.html
trunk/examples/jms/static-selector/readme.html
trunk/examples/jms/symmetric-cluster/readme.html
trunk/examples/jms/temp-queue/readme.html
trunk/examples/jms/topic-hierarchies/readme.html
trunk/examples/jms/topic-selector-example1/readme.html
trunk/examples/jms/topic-selector-example2/readme.html
trunk/examples/jms/topic/readme.html
trunk/examples/jms/transaction-failover/readme.html
trunk/examples/jms/transactional/readme.html
trunk/examples/jms/xa-heuristic/readme.html
trunk/examples/jms/xa-receive/readme.html
trunk/examples/jms/xa-send/readme.html
trunk/examples/jms/xa-with-jta/readme.html
Log:
fixed examples' readmes
Modified: trunk/examples/core/embedded/readme.html
===================================================================
--- trunk/examples/core/embedded/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/core/embedded/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -8,9 +8,14 @@
<body onload="prettyPrint()">
<h1>Embedded Example</h1>
- <p>This examples shows how to setup and run HornetQ embedded.</p>
+ <p>This example shows how to setup and run HornetQ embedded.</p>
<p>HornetQ was designed to use POJOs (Plain Old Java Objects), what makes
embedding HornetQ as simple as instantiating a few objects.</p>
- <p>On this example, we are only using one jar (hornetq-core.jar).</p>
+ <p>On this example, we are using three jars:</p>
+ <ul>
+ <li>hornetq-core.jar</li>
+ <li>hornetq-transports.jar</li>
+ <li>netty.jar</li>
+ </ul>
<p>HornetQ Embedded could be used from very simple use cases with only InVM
support to very complex cases with clustering, persistence and fail over.</p>
Modified: trunk/examples/core/embedded-remote/readme.html
===================================================================
--- trunk/examples/core/embedded-remote/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/core/embedded-remote/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>Embedded Example</h1>
- <p>This examples shows how to setup and run HornetQ embedded with remote
clients connecting.</p>
+ <p>This example shows how to setup and run HornetQ embedded with remote
clients connecting.</p>
<p>HornetQ was designed to use POJOs (Plain Old Java Objects), what makes
embedding HornetQ as simple as instantiating a few objects.</p>
<p>We have limited the server classpath on this example:</p>
Modified: trunk/examples/javaee/ejb-jms-transaction/readme.html
===================================================================
--- trunk/examples/javaee/ejb-jms-transaction/readme.html 2010-01-08 11:02:17 UTC (rev
8777)
+++ trunk/examples/javaee/ejb-jms-transaction/readme.html 2010-01-08 13:44:27 UTC (rev
8778)
@@ -10,9 +10,12 @@
<p>This example will show how to run HornetQ in JBoss AS (Application
Server).</p>
- <p>The example application will invoke an EJB which will (1) send a JMS
message, (2) update a database from
- the same transaction.<br />
- The example application will then receive the message sent by the EJB.<br
/>
+ <p>The example application will invoke an EJB which will:</p>
+ <ol>
+ <li>send a JMS message</li>
+ <li>update a database from the same transaction</li>
+ </ol>
+ <p>The example application will then receive the message sent by the
EJB.<br />
We will also check that the database has been updated as expected.</p>
<h2>Example configuration</h2>
Modified: trunk/examples/javaee/hajndi/readme.html
===================================================================
--- trunk/examples/javaee/hajndi/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/javaee/hajndi/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -1,14 +1,14 @@
<html>
<head>
- <title>HornetQ Java EE HAJNDI Example</title>
+ <title>HornetQ Java EE HA-JNDI Example</title>
<link rel="stylesheet" type="text/css"
href="../../common/common.css" />
<link rel="stylesheet" type="text/css"
href="../../common/prettify.css" />
<script type="text/javascript"
src="../../common/prettify.js"></script>
</head>
<body onload="prettyPrint()">
- <h1>Java EE HAJNDI Example</h1>
+ <h1>Java EE HA-JNDI Example</h1>
- <p>This example demonstrates the use of High Availability JNDI (HA-JNDI) to
look-up HornetQ
+ <p>This example demonstrates the use of High Availability JNDI (HA-JNDI) to
lookup HornetQ
JMS Connection Factories, Queues and Topics.</p>
<p>With normal JNDI you need to configure the client with the specific
connection parameters
(i.e. host and port) of the JNDI server from which you want to perform
look-ups.</p>
Modified: trunk/examples/javaee/jca-config/readme.html
===================================================================
--- trunk/examples/javaee/jca-config/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/javaee/jca-config/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -8,13 +8,13 @@
<body onload="prettyPrint()">
<h1>Java EE Resource Adapter Configuration Example</h1>
<p>This example demonstrates how to configure several properties on the
HornetQ Resource Adapter. We setup two JBoss Servers. The enterprise application is being
deployed in one application server while the MDBs and JMS Connections are pointing to a
remote server</p>
- <p>This example is composed by two MDBs (MDBQueueA and MDBQueueB) and a
StatlessSessionBean (StatelessSender). The main class (MDBRemoteClientExample) will call a
method on StatelessSender and send a Message to Queue B.<p>
- <p>StatelessSender will send a message to Queue A and it is getting the
connection out of the JavaConnectionArchitecture (JCA) ConnectionFactory, and sending a
message to QueueA which will be received on MDBQueueA.</p>
+ <p>This example is composed by two message-driven beans (MDB), MDBQueueA and
MDBQueueB, and a stateless session bean StatelessSender. The main class,
MDBRemoteClientExample, will call a method on StatelessSender and send a Message to Queue
B.<p>
+ <p>StatelessSender will send a message to Queue A and it is getting the
connection out of the Java Connection Architecture (JCA) ConnectionFactory, and sending a
message to QueueA which will be received on MDBQueueA.</p>
<p>MDBQueueB is connected to a different HornetQ resource-adapter, and it will
receive the message sent by the main Class.</p>
<p>All the MDBs and JMS Connections are referring to the remote
server</p>
<p>A Resource Adapter is a way to connect any system provider to an
application server, and is integral part of the Java Connectors Architecture
specification.</p>
<p>HornetQ provides its own adapter and this example will provide you a quick
tutorial on how to configure some of the default properties, and how to change the default
values on MDB Inbound Properties, or on ConnectionFactory Outbound Properties.</p>
- <p>This ResourceAdapter is what provides integration for Message Drive Beans
(MDBs) or DataSource integration on the application server.</p>
+ <p>This ResourceAdapter is what provides integration for Message-Driven Beans
or DataSource integration on the application server.</p>
<h2>MDB Properties</h2>
<p>You can configure the adapter through ActivactionConfigProperties on the
MDB. Example:</p>
<pre class="prettyprint">
@@ -137,7 +137,7 @@
<p><i>To run the example, simply type <code>./build.sh
run</code> (or <code>build.bat run</code> on windows) from the example
directory</i></p>
<p><i>To undeploy the example, simply type <code>./build.sh
undeploy undeploy2</code> (or <code>build.bat undeploy undeploy2</code>
on windows) from the example directory</i></p>
<p><i> ** make sure that JBOSS_HOME is set to the JBoss installation
directory</i></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the EJB on
the second server from JNDI. This initial context will get it's properties from the
<code>jndi.properties</code> file in the directory
<code>config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/javaee/jms-bridge/readme.html
===================================================================
--- trunk/examples/javaee/jms-bridge/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/javaee/jms-bridge/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -32,7 +32,7 @@
<h3>JMS Bridge configuration</h3>
- <p>The JMS Bridge is configured using JBoss microcontainer (<a
href="config/jms-bridge-jboss-beans.xml">jms-bridge-jboss-beans.xml</a>
contains comments about the various parameters
+ <p>The JMS Bridge is configured using JBoss microcontainer (<a
href="server/jms-bridge-jboss-beans.xml">jms-bridge-jboss-beans.xml</a>
contains comments about the various parameters
used to configure the bridge).<br />
<p>The Bridge is deployed in the application server when you simply type
<code>./build.sh deploy</code> (or <code>build.bat deploy</code>
on windows) (it is copied to
<code>${JBOSS_HOME}/server/default-with-hornetq/deploy/</code>).</p>
@@ -43,7 +43,7 @@
<p>The example is simple: the application will send a message to the
<em>source</em> queue and consume the same message
from the <em>target</em> queue.</p>
- <p>The bridge was configured in <a
href="config/jms-bridge-jboss-beans.xml">jms-bridge-jboss-beans.xml</a>
to bridge these two queues.</p>
+ <p>The bridge was configured in <a
href="server/jms-bridge-jboss-beans.xml">jms-bridge-jboss-beans.xml</a>
to bridge these two queues.</p>
<ol>
<li>First we need to get an initial context so we can look up the JMS
resources
Modified: trunk/examples/javaee/mdb-bmt/readme.html
===================================================================
--- trunk/examples/javaee/mdb-bmt/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/javaee/mdb-bmt/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>Java EE MDB Bean Managed Transaction Example</h1>
- <br>
+
<p>This example shows you how to send a message to an MDB configured to use
Bean Managed Transactions</p>
<p>
The example will send deploy a simple MDB and demonstrate sending a message and
the MDB consuming it
@@ -21,8 +21,8 @@
<p><i>To deploy and start the server, simply type <code>./build.sh
deploy</code> (or <code>build.bat deploy</code> on windows) from the
example directory</i></p>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from the example directory</i></p>
<p><i>To remove the example profile, simply type <code>./build.sh
undeploy</code> (or <code>build.bat undeploy</code> on windows) from the
example directory</i></p>
- <p><i> ** make sure that JBOSS_HOME is set to the Jboss installation
directory</i></p>
- <br>
+ <p><i> ** make sure that JBOSS_HOME is set to the JBoss installation
directory</i></p>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>jndi.properties</code> file in the
directory <code>config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/javaee/mdb-cmt-setrollbackonly/readme.html
===================================================================
--- trunk/examples/javaee/mdb-cmt-setrollbackonly/readme.html 2010-01-08 11:02:17 UTC (rev
8777)
+++ trunk/examples/javaee/mdb-cmt-setrollbackonly/readme.html 2010-01-08 13:44:27 UTC (rev
8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>Java EE MDB SetRollbackOnly Example</h1>
- <br>
+
<p>This example shows you how to send a message to an MDB and then roll back
the transaction forcing re delivery</p>
<p>
The example will send deploy a simple MDB and demonstrate sending a message and
the MDB consuming it
@@ -21,8 +21,8 @@
<p><i>To deploy and start the server, simply type <code>./build.sh
deploy</code> (or <code>build.bat deploy</code> on windows) from the
example directory</i></p>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from the example directory</i></p>
<p><i>To remove the example profile, simply type <code>./build.sh
undeploy</code> (or <code>build.bat undeploy</code> on windows) from the
example directory</i></p>
- <p><i> ** make sure that JBOSS_HOME is set to the Jboss installation
directory</i></p>
- <br>
+ <p><i> ** make sure that JBOSS_HOME is set to the JBoss installation
directory</i></p>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>jndi.properties</code> file in the
directory <code>config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/javaee/mdb-cmt-tx-local/readme.html
===================================================================
--- trunk/examples/javaee/mdb-cmt-tx-local/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/javaee/mdb-cmt-tx-local/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>Java EE MDB using a local transaction Example</h1>
- <br>
+
<p>This example shows you how to send a message to an MDB and deliver it
within a local transaction</p>
<p>
The example will send deploy a simple MDB and demonstrate sending a message and
the MDB consuming it, throwing an exception and the message being re delivered.
@@ -21,8 +21,8 @@
<p><i>To deploy and start the server, simply type <code>./build.sh
deploy</code> (or <code>build.bat deploy</code> on windows) from the
example directory</i></p>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from the example directory</i></p>
<p><i>To remove the example profile, simply type <code>./build.sh
undeploy</code> (or <code>build.bat undeploy</code> on windows) from the
example directory</i></p>
- <p><i> ** make sure that JBOSS_HOME is set to the Jboss installation
directory</i></p>
- <br>
+ <p><i> ** make sure that JBOSS_HOME is set to the JBoss installation
directory</i></p>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>jndi.properties</code> file in the
directory <code>config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/javaee/mdb-cmt-tx-not-supported/readme.html
===================================================================
--- trunk/examples/javaee/mdb-cmt-tx-not-supported/readme.html 2010-01-08 11:02:17 UTC
(rev 8777)
+++ trunk/examples/javaee/mdb-cmt-tx-not-supported/readme.html 2010-01-08 13:44:27 UTC
(rev 8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>Java EE MDB Container Managed Transaction with NOT_SUPPORTED transaction
Example</h1>
- <br>
+
<p>This example shows you how to send a message to an MDB</p>
<p>
The example will send deploy a simple MDB and demonstrate sending a message and
the MDB consuming it but with a transaction as this MDB does not support one.
@@ -21,8 +21,8 @@
<p><i>To deploy and start the server, simply type <code>./build.sh
deploy</code> (or <code>build.bat deploy</code> on windows) from the
example directory</i></p>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from the example directory</i></p>
<p><i>To remove the example profile, simply type <code>./build.sh
undeploy</code> (or <code>build.bat undeploy</code> on windows) from the
example directory</i></p>
- <p><i> ** make sure that JBOSS_HOME is set to the Jboss installation
directory</i></p>
- <br>
+ <p><i> ** make sure that JBOSS_HOME is set to the JBoss installation
directory</i></p>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>jndi.properties</code> file in the
directory <code>config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/javaee/mdb-cmt-tx-required/readme.html
===================================================================
--- trunk/examples/javaee/mdb-cmt-tx-required/readme.html 2010-01-08 11:02:17 UTC (rev
8777)
+++ trunk/examples/javaee/mdb-cmt-tx-required/readme.html 2010-01-08 13:44:27 UTC (rev
8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>Java EE MDB Container Managed Transactions Example</h1>
- <br>
+
<p>This example shows you how to send a message to an MDB that is delivered
within a transaction controlled by the container</p>
<p>
The example will send deploy a simple MDB and demonstrate sending a message and
the MDB consuming it
@@ -21,8 +21,8 @@
<p><i>To deploy and start the server, simply type <code>./build.sh
deploy</code> (or <code>build.bat deploy</code> on windows) from the
example directory</i></p>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from the example directory</i></p>
<p><i>To remove the example profile, simply type <code>./build.sh
undeploy</code> (or <code>build.bat undeploy</code> on windows) from the
example directory</i></p>
- <p><i> ** make sure that JBOSS_HOME is set to the Jboss installation
directory</i></p>
- <br>
+ <p><i> ** make sure that JBOSS_HOME is set to the JBoss installation
directory</i></p>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>jndi.properties</code> file in the
directory <code>config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/javaee/mdb-message-selector/readme.html
===================================================================
--- trunk/examples/javaee/mdb-message-selector/readme.html 2010-01-08 11:02:17 UTC (rev
8777)
+++ trunk/examples/javaee/mdb-message-selector/readme.html 2010-01-08 13:44:27 UTC (rev
8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>Java EE MDB Message Selector Example</h1>
- <br>
+
<p>This example shows you how to send a message to an MDB that is configured
to use a message selector</p>
<p>
The example will send deploy a simple MDB and demonstrate sending a message and
the MDB consuming only the message that matches the message selector.
@@ -21,8 +21,8 @@
<p><i>To deploy and start the server, simply type <code>./build.sh
deploy</code> (or <code>build.bat deploy</code> on windows) from the
example directory</i></p>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from the example directory</i></p>
<p><i>To remove the example profile, simply type <code>./build.sh
undeploy</code> (or <code>build.bat undeploy</code> on windows) from the
example directory</i></p>
- <p><i> ** make sure that JBOSS_HOME is set to the Jboss installation
directory</i></p>
- <br>
+ <p><i> ** make sure that JBOSS_HOME is set to the JBoss installation
directory</i></p>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>jndi.properties</code> file in the
directory <code>config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/javaee/mdb-tx-send/readme.html
===================================================================
--- trunk/examples/javaee/mdb-tx-send/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/javaee/mdb-tx-send/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>Java EE MDB Send Example</h1>
- <br>
+
<p>This example shows you how to send a message to an MDB that returns a reply
using the same XA transaction</p>
<p>
The example will send deploy a simple MDB and demonstrate sending a message and
the MDB consuming it
@@ -21,8 +21,8 @@
<p><i>To deploy and start the server, simply type <code>./build.sh
deploy</code> (or <code>build.bat deploy</code> on windows) from the
example directory</i></p>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from the example directory</i></p>
<p><i>To remove the example profile, simply type <code>./build.sh
undeploy</code> (or <code>build.bat undeploy</code> on windows) from the
example directory</i></p>
- <p><i> ** make sure that JBOSS_HOME is set to the Jboss installation
directory</i></p>
- <br>
+ <p><i> ** make sure that JBOSS_HOME is set to the JBoss installation
directory</i></p>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>jndi.properties</code> file in the
directory <code>config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/javaee/servlet-ssl/readme.html
===================================================================
--- trunk/examples/javaee/servlet-ssl/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/javaee/servlet-ssl/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>Java EE SSL Servlet Example</h1>
- <br>
+
<p>This example shows you how to configure and use servlet transport over SSL
with HornetQ.</p>
<h2>JBoss AS configuration</h2>
@@ -25,7 +25,7 @@
Once the server has started type simply type <code>./build.sh run</code>
(or <code>build.bat run</code> on windows) to run the example.<br />
To remove the new profile type simply type <code>./build.sh
undeploy</code> (or <code>build.bat undeploy</code> on
windows).</em></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>jndi.properties</code> file in the
directory <code>config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/javaee/servlet-transport/readme.html
===================================================================
--- trunk/examples/javaee/servlet-transport/readme.html 2010-01-08 11:02:17 UTC (rev
8777)
+++ trunk/examples/javaee/servlet-transport/readme.html 2010-01-08 13:44:27 UTC (rev
8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>Java EE Servlet Example</h1>
- <br>
+
<p>This example shows you how to configure and use servlet transport with
HornetQ.</p>
<h2>JBoss AS configuration</h2>
@@ -23,7 +23,7 @@
Once the server has started simply type <code>./build.sh run</code> (or
<code>build.bat run</code> on windows) to run the example.<br />
To remove the new profile type simply type <code>./build.sh
undeploy</code> (or <code>build.bat undeploy</code> on
windows).</em></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>jndi.properties</code> file in the
directory <code>config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/applet/readme.html
===================================================================
--- trunk/examples/jms/applet/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/applet/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,7 +7,6 @@
</head>
<body onload="prettyPrint()">
<h1>Applet Example</h1>
- <br>
<p>This example shows you how to send and receive JMS messages from an
Applet.</p>
<h2>Example step-by-step</h2>
Modified: trunk/examples/jms/application-layer-failover/readme.html
===================================================================
--- trunk/examples/jms/application-layer-failover/readme.html 2010-01-08 11:02:17 UTC (rev
8777)
+++ trunk/examples/jms/application-layer-failover/readme.html 2010-01-08 13:44:27 UTC (rev
8778)
@@ -6,8 +6,8 @@
<script type="text/javascript"
src="../../common/prettify.js"></script>
</head>
<body onload="prettyPrint()">
- <h1>HornetQ Application-Layer Failover Example</h1>
- <br>
+ <h1>Application-Layer Failover Example</h1>
+
<p>HornetQ implements fully transparent <b>automatic</b> failover
of connections from a live to backup node, this requires
no special coding for failover, and is described in a different example. Automatic
failover requires server replication.</p>
<p>However, HornetQ also supports <b>Application-Layer</b>
failover, useful in the case that replication is not enabled
@@ -22,13 +22,14 @@
work in the old Session will be lost, and any unacknowledged messages might be
redelivered.</p>
<p>For more information on HornetQ failover and HA, and clustering in general,
please see the clustering
section of the user manual.</p>
+
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
<p>In this example, the live server is server 1, which will failover onto
server 0.</p>
<p>The connection will initially be created to server1, server 1 will crash,
and the client will carry on
on server 0, the new server. With Application-Layer failover the node that is
failed over onto, does not need to
be specially configured as a backup server, it can be any node.</p>
- <br>
+
<ol>
<li> We create our JMS Connection, Session, MessageProducer and
MessageConsumer on server 1</li>
<pre class="prettyprint">
Modified: trunk/examples/jms/bridge/readme.html
===================================================================
--- trunk/examples/jms/bridge/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/bridge/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -6,8 +6,7 @@
<script type="text/javascript"
src="../../common/prettify.js"></script>
</head>
<body onload="prettyPrint()">
- <h1>HornetQ Core Bridge Example</h1>
- <br>
+ <h1>Core Bridge Example</h1>
<p>This example demonstrates a core bridge deployed on one server, which
consumes messages from a
local queue and forwards them to an address on a second server.</p>
@@ -25,7 +24,7 @@
between HornetQ instances, but may provide better performance than the JMS bridge.
The JMS bridge is covered in
a separate example.</p>
<p>For more information on bridges, please see the HornetQ user
manual.</p>
- <br>
+
<p>In this example we will demonstrate a simple sausage factory for
aardvarks.</p>
<p>We have a JMS queue on server 0 named
<code>sausage-factory</code>, and we have a
JMS queue on server 1 named <code>mincing-machine</code></p>
@@ -51,7 +50,7 @@
</pre>
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>We create an initial context for looking up JNDI on node 0</li>
<pre class="prettyprint">
Modified: trunk/examples/jms/browser/readme.html
===================================================================
--- trunk/examples/jms/browser/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/browser/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -6,8 +6,8 @@
<script type="text/javascript"
src="../../common/prettify.js"></script>
</head>
<body onload="prettyPrint()">
- <h1>JMS Queue Example</h1>
- <br>
+ <h1>JMS QueueBrowser Example</h1>
+
<p>This example shows you how to use a JMS <a
href="http://java.sun.com/javaee/5/docs/api/javax/jms/QueueBrowser.h...
with HornetQ.<br />
Queues are a standard part of JMS, please consult the JMS 1.1 specification for full
details.<br />
A QueueBrowser is used to look at messages on the queue without removing them.
@@ -18,7 +18,7 @@
</p>
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>client-jndi.properties</code> file in the
directory <code>../common/config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/client-side-load-balancing/readme.html
===================================================================
--- trunk/examples/jms/client-side-load-balancing/readme.html 2010-01-08 11:02:17 UTC (rev
8777)
+++ trunk/examples/jms/client-side-load-balancing/readme.html 2010-01-08 13:44:27 UTC (rev
8778)
@@ -1,13 +1,13 @@
<html>
<head>
- <title>HornetQ JMS Client Side Load-Balancing Example</title>
+ <title>HornetQ JMS Client-Side Load-Balancing Example</title>
<link rel="stylesheet" type="text/css"
href="../../common/common.css" />
<link rel="stylesheet" type="text/css"
href="../../common/prettify.css" />
<script type="text/javascript"
src="../../common/prettify.js"></script>
</head>
<body onload="prettyPrint()">
- <h1>HornetQ JMS Client Side Load-Balancing Example</h1>
- <br>
+ <h1>JMS Client-Side Load-Balancing Example</h1>
+
<p>This example demonstrates how subsequent connections created from a JMS
Connection Factory can be created
to different nodes of the cluster. In other words it demonstrates how HornetQ does
<b>client side load balancing</b> of
connections across the cluster.</p>
@@ -24,9 +24,10 @@
connection factory.</p>
<p>For more information on HornetQ load balancing, and clustering in general,
please see the clustering
section of the user manual.</p>
+
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li> Get an initial context for looking up JNDI from server 0.</li>
<pre class="prettyprint">>
Modified: trunk/examples/jms/clustered-durable-subscription/readme.html
===================================================================
--- trunk/examples/jms/clustered-durable-subscription/readme.html 2010-01-08 11:02:17 UTC
(rev 8777)
+++ trunk/examples/jms/clustered-durable-subscription/readme.html 2010-01-08 13:44:27 UTC
(rev 8778)
@@ -6,8 +6,8 @@
<script type="text/javascript"
src="../../common/prettify.js"></script>
</head>
<body onload="prettyPrint()">
- <h1>HornetQ JMS Durable Subscription Example</h1>
- <br>
+ <h1>JMS Durable Subscription Example</h1>
+
<p>This example demonstrates a clustered JMS durable subscription.
Normally durable subscriptions exist on a single node and can only have one
subscriber at any one time,
however, with HornetQ it's possible to create durable subscription instances
with the same name and client-id
@@ -38,10 +38,11 @@
</code>
</pre>
<p>For more information on HornetQ load balancing, and clustering in general,
please see the clustering
- section of the user manual.</p>
+ section of the user manual.</p>
+
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li> Get an initial context for looking up JNDI from server 0.</li>
<pre class="prettyprint">
Modified: trunk/examples/jms/clustered-grouping/readme.html
===================================================================
--- trunk/examples/jms/clustered-grouping/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/clustered-grouping/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -4,8 +4,8 @@
<link rel="stylesheet" type="text/css"
href="../../common/common.css">
</head>
<body>
- <h1>HornetQ JMS Clustered Grouping Example</h1>
- <br>
+ <h1>JMS Clustered Grouping Example</h1>
+
<p>This example demonstrates how to ensure strict ordering across a cluster
using clustered message grouping</p>
<p>We create 3 nodes each with a grouping message handler, one with a Local
handler and 2 with a Remote handler.</p>
<p>The local handler acts as an arbitrator for the 2 remote handlers, holding
the information on routes and communicating that with the remote handlers</p>
@@ -57,7 +57,7 @@
section of the user manual.</p>
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li> Get an initial context for looking up JNDI from server 0.</li>
<pre class="prettyprint">
Modified: trunk/examples/jms/clustered-queue/readme.html
===================================================================
--- trunk/examples/jms/clustered-queue/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/clustered-queue/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -1,13 +1,13 @@
<html>
<head>
- <title>HornetQ JMS Load Balanced Queue Example</title>
+ <title>HornetQ JMS Load Balanced Clustered Queue Example</title>
<link rel="stylesheet" type="text/css"
href="../../common/common.css" />
<link rel="stylesheet" type="text/css"
href="../../common/prettify.css" />
<script type="text/javascript"
src="../../common/prettify.js"></script>
</head>
<body onload="prettyPrint()">
- <h1>HornetQ JMS Load Balanced Clustered Queue Example</h1>
- <br>
+ <h1>JMS Load Balanced Clustered Queue Example</h1>
+
<p>This example demonstrates a JMS queue deployed on two different nodes. The
two nodes are configured to form a cluster.</p>
<p>We then create a consumer on the queue on each node, and we create a
producer on only one of the nodes.</p>
<p>We then send some messages via the producer, and we verify that
<b>both</b> consumers receive the sent messages
@@ -32,7 +32,7 @@
section of the user manual.</p>
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li> Get an initial context for looking up JNDI from server 0.</li>
<pre class="prettyprint">
Modified: trunk/examples/jms/clustered-standalone/readme.html
===================================================================
--- trunk/examples/jms/clustered-standalone/readme.html 2010-01-08 11:02:17 UTC (rev
8777)
+++ trunk/examples/jms/clustered-standalone/readme.html 2010-01-08 13:44:27 UTC (rev
8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>JMS Clustered Stand-alone Example</h1>
- <br>
+
<p>This example demonstrates a JMS Topic deployed on three different nodes.
The three nodes are configured to form a cluster.</p>
<p>Subscriber for the topic are created on each node, and a producer is
created on only one of the nodes.</p>
Modified: trunk/examples/jms/clustered-topic/readme.html
===================================================================
--- trunk/examples/jms/clustered-topic/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/clustered-topic/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -6,8 +6,8 @@
<script type="text/javascript"
src="../../common/prettify.js"></script>
</head>
<body onload="prettyPrint()">
- <h1>HornetQ JMS Clustered Topic Example</h1>
- <br>
+ <h1>JMS Clustered Topic Example</h1>
+
<p>This example demonstrates a JMS Topic deployed on two different nodes. The
two nodes are configured to form a cluster.</p>
<p>We then create a subscriber on the topic on each node, and we create a
producer on only one of the nodes.</p>
<p>We then send some messages via the producer, and we verify that
<b>both</b> subscribers receive all the
@@ -33,7 +33,7 @@
section of the user manual.</p>
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li> Get an initial context for looking up JNDI from server 0.</li>
<pre class="prettyprint">
Modified: trunk/examples/jms/consumer-rate-limit/readme.html
===================================================================
--- trunk/examples/jms/consumer-rate-limit/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/consumer-rate-limit/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -6,8 +6,8 @@
<script type="text/javascript"
src="../../common/prettify.js"></script>
</head>
<body onload="prettyPrint()">
- <h1>HornetQ <br>JMS Message Consumer Rate Limiting</h1>
- <br><br>
+ <h1>JMS Message Consumer Rate Limiting</h1>
+
<p>With HornetQ you can specify a maximum consume rate at which a JMS
MessageConsumer will consume messages.
This can be specified when creating or deploying the connection factory. See
<code>hornetq-jms.xml</code></p>
<p>If this value is specified then HornetQ will ensure that messages are never
consumed at a rate higher than
@@ -32,9 +32,9 @@
</pre>
<p>We then simply consume as many messages as we can in 10 seconds and note
how many messages are actually consumed.</p>
<p>We note that the number of messages consumed per second never exceeds the
specified value of <code>10</code> messages per second.</p>
- <br>
+
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>Create an initial context to perform the JNDI lookup.</li>
<pre class="prettyprint">
Modified: trunk/examples/jms/delayed-redelivery/readme.html
===================================================================
--- trunk/examples/jms/delayed-redelivery/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/delayed-redelivery/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -6,7 +6,7 @@
<script type="text/javascript"
src="../../common/prettify.js"></script>
</head>
<body onload="prettyPrint()">
- <h1>HornetQ Delayed Redelivery Example</h1>
+ <h1>Delayed Redelivery Example</h1>
<p>This example demonstrates how HornetQ can be configured to provide a
delayed redelivery in the case
a message needs to be redelivered.</p>
Modified: trunk/examples/jms/divert/readme.html
===================================================================
--- trunk/examples/jms/divert/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/divert/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -6,8 +6,8 @@
<script type="text/javascript"
src="../../common/prettify.js"></script>
</head>
<body onload="prettyPrint()">
- <h1>HornetQ Divert Example</h1>
- <br>
+ <h1>Divert Example</h1>
+
<p>HornetQ diverts allow messages to be transparently "diverted"
from one address to another
with just some simple configuration defined on the server side.</p>
<p>Diverts can be defined to be <b>exclusive</b> or
<b>non-exclusive</b>.</p>
@@ -95,7 +95,7 @@
</pre>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>Create an initial context to perform the JNDI lookup on the London
server</li>
<pre class="prettyprint">
Modified: trunk/examples/jms/durable-subscription/readme.html
===================================================================
--- trunk/examples/jms/durable-subscription/readme.html 2010-01-08 11:02:17 UTC (rev
8777)
+++ trunk/examples/jms/durable-subscription/readme.html 2010-01-08 13:44:27 UTC (rev
8778)
@@ -7,14 +7,14 @@
</head>
<body onload="prettyPrint()">
<h1>JMS Durable Subscription Example</h1>
- <br>
+
<p>This example shows you how to use a durable subscription with
HornetQ.</p>
<p>Durable subscriptions are a standard part of JMS, please consult the JMS
1.1 specification for full details.</p>
<p>Unlike non durable subscriptions, the key function of durable subscriptions
is that the messages contained in them persist longer than the lifetime of the subscriber
- i.e. they will accumulate messages sent to the topic even if there is no active
subscriber on them. They will also survive server restarts. Note that for the messages to
be persisted, the messages sent to them must be marked as persistent messages.</p>
- <br>
+
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>client-jndi.properties</code> file in the
directory <code>../common/config</code></li>
<pre class="prettyprint">
@@ -78,10 +78,10 @@
</pre>
<li>We create and send another text message, message 2, to the same
topic</li>
- <pre class="prettyprint">
- <code>TextMessage message2 = session.createTextMessage("This is a
text message 2");</code>
- <br>
- <code>messageProducer.send(message2);</code>
+ <pre class="prettyprint">
+ <code>TextMessage message2 = session.createTextMessage("This is a
text message 2");
+
+ messageProducer.send(message2);</code>
</pre>
<li>Now we close the subscriber. Since the subscription is durable it will
continue to survive even though there is no subscriber attached to it. At this point you
could even stop and restart the server and the subscription would survive!</li>
Modified: trunk/examples/jms/http-transport/readme.html
===================================================================
--- trunk/examples/jms/http-transport/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/http-transport/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>JMS HTTP Example</h1>
- <br>
+
<p>This example shows you how to configure HornetQ to use HTTP protocol as its
transport layer.</p>
<p>HornetQ supports a variety of network protocols to be its underlying
transport without any specific code change.</p>
@@ -34,10 +34,9 @@
</code>
</pre>
- <br>
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>client-jndi.properties</code> file in the
directory <code>../common/config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/instantiate-connection-factory/readme.html
===================================================================
--- trunk/examples/jms/instantiate-connection-factory/readme.html 2010-01-08 11:02:17 UTC
(rev 8777)
+++ trunk/examples/jms/instantiate-connection-factory/readme.html 2010-01-08 13:44:27 UTC
(rev 8778)
@@ -6,8 +6,7 @@
<script type="text/javascript"
src="../../common/prettify.js"></script>
</head>
<body onload="prettyPrint()">
- <h1>HornetQ JMS Instantiate Connection Factory Example</h1>
- <br>
+ <h1>JMS Instantiate Connection Factory Example</h1>
<p>Usually, JMS Objects such as ConnectionFactory, Queue and Topic instances
are looked up from JNDI
before being used by the client code. This objects are called "administered
objects" in JMS specification
@@ -28,7 +27,7 @@
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>Instead of looking it up from JNDI we directly instantiate the JMS
Queue object. We
pass in the name of the JMS Queue in the constructor. The actual JMS Queue must
already be deployed on
Modified: trunk/examples/jms/interceptor/readme.html
===================================================================
--- trunk/examples/jms/interceptor/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/interceptor/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>JMS Interceptor Example</h1>
- <br>
+
<p>This example shows you how to implement and configure a simple interceptor
with HornetQ.</p>
<p>HornetQ allows an application to use an interceptor to hook into the
messaging system. All that needs to do is to implement the
@@ -41,10 +41,9 @@
to return <code>false</code> that signifies that no more interceptors
are to run or the target
is not to be called. Return <code>false</code> to abort processing of
the packet.</p>
- <br>
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>client-jndi.properties</code> file in the
directory <code>../common/config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/jmx/readme.html
===================================================================
--- trunk/examples/jms/jmx/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/jmx/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>JMX Management Example</h1>
- <br>
+
<p>This example shows how to manage HornetQ using <a
href="http://java.sun.com/javase/technologies/core/mntr-mgmt/javaman...
<h2>Example configuration</h2>
Modified: trunk/examples/jms/large-message/readme.html
===================================================================
--- trunk/examples/jms/large-message/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/large-message/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>Large Message Example</h1>
- <br>
+
<p>This example shows you how to send and receive very large messages with
HornetQ.</p>
<p>HornetQ supports the sending and receiving of huge messages, much larger
than can fit in available RAM
on the client or server. Effectively the only limit to message size is the amount of
disk space you have on the server.</p>
@@ -15,7 +15,7 @@
do a simple socket stream from the sender to the consumer.</p>
<p>In order to do this HornetQ provides an extension to JMS where you can use
an InputStream or OutputStream as the source and destination for your messages. You can
send messages as large as it would fit in your disk.</p>
<p>You may also choose to read LargeMessages using the regular ByteStream or
ByteMessage methods, but using the InputStream and OutputStream will provide you a much
better performance</p>
- <br>
+
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
<p>In this example we limit both the server and the client to be running in a
maximum of 50MB of RAM,
@@ -26,7 +26,7 @@
a FileInputStream on that file and set that InputStream as the body of the message
before sending.</p>
<p>The message is sent, then we stop the server, and restart it. This
demonstrates the large message will survive a restart of the server.</p>
<p>Once the server is restarted we receive the message and stream it's
body to another file on disk.</p>
- <br>
+
<ol>
<li>Create an initial context to perform the JNDI lookup.</li>
<pre class="prettyprint">
Modified: trunk/examples/jms/last-value-queue/readme.html
===================================================================
--- trunk/examples/jms/last-value-queue/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/last-value-queue/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -6,7 +6,7 @@
<script type="text/javascript"
src="../../common/prettify.js"></script>
</head>
<body onload="prettyPrint()">
- <h1>Last Value Queue Example</h1>
+ <h1>Last-Value Queue Example</h1>
<p>This example shows you how to define and deal with last-value
queues.</p>
<p>Last-Value queues are special queues which discard any messages when a
newer message with the same value for a well-defined <em>Last-Value</em>
property is put in the queue.
Modified: trunk/examples/jms/management/readme.html
===================================================================
--- trunk/examples/jms/management/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/management/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -6,7 +6,7 @@
<script type="text/javascript"
src="../../common/prettify.js"></script>
</head>
<body onload="prettyPrint()">
- <h1> Management Example</h1>
+ <h1>Management Example</h1>
<p>This example shows how to manage HornetQ using JMS Messages to invoke
management operations on the server.</a></p>
<p>To manage HornetQ using JMX, see the <a
href="../jmx/readme.html">JMX</a> example.</p>
Modified: trunk/examples/jms/message-group/readme.html
===================================================================
--- trunk/examples/jms/message-group/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/message-group/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>Message Group Example</h1>
- <br>
+
<p>This example shows you how to configure and use message groups with
HornetQ.</p>
<p>Message groups are sets of messages that has the following characteristics:
</p>
@@ -25,10 +25,9 @@
will be picked to create a message group. <em>Every messages</em>
sent by a producer created from this connection factory will automatically
be part of this message group.</p>
- <br>
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>client-jndi.properties</code> file in the
directory <code>../common/config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/message-group2/readme.html
===================================================================
--- trunk/examples/jms/message-group2/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/message-group2/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>Message Group Example</h1>
- <br>
+
<p>This example shows you how to configure and use message groups via a
connection factory with HornetQ.</p>
<p>Message groups are sets of messages that has the following characteristics:
</p>
@@ -23,10 +23,8 @@
will be picked to create a message group. <em>Every messages</em>
sent by a producer created from this connection factory will automatically
be part of this message group.</p>
- <br>
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>client-jndi.properties</code> file in the
directory <code>../common/config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/message-priority/readme.html
===================================================================
--- trunk/examples/jms/message-priority/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/message-priority/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>JMS Message Priority Example</h1>
- <br>
+
<p>This example shows how messages with priorities are delivered.</p>
<p>Message Priority carries the delivery preference of messages. It can be
retrieved by the message's
@@ -24,10 +24,9 @@
is also received ahead of the message first sent, but behind the third message. The
first message, regardless
of its being sent first, arrives last.</p>
- <br>
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>client-jndi.properties</code> file in the
directory <code>../common/config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/no-consumer-buffering/readme.html
===================================================================
--- trunk/examples/jms/no-consumer-buffering/readme.html 2010-01-08 11:02:17 UTC (rev
8777)
+++ trunk/examples/jms/no-consumer-buffering/readme.html 2010-01-08 13:44:27 UTC (rev
8778)
@@ -6,8 +6,8 @@
<script type="text/javascript"
src="../../common/prettify.js"></script>
</head>
<body onload="prettyPrint()">
- <h1>HornetQ <br>No Consumer Buffering Example</h1>
- <br><br>
+ <h1>No Consumer Buffering Example</h1>
+
<p>By default, HornetQ consumers buffer messages from the server in a client
side buffer
before you actually receive them on the client side.</p>
<p>This improves performance since otherwise every time you called receive()
or had processed the last
@@ -50,9 +50,9 @@
are consumed in the order they were sent.</p>
<p>If the messages had been buffered in each consumer they would not be
available to be consumed
in an order determined afer delivery.</p>
- <br>
+
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>Create an initial context to perform the JNDI lookup.</li>
<pre class="prettyprint">
Modified: trunk/examples/jms/non-transaction-failover/readme.html
===================================================================
--- trunk/examples/jms/non-transaction-failover/readme.html 2010-01-08 11:02:17 UTC (rev
8777)
+++ trunk/examples/jms/non-transaction-failover/readme.html 2010-01-08 13:44:27 UTC (rev
8778)
@@ -23,7 +23,6 @@
<p>In this example, the live server is server 1, and the backup server is
server 0</p>
<p>The connection will initially be created to server1, server 1 will crash,
and the client will carry on
seamlessly on server 0, the backup server.</p>
- <br>
<ol>
<li>Get an initial context for looking up JNDI from server #1.</li>
<pre class="prettyprint">
Modified: trunk/examples/jms/paging/readme.html
===================================================================
--- trunk/examples/jms/paging/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/paging/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,17 +7,17 @@
</head>
<body onload="prettyPrint()">
<h1>Paging Example</h1>
- <br>
+
<p>This example shows how HornetQ would avoid running out of resources by
paging messages.</p>
<p>A maxSize could be specified per Destination on the destinations settings
(hornetq-configuration.xml).</p>
<p>When the buffered messages are consuming too much memory, HornetQ starts
writing messages on the file-system, and as the memory is released by message
acknowledgement or transaction commits those messages are recovered from disk and placed
in memory</p>
<p>Acknowledgement plays an important factor on paging as messages will stay
on the file system until the memory is released</p>
<p>A Queue is used to send messages point to point, from a producer to a
consumer. The queue guarantees message ordering between these 2 points.</p>
- <br>
+
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>client-jndi.properties</code> file in the
directory <code>../common/config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/pre-acknowledge/readme.html
===================================================================
--- trunk/examples/jms/pre-acknowledge/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/pre-acknowledge/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -6,8 +6,8 @@
<script type="text/javascript"
src="../../common/prettify.js"></script>
</head>
<body onload="prettyPrint()">
- <h1>HornetQ JMS Pre-Acknowledge Example</h1>
- <br>
+ <h1>JMS Pre-Acknowledge Example</h1>
+
<p>Standard JMS supports three acknowledgement modes: AUTO_ACKNOWLEDGE,
CLIENT_ACKNOWLEDGE, and
DUPS_OK_ACKNOWLEDGE. For a full description on these modes please consult the JMS
specification, or any
JMS tutorial.</p>
@@ -28,7 +28,7 @@
<code>HornetQSession.PRE_ACKNOWLEDGE</code>.
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>Create an initial context to perform the JNDI lookup.</li>
<pre class="prettyprint">
Modified: trunk/examples/jms/producer-rate-limit/readme.html
===================================================================
--- trunk/examples/jms/producer-rate-limit/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/producer-rate-limit/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -6,8 +6,8 @@
<script type="text/javascript"
src="../../common/prettify.js"></script>
</head>
<body onload="prettyPrint()">
- <h1>HornetQ JMS Message Producer Rate Limiting</h1>
- <br>
+ <h1>JMS Message Producer Rate Limiting</h1>
+
<p>With HornetQ you can specify a maximum send rate at which a JMS
MessageProducer will send messages.
This can be specified when creating or deploying the connection factory. See
<code>hornetq-jms.xml</code></p>
<p>If this value is specified then HornetQ will ensure that messages are never
produced at a rate higher than
@@ -32,9 +32,9 @@
</pre>
<p>We then simply send as many messages as we can in 10 seconds and note how
many messages are actually sent.</p>
<p>We note that the number of messages sent per second never exceeds the
specified value of <code>50</code> messages per second.</p>
- <br>
+
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>Create an initial context to perform the JNDI lookup.</li>
<pre class="prettyprint">
Modified: trunk/examples/jms/queue/readme.html
===================================================================
--- trunk/examples/jms/queue/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/queue/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,14 +7,14 @@
</head>
<body onload="prettyPrint()">
<h1>JMS Queue Example</h1>
- <br>
+
<p>This example shows you how to send and receive a message to a JMS Queue
with HornetQ.</p>
<p>Queues are a standard part of JMS, please consult the JMS 1.1 specification
for full details.</p>
<p>A Queue is used to send messages point to point, from a producer to a
consumer. The queue guarantees message ordering between these 2 points.</p>
- <br>
+
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>client-jndi.properties</code> file in the
directory <code>../common/config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/queue-message-redistribution/readme.html
===================================================================
--- trunk/examples/jms/queue-message-redistribution/readme.html 2010-01-08 11:02:17 UTC
(rev 8777)
+++ trunk/examples/jms/queue-message-redistribution/readme.html 2010-01-08 13:44:27 UTC
(rev 8778)
@@ -6,8 +6,8 @@
<script type="text/javascript"
src="../../common/prettify.js"></script>
</head>
<body onload="prettyPrint()">
- <h1>HornetQ Message Redistribution Example</h1>
- <br>
+ <h1>Message Redistribution Example</h1>
+
<p>This example demonstrates message redistribution between queues with the
same name deployed in different
nodes of a cluster.</p>
<p>As demontrated in the clustered queue example, if queues with the same name
are deployed on different nodes of
@@ -37,7 +37,6 @@
section of the user manual.</p>
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
<ol>
<li>Get an initial context for looking up JNDI from server 0</li>
<pre class="prettyprint">
Modified: trunk/examples/jms/queue-requestor/readme.html
===================================================================
--- trunk/examples/jms/queue-requestor/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/queue-requestor/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>JMS QueueRequestor Example</h1>
- <br>
+
<p>This example shows you how to use a <a
href="http://java.sun.com/javaee/5/docs/api/javax/jms/QueueRequestor...
with HornetQ.</p>
<p>JMS is mainly used to send messages asynchronously so that the producer of
a message is not waiting for the result of the message consumption.
However, there are cases where it is necessary to have a synchronous behavior:
the code sending a message requires a reply for this message
@@ -20,11 +20,11 @@
<dt><code>QueueRequestorExample</code></dt>
<dd>A JMS Client which uses a QueueRequestor to send text requests to a
queue and receive replies with the reversed text in a synchronous fashion</dd>
</dl>
+
-
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory from JNDI. This initial context will get it's properties from the
<code>client-jndi.properties</code> file in the directory
<code>../common/config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/queue-selector/readme.html
===================================================================
--- trunk/examples/jms/queue-selector/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/queue-selector/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>JMS Queue Selector Example</h1>
- <br>
+
<p>This example shows you how to selectively consume messages using message
selectors with queue consumers.</p>
<p>Message selectors are strings with special syntax that can be used in
creating consumers. Message consumers
@@ -28,10 +28,10 @@
consume the first message delivered, therefore there is no chance for the next
consumer to get the message, even if it
matches the selector.</p>
- <br>
+
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>client-jndi.properties</code> file in the
directory <code>../common/config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/reattach-node/readme.html
===================================================================
--- trunk/examples/jms/reattach-node/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/reattach-node/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -6,8 +6,8 @@
<script type="text/javascript"
src="../../common/prettify.js"></script>
</head>
<body onload="prettyPrint()">
- <h1>HornetQ JMS Reattach Example</h1>
- <br>
+ <h1>JMS Reattach Example</h1>
+
<p>This example demonstrates how HornetQ connections can be configured to be
resilient to
temporary network failures.</p>
<p>In the case of a network failure being detected, either as a result of a
failure to read/write to the connection,
@@ -30,10 +30,9 @@
<p>For more details on how to configure this and for clustering in general
please consult the HornetQ user manual.</p>
- <br>
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>Create an initial context to perform the JNDI lookup.</li>
<pre class="prettyprint">
Modified: trunk/examples/jms/request-reply/readme.html
===================================================================
--- trunk/examples/jms/request-reply/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/request-reply/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,17 +7,17 @@
</head>
<body onload="prettyPrint()">
<h1>JMS Request-Reply Example</h1>
- <br>
+
<p>This example shows you how to handle a request message and receive a reply.
To get a reply message, the requesting client creates a temporary queue. Then it sends out
the request message with JMSReplyTo set to the temporary queue. The request message is
handled by a SimpleRequestServer, who is listening to the request queue for incoming
requests. If a request message has arrived, it extracts the reply queue from the request
message by JMSReplyTo header, and sends back a reply message. To let the client know to
which request message a reply message is related, the server also set the JMSCorrelationID
with the request message's JMSMessageID header to the reply message.</p>
<p>Of course, in a real world example you would re-use the session, producer,
consumer and temporary queue and not create a new one for each message!
Or better still use the correlation id, and just store the requests in a map, then you
don't need a temporary queue at all
<p>Request/Reply style messaging is supported through standard JMS message
headers JMSReplyTo and JMSCorrelationID. This is often used in request-reply style
communications between applications.
Whenever a client sends a message that expects a response, it can use this mechanism
to implement. please consult the JMS 1.1 specification for full details.</p>
- <br>
+
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>We start the request server</li>
Modified: trunk/examples/jms/scheduled-message/readme.html
===================================================================
--- trunk/examples/jms/scheduled-message/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/scheduled-message/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>JMS Scheduled Message Example</h1>
- <br>
+
<p>This example shows you how to send a scheduled message to a JMS Queue with
HornetQ.</p>
<p>A Scheduled Message is a message that will be delivered at a time specified
by the sender. To do this,
simply set a HDR_SCHEDULED_DELIVERY_TIME header property. The value of the property
should be the time of
@@ -15,10 +15,10 @@
<p>In this example, a message is created with the scheduled delivery time set
to 5 seconds after.</p>
- <br>
+
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>client-jndi.properties</code> file in the
directory <code>../common/config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/security/readme.html
===================================================================
--- trunk/examples/jms/security/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/security/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>JMS Security Example</h1>
- <br>
+
<p>This example shows you how configure and use security with
HornetQ.</p>
<p>With security properly configured, HornetQ can restrict client access to
its resouces, including
@@ -111,10 +111,10 @@
check out the hornetq-beans.xml for how to do. In this example we just use the basic
HornetQSecurityManagerImpl which reads users/roles/passwords from the xml
file <code>hornetq-users.xml</code>.
- <br>
+
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>client-jndi.properties</code> file in the
directory <code>../common/config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/send-acknowledgements/readme.html
===================================================================
--- trunk/examples/jms/send-acknowledgements/readme.html 2010-01-08 11:02:17 UTC (rev
8777)
+++ trunk/examples/jms/send-acknowledgements/readme.html 2010-01-08 13:44:27 UTC (rev
8778)
@@ -7,18 +7,18 @@
</head>
<body onload="prettyPrint()">
<h1>Asynchronous Send Acknowledgements Example</h1>
- <br>
+
<p>Asynchronous Send Acknowledgements are an advanced feature of HornetQ which
allow you to
receive acknowledgements that messages were successfully received at the server in a
separate stream
to the stream of messages being sent to the server.<p/>
<p>In this example we create a normal JMS session, then set a
SendAcknowledgementHandler on the JMS
session's underlying core session. We send many messages to the server without
blocking, and asynchronously
the server calls the handler when it has successfully received each message.
- <br>
+
<p>For more information on Asynchronous Send Acknowledgements please see the
user manual</p>
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>client-jndi.properties</code> file in the
directory <code>../common/config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/ssl-enabled/readme.html
===================================================================
--- trunk/examples/jms/ssl-enabled/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/ssl-enabled/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>JMS SSL Example</h1>
- <br>
+
<p>This example shows you how to configure SSL with HornetQ to send and
receive message. </p>
<p>Using SSL can make your messaging applications interact with HornetQ
service securely. An application can
@@ -47,10 +47,10 @@
<p>In the configuration, the hornetq.example.keystore is the key store file
holding client certificate. The hornetq.example.truststore
is the file for server to hold trusted client certificates. They are pre-generated
for illustration purpose<a id="fnr1"
href="#fn1"><sup>1</sup></a>.</p>
- <br>
+
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>client-jndi.properties</code> file in the
directory <code>../common/config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/static-selector/readme.html
===================================================================
--- trunk/examples/jms/static-selector/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/static-selector/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>Static Message Selector Example</h1>
- <br>
+
<p>This example shows you how to configure a HornetQ queue with static message
selectors (filters)
(to configure a static selector directly on a <em>JMS</em> queue,
please see the
<a href="../static-selector-jms/readme.html">static-selector-jms
example</a>).</p>
@@ -34,10 +34,10 @@
is created to receive messages from the queue. Of the five sent messages, two are of
'red' color properties, one is 'blue',
one is 'green' and one has not the 'color' propery at all. The
result is that the consumer only gets the two 'red' messages.</p>
- <br>
+
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>client-jndi.properties</code> file in the
directory <code>../common/config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/static-selector-jms/readme.html
===================================================================
--- trunk/examples/jms/static-selector-jms/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/static-selector-jms/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>Static Message Selector Example</h1>
- <br>
+
<p>This example shows you how to configure a JMS queue with static message
selectors (filters).</p>
<p>Static message selectors are HornetQ's extension to message selectors
as defined in JMS spec 1.1.
@@ -32,10 +32,10 @@
and one has not the <code>color</code> property at all. The result is
that the consumer only gets the two messages
with the <code>'red'</code> color.</p>
- <br>
+
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>client-jndi.properties</code> file in the
directory <code>../common/config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/symmetric-cluster/readme.html
===================================================================
--- trunk/examples/jms/symmetric-cluster/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/symmetric-cluster/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -6,8 +6,8 @@
<script type="text/javascript"
src="../../common/prettify.js"></script>
</head>
<body onload="prettyPrint()">
- <h1>HornetQ Symmetric Cluster Example</h1>
- <br>
+ <h1>JMS Symmetric Cluster Example</h1>
+
<p>This examples demonstrates a <b>symmetric cluster</b> set-up
with HornetQ.</p>
<p>HornetQ has extremely flexible clustering which allows you to set-up
servers in
many different topologies.</p>
@@ -49,7 +49,7 @@
section of the user manual.</p>
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>We instantiate a connection factory directly, specifying the UDP
address and port for discovering
the list of servers in the cluster.
Modified: trunk/examples/jms/temp-queue/readme.html
===================================================================
--- trunk/examples/jms/temp-queue/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/temp-queue/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,13 +7,13 @@
</head>
<body onload="prettyPrint()">
<h1>JMS Temporary Queue Example</h1>
- <br>
+
<p>This example shows you how to use a TemporaryQueue object with HornetQ.
First it creates a temporary queue to send and receive a message, then delete it. Then it
creates another temporary queue and tries to use it after its connection is closed -- to
illustrate its scope.</p>
<p>TemporaryQueue is a JMS queue that lives within lifetime of its connection.
It is often used in request-reply type messaging where the reply is sent through a
temporary destination. The temporary queue is often created as a server resource, so after
using, the user should call delete() method to release the resources. Please consult the
JMS 1.1 specification for full details.</p>
- <br>
+
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory from JNDI. This initial context will get it's properties from the
<code>client-jndi.properties</code> file in the directory
<code>../common/config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/topic/readme.html
===================================================================
--- trunk/examples/jms/topic/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/topic/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,14 +7,14 @@
</head>
<body onload="prettyPrint()">
<h1>JMS Topic Example</h1>
- <br>
+
<p>This example shows you how to send and receive a message to a JMS Topic
with HornetQ.</p>
<p>Topics are a standard part of JMS, please consult the JMS 1.1 specification
for full details.</p>
<p>A Topic is used to send messages using the publish-subscribe model, from a
producer to 1 or more consumers.</p>
- <br>
+
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>client-jndi.properties</code> file in the
directory <code>../common/config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/topic-hierarchies/readme.html
===================================================================
--- trunk/examples/jms/topic-hierarchies/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/topic-hierarchies/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -6,8 +6,8 @@
<script type="text/javascript"
src="../../common/prettify.js"></script>
</head>
<body onload="prettyPrint()">
- <h1>HornetQ Topic Hierarchy Example</h1>
- <br>
+ <h1>Topic Hierarchy Example</h1>
+
<p>HornetQ supports topic hierarchies. With a topic hierarchy you can register
a subscriber with a wild-card
and that subscriber will receive any messages sent to an address that matches the
wildcard.</p>
<p>HornetQ wild-cards can use the character '#' which means
"match any number of words", and
@@ -51,7 +51,7 @@
and one to the address news.europe.entertainment.</p>
<p>We will verify that the message sent to news.usa.wrestling does not get
received since it does not match,
but the messages sent to the other two addresses do get received since they
match.</p>
- <br>
+
<ol>
<li>Create an initial context to perform the JNDI
lookup.</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/topic-selector-example1/readme.html
===================================================================
--- trunk/examples/jms/topic-selector-example1/readme.html 2010-01-08 11:02:17 UTC (rev
8777)
+++ trunk/examples/jms/topic-selector-example1/readme.html 2010-01-08 13:44:27 UTC (rev
8778)
@@ -7,14 +7,14 @@
</head>
<body onload="prettyPrint()">
<h1>JMS Topic Selector Example 1</h1>
- <br>
+
<p>This example shows you how to send message to a JMS Topic, and subscribe
them using selectors with HornetQ, also creating 3 non durable subscribers. 2
subscriptions using selectors, and a third one that should receive the complete set of
messages.</p>
<p>Topics and selectors are a standard part of JMS, please consult the JMS 1.1
specification for full details.</p>
<p>A regular subscriber would receive every message sent to the topic, but
when you use a selector you would limit the messages you receive by the logic expression
you choose only getting the messages that will matter to your processing.</p>
- <br>
+
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>client-jndi.properties</code> file in the
directory <code>../common/config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/topic-selector-example2/readme.html
===================================================================
--- trunk/examples/jms/topic-selector-example2/readme.html 2010-01-08 11:02:17 UTC (rev
8777)
+++ trunk/examples/jms/topic-selector-example2/readme.html 2010-01-08 13:44:27 UTC (rev
8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>JMS Topic Selector Example 2</h1>
- <br>
+
<p>This example shows you how to selectively consume messages using message
selectors with topic consumers.</p>
<p>Message selectors are strings with special syntax that can be used in
creating consumers. Message consumers
@@ -21,10 +21,10 @@
only receives messages who have a 'color' string property of
'green' value; and the thrid without a selector, which means it receives all
messages. To illustrate, three messages
with different 'color' property values are created and sent.</p>
- <br>
+
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>client-jndi.properties</code> file in the
directory <code>../common/config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/transaction-failover/readme.html
===================================================================
--- trunk/examples/jms/transaction-failover/readme.html 2010-01-08 11:02:17 UTC (rev
8777)
+++ trunk/examples/jms/transaction-failover/readme.html 2010-01-08 13:44:27 UTC (rev
8778)
@@ -26,7 +26,7 @@
<p>In this example, the live server is server 1, and the backup server is
server 0</p>
<p>The connection will initially be created to server1, server 1 will crash,
and the client will carry on
seamlessly on server 0, the backup server.</p>
- <br>
+
<ol>
<li>Get an initial context for looking up JNDI from server #1.</li>
<pre class="prettyprint">
Modified: trunk/examples/jms/transactional/readme.html
===================================================================
--- trunk/examples/jms/transactional/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/transactional/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,15 +7,15 @@
</head>
<body onload="prettyPrint()">
<h1>JMS Transactional Session Example</h1>
- <br>
+
<p>This example shows you how to use a transactional Session with HornetQ. It
creates a transactional session. At first it sends out two messages and tries to receive
without session commit. Then it commits the sending session and receives only one messages
before it rolls back the receiving session. It then receives all the messages and commits
the session.</p>
<p>Messages can be sent and received over transactional sessions. Messages in
a transactional session will not be sent or acknowledged until the session is committed.
It a session is rolled back, the produced messages will be destroyed and consumed messages
will be recovered. Please consult the JMS 1.1 specification for full details.</p>
- <br>
+
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>client-jndi.properties</code> file in the
directory <code>../common/config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/xa-heuristic/readme.html
===================================================================
--- trunk/examples/jms/xa-heuristic/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/xa-heuristic/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,7 +7,6 @@
</head>
<body onload="prettyPrint()">
<h1>JMS XA Heuristic Example</h1>
- <br>
<p>This example shows you how to make an XA heuristic decision through HornetQ
Management Interface.</p>
<p>A heuristic decision is a unilateral decision to commit or rollback an XA
transaction branch after it has
@@ -24,10 +23,8 @@
<p>This example uses JMX to manipulate transactions in a HornetQ Server. For
details on JMX facilities with HornetQ,
please look at the JMX Example.</p>
- <br>
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>client-jndi.properties</code> file in the
directory <code>../common/config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/xa-receive/readme.html
===================================================================
--- trunk/examples/jms/xa-receive/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/xa-receive/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,7 +7,6 @@
</head>
<body onload="prettyPrint()">
<h1>JMS XA Receive Example</h1>
- <br>
<p>This example shows you how message receiving behaves in an XA transaction
in HornetQ. In an XA
Transaction, only if the associated XAResource are commited, will the messages be
removed from the queue.
Otherwise, the messages maybe redelivered after rollback or during the XA
recovery.</p>
@@ -22,10 +21,9 @@
transaction roll back. The received messages are cancelled back to the queue. Next
we start
a new transaction with the same XAResource enlisted, but this time we commit the
transaction after receiving the
messages. Then we check that no more messages are to be received.</p>
- <br>
+
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>client-jndi.properties</code> file in the
directory <code>../common/config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/xa-send/readme.html
===================================================================
--- trunk/examples/jms/xa-send/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/xa-send/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,7 +7,6 @@
</head>
<body onload="prettyPrint()">
<h1>JMS XA Send Example</h1>
- <br>
<p>This example shows you how message sending behaves in an XA transaction in
HornetQ. In an XA
Transaction, only if the associated XAResource are commited, will the messages be
sent to the queue.
Otherwise, the messages to be sent will be discarded.</p>
@@ -20,10 +19,10 @@
and enlist it in a transaction through its XAResource. We then send two words,
'hello' and 'world', with
the session, let the transaction roll back. The messages are discarded and never be
received. Next we start
a new transaction with the same XAResource, but this time we commit the transaction.
Both messages are received.</p>
- <br>
+
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory</i></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>client-jndi.properties</code> file in the
directory <code>../common/config</code></li>
<pre class="prettyprint">
Modified: trunk/examples/jms/xa-with-jta/readme.html
===================================================================
--- trunk/examples/jms/xa-with-jta/readme.html 2010-01-08 11:02:17 UTC (rev 8777)
+++ trunk/examples/jms/xa-with-jta/readme.html 2010-01-08 13:44:27 UTC (rev 8778)
@@ -7,7 +7,7 @@
</head>
<body onload="prettyPrint()">
<h1>JMS XA with JTA Example</h1>
- <br>
+
<p>This example shows you how to use JTA interfaces to control transactions
with HornetQ. JTA provides
facilities to start and stop a transaction, enlist XA resources into a
transaction.</p>
@@ -22,11 +22,11 @@
a new transaction with the same XAResource enlisted, but this time we commit the
transaction after receiving the
messages. Then we check that no more messages are to be received. In each
transaction a dummy XAResource is also
enlisted to show the transaction processing information.</p>
- <br>
+
<h2>Example step-by-step</h2>
<p><i>To run the example, simply type
<code>./build.sh</code> (or <code>build.bat</code> on windows)
from this directory. It will download the JBoss JTA jars before
it launches the example.</i></p>
- <br>
+
<ol>
<li>First we need to get an initial context so we can look-up the JMS
connection factory and destination objects from JNDI. This initial context will get
it's properties from the <code>client-jndi.properties</code> file in the
directory <code>../common/config</code></li>
<pre class="prettyprint">