9:59 a.m.
Author: ataylor
Date: 2010-01-08 10:59:58 -0500 (Fri, 08 Jan 2010)
New Revision: 8781
Modified:
trunk/examples/jms/embedded/readme.html
trunk/examples/jms/expiry/readme.html
trunk/examples/jms/http-transport/readme.html
trunk/examples/jms/instantiate-connection-factory/readme.html
trunk/examples/jms/last-value-queue/readme.html
trunk/examples/jms/message-group/readme.html
trunk/examples/jms/message-priority/readme.html
Log:
example read me fix take 2
Modified: trunk/examples/jms/embedded/readme.html
===================================================================
--- trunk/examples/jms/embedded/readme.html 2010-01-08 14:44:04 UTC (rev 8780)
+++ trunk/examples/jms/embedded/readme.html 2010-01-08 15:59:58 UTC (rev 8781)
@@ -8,8 +8,9 @@
<body onload="prettyPrint()">
<h1>Embedded JMS Server Example</h1>
- <p>This examples shows how to setup and run an embedded JMS server with
HornetQ.</p>
- <p>HornetQ was designed to use POJOs (Plain Old Java Objects) so that
embedding HornetQ is as simple as instantiating a few objects.</p>
+ <p>This examples shows how to setup and run an embedded JMS server using
HornetQ.</p>
+ <p>HornetQ was designed using POJOs (Plain Old Java Objects) which means
embedding HornetQ in your own application
+ is as simple as instantiating a few objects.</p>
<p>This example does not use any configuration files. The server is
configured using POJOs and can be easily ported to any dependency injection
framework.<br />
We will setup and run a full-fledged JMS server which binds its JMS resources to
JNDI and can be accessed by remote clients.</p>
Modified: trunk/examples/jms/expiry/readme.html
===================================================================
--- trunk/examples/jms/expiry/readme.html 2010-01-08 14:44:04 UTC (rev 8780)
+++ trunk/examples/jms/expiry/readme.html 2010-01-08 15:59:58 UTC (rev 8781)
@@ -8,11 +8,11 @@
<body onload="prettyPrint()">
<h1>JMS Expiration Example</h1>
- <p>This example shows you how to define and deal with message
expiration.</p>
+ <p>This example shows you how to configure HornetQ so messages are expipired
after a certain time..</p>
<p>Messages can be retained in the messaging system for a limited period of
time before being removed.
JMS specification states that clients should not receive messages that have been
expired (but it does not guarantee this will not happen).</p>
- <p>HornetQ can assign a <em>expiry destination</em> to a given
queue so that when messages are expired, they are removed from the queue and sent
- to the expiry destination. These "expired" messages can later be
consumed from the expiry destination for further inspection.
+ <p>HornetQ can assign a <em>expiry address</em> to a given queue
so that when messages are expired, they are removed from the queue and
+ routed to an this address. These "expired" messages can later be
consumed for further inspection.
<p>
The example will send 1 message with a short <em>time-to-live</em>
to a queue. We will wait for the message to expire and checks that the message
is no longer in the queue it was sent to.
Modified: trunk/examples/jms/http-transport/readme.html
===================================================================
--- trunk/examples/jms/http-transport/readme.html 2010-01-08 14:44:04 UTC (rev 8780)
+++ trunk/examples/jms/http-transport/readme.html 2010-01-08 15:59:58 UTC (rev 8781)
@@ -8,7 +8,7 @@
<body onload="prettyPrint()">
<h1>JMS HTTP Example</h1>
- <p>This example shows you how to configure HornetQ to use HTTP protocol as its
transport layer.</p>
+ <p>This example shows you how to configure HornetQ to use the 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>
Modified: trunk/examples/jms/instantiate-connection-factory/readme.html
===================================================================
--- trunk/examples/jms/instantiate-connection-factory/readme.html 2010-01-08 14:44:04 UTC
(rev 8780)
+++ trunk/examples/jms/instantiate-connection-factory/readme.html 2010-01-08 15:59:58 UTC
(rev 8781)
@@ -8,7 +8,7 @@
<body onload="prettyPrint()">
<h1>JMS Instantiate Connection Factory Example</h1>
- <p>Usually, JMS Objects such as ConnectionFactory, Queue and Topic instances
are looked up from JNDI
+ <p>Usually, JMS Objects such as ConnectionFactories, 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
terminology.</p>
<p>However, in some cases a JNDI server may not be available or desired. To
come to the rescue HornetQ
@@ -16,10 +16,10 @@
<p>This allows the full set of JMS functionality to be available without
requiring a JNDI server!</p>
<p>This example is very simple and based on the simple Queue example, however
in this example we
instantiate the JMS Queue and ConnectionFactory objects directly.</p>
- <p>A wide variety of constructors are available for instantiating
ConnectionFactory objects. In this example
- we use a simple constructor which just takes the server connection details so it
knows where to make the
+ <p>A wide variety of methods are available for instantiating ConnectionFactory
objects. In this example
+ we use a simple method which just takes the server connection details so it knows
where to make the
connection to.</p>
- <p>Other constructors are avilable so all the connection factory parameters
can be specified
+ <p>Other methods are available so all the connection factory parameters can be
specified
including specifying UDP discovery so the client does not need hard-wired knowledge
of where the servers
are that it wishes to connect to, or for specifying live-backup pairs of servers for
failover.</p>
<p>For more information on instantiating ConnectionFactories directly please
consult the user manual and
Modified: trunk/examples/jms/last-value-queue/readme.html
===================================================================
--- trunk/examples/jms/last-value-queue/readme.html 2010-01-08 14:44:04 UTC (rev 8780)
+++ trunk/examples/jms/last-value-queue/readme.html 2010-01-08 15:59:58 UTC (rev 8781)
@@ -8,7 +8,7 @@
<body onload="prettyPrint()">
<h1>Last-Value Queue Example</h1>
- <p>This example shows you how to define and deal with last-value
queues.</p>
+ <p>This example shows you how to configure and use 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.
In other words, a Last-Value queue only retains the last value.</p>
<p>A typical example for Last-Value queue is for stock prices, where you are
only interested by the latest value for a particular stock.</p>
Modified: trunk/examples/jms/message-group/readme.html
===================================================================
--- trunk/examples/jms/message-group/readme.html 2010-01-08 14:44:04 UTC (rev 8780)
+++ trunk/examples/jms/message-group/readme.html 2010-01-08 15:59:58 UTC (rev 8781)
@@ -13,7 +13,7 @@
<p>Message groups are sets of messages that has the following characteristics:
</p>
<li>Messages in a message group share the same group id, i.e. they have same
JMSXGroupID string property values.</li>
<li>Messages in a message group will be all delivered to no more than one of
the queue's consumers. The consumer that receives the
- first message of a group will receive all the messages that belongs to the
group.</li>
+ first message of a group will receive all the messages that belong to the
group.</li>
<p>You can make any message belong to a message group by setting its
'JMXGroupID' string property to the group id.
In this example we create a message group 'Group-0'. And make such a message
group of 10 messages. It also create two consumers on the queue
Modified: trunk/examples/jms/message-priority/readme.html
===================================================================
--- trunk/examples/jms/message-priority/readme.html 2010-01-08 14:44:04 UTC (rev 8780)
+++ trunk/examples/jms/message-priority/readme.html 2010-01-08 15:59:58 UTC (rev 8781)
@@ -8,9 +8,9 @@
<body onload="prettyPrint()">
<h1>JMS Message Priority Example</h1>
- <p>This example shows how messages with priorities are delivered.</p>
+ <p>This example shows how messages with different priorities are delivered in
different orders.</p>
- <p>Message Priority carries the delivery preference of messages. It can be
retrieved by the message's
+ <p>The Message Priority property carries the delivery preference of sent
messages. It can be set by the message's
standard header field 'JMSPriority' as defined in JMS specification version
1.1. The value is of type
integer, ranging from 0 (the lowest) to 9 (the highest). When messages are being
delivered, their priorities
will effect their order of delivery. Messages of higher priorities will likely be
delivered before those