5:28 a.m.
Author: jmesnil
Date: 2009-08-21 06:28:06 -0400 (Fri, 21 Aug 2009)
New Revision: 7860
Added:
trunk/examples/common/images/hornetQ-banner_final.png
Removed:
trunk/examples/common/images/title_hdr.png
Modified:
trunk/examples/common/common.css
trunk/examples/core/microcontainer/readme.html
trunk/examples/javaee/ejb-jms-transaction/readme.html
trunk/examples/javaee/hajndi/readme.html
trunk/examples/javaee/jms-bridge/readme.html
trunk/examples/javaee/xarecovery/readme.html
trunk/examples/jms/clustered-durable-subscription/readme.html
trunk/examples/jms/management/readme.html
trunk/examples/jms/message-group/readme.html
trunk/examples/jms/xa-heuristic/readme.html
Log:
update examples' readmes
* added hornet banner
* removed remaining references to JBoss Messaging / JBM
Modified: trunk/examples/common/common.css
===================================================================
--- trunk/examples/common/common.css 2009-08-21 10:04:26 UTC (rev 7859)
+++ trunk/examples/common/common.css 2009-08-21 10:28:06 UTC (rev 7860)
@@ -1,16 +1,24 @@
-h1 {height:89px;
- background: url(./images/title_hdr.png) top left no-repeat;
- vertical-align: middle;
- line-height:89px;
- font-size: 250%;}
+body {
+ background: url(./images/hornetQ-banner_final.png) top left no-repeat;
+}
-pre, code { background-color: lightgrey;
- color:#333; }
-pre {display:block;
- overflow:auto;
- border: dotted grey 1px;}
+h1 {
+ margin-top: 110px;
+ font-size: 250%;
+}
+pre, code {
+ background-color: lightgrey;
+ color:#333;
+}
+
+pre {
+ display:block;
+ overflow:auto;
+ border: dotted grey 1px;
+}
+
.missing-doc {
- background-color: red;
- border: dotted black 1px;
+ background-color: red;
+ border: dotted black 1px;
}
Added: trunk/examples/common/images/hornetQ-banner_final.png
===================================================================
(Binary files differ)
Property changes on: trunk/examples/common/images/hornetQ-banner_final.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: trunk/examples/common/images/title_hdr.png
===================================================================
(Binary files differ)
Modified: trunk/examples/core/microcontainer/readme.html
===================================================================
--- trunk/examples/core/microcontainer/readme.html 2009-08-21 10:04:26 UTC (rev 7859)
+++ trunk/examples/core/microcontainer/readme.html 2009-08-21 10:28:06 UTC (rev 7860)
@@ -4,7 +4,7 @@
<link rel="stylesheet" type="text/css"
href="../../common/common.css"/>
</head>
<body>
- <h1>Example Micro Container</h1>
+ <h1>Micro Container Example</h1>
<br/>
<p>This examples shows how to setup and run HornetQ through the Micro
Container.</p>
<p>Refer to the user's manual for the list of required Jars, since JBoss
Micro Container requires a few jars.</p>
Modified: trunk/examples/javaee/ejb-jms-transaction/readme.html
===================================================================
--- trunk/examples/javaee/ejb-jms-transaction/readme.html 2009-08-21 10:04:26 UTC (rev
7859)
+++ trunk/examples/javaee/ejb-jms-transaction/readme.html 2009-08-21 10:28:06 UTC (rev
7860)
@@ -220,7 +220,7 @@
<h2>More information</h2>
<ul>
- <li><a
href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">JBoss
Messsaging deployment in JBoss AS 5</a></li>
+ <li><a
href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">HornetQ
deployment in JBoss AS 5</a></li>
<li><a
href="http://www.jboss.org/file-access/default/members/jbossas/freez...
Alternative Databases with JBoss AS</a></li>
</ul>
Modified: trunk/examples/javaee/hajndi/readme.html
===================================================================
--- trunk/examples/javaee/hajndi/readme.html 2009-08-21 10:04:26 UTC (rev 7859)
+++ trunk/examples/javaee/hajndi/readme.html 2009-08-21 10:28:06 UTC (rev 7860)
@@ -6,8 +6,8 @@
<body>
<h1>Java EE HAJNDI Example</h1>
<br>
- <p>This example demonstrates the use of High Availability JNDI (HA-JNDI) to
look-up JBoss
- Messaging JMS Connection Factories, Queues and Topics.</p>
+ <p>This example demonstrates the use of High Availability JNDI (HA-JNDI) to
look-up 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>
<p>This means if that server crashes, or is not available you won't be
able to perform lookups.</p>
@@ -16,7 +16,7 @@
<p>With HA-JNDI the client can be simplify configured with UDP address
parameters and can transparently
perform JNDI lookups without having to worry about a particular server being
unavailable.</p>
<p>HA-JNDI is a service of JBoss Application Server and is not available by
default when running against
- a stand-alone HornetQ instance.</>
+ a stand-alone HornetQ instance.</p>
<p>An alternative approach is to avoid JNDI together and directly instantiate
JMS Connection Factory,
Queue and Topic instances on the client side. HornetQ Connection Factory instances
can
also be configured to use UDP discovery so the specific details of the available
servers are
Modified: trunk/examples/javaee/jms-bridge/readme.html
===================================================================
--- trunk/examples/javaee/jms-bridge/readme.html 2009-08-21 10:04:26 UTC (rev 7859)
+++ trunk/examples/javaee/jms-bridge/readme.html 2009-08-21 10:28:06 UTC (rev 7860)
@@ -149,7 +149,7 @@
<h2>More information</h2>
<ul>
- <li><a
href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">JBoss
Messsaging deployment in JBoss AS 5</a></li>
+ <li><a
href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">HornetQ
deployment in JBoss AS 5</a></li>
<li><a
href="../../../docs/user-manual/en/html_single/index.html#jms-bridge">JMS
Bridge configuration</a></li>
</ul>
Modified: trunk/examples/javaee/xarecovery/readme.html
===================================================================
--- trunk/examples/javaee/xarecovery/readme.html 2009-08-21 10:04:26 UTC (rev 7859)
+++ trunk/examples/javaee/xarecovery/readme.html 2009-08-21 10:28:06 UTC (rev 7860)
@@ -29,7 +29,7 @@
is added:</p>
<pre>
<code><property
name="com.arjuna.ats.jta.recovery.XAResourceRecovery.HORNETQ1"
-
value="org.hornetq.jms.server.recovery.MessagingXAResourceRecovery;org.hornetq.core.remoting.impl.invm.InVMConnectorFactory"/></code>
+
value="org.hornetq.jms.server.recovery.HornetQXAResourceRecovery;org.hornetq.core.remoting.impl.invm.InVMConnectorFactory"/></code>
</pre>
<p>This informs the Recovery Manager that it can recovers HornetQ XA Resources
by connecting to the server using an <code>InVMConnectorFactory</code>.
@@ -221,8 +221,8 @@
<h2>More information</h2>
<ul>
- <li><a
href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">JBoss
Messsaging installation in JBoss AS 5</a></li>
- <li><a
href="../../../docs/user-manual/en/html_single/index.html#xa-recovery">JBoss
Messsaging XA Recovery configuration in JBoss AS 5</span></li>
+ <li><a
href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">HornetQ
installation in JBoss AS 5</a></li>
+ <li><a
href="../../../docs/user-manual/en/html_single/index.html#xa-recovery">HornetQ
XA Recovery configuration in JBoss AS 5</span></li>
<li><a href="http://www.jboss.org/jbosstm/">JBoss
Transactions</a></li>
</ul>
Modified: trunk/examples/jms/clustered-durable-subscription/readme.html
===================================================================
--- trunk/examples/jms/clustered-durable-subscription/readme.html 2009-08-21 10:04:26 UTC
(rev 7859)
+++ trunk/examples/jms/clustered-durable-subscription/readme.html 2009-08-21 10:28:06 UTC
(rev 7860)
@@ -8,7 +8,7 @@
<br>
<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 2.0 it's possible to create durable subscription instances
with the same name and client-id
+ however, with HornetQ it's possible to create durable subscription instances
with the same name and client-id
on different nodes of the cluster, and consume from them simultaneously.
This allows the work of processing messages from a durable subscription to be spread
across the cluster in
a similar way to how JMS Queues can be load balanced across the cluster
Modified: trunk/examples/jms/management/readme.html
===================================================================
--- trunk/examples/jms/management/readme.html 2009-08-21 10:04:26 UTC (rev 7859)
+++ trunk/examples/jms/management/readme.html 2009-08-21 10:28:06 UTC (rev 7860)
@@ -72,7 +72,11 @@
<li>We create the JMS management queue. This is a
<em>special</em> queue which is not looked up from JNDI but instantiated
directly</li>
<pre>
+<<<<<<< .mine
<code>Queue managementQueue = new
HornetQQueue("hornetq.management",
"hornetq.management");</code>
+=======
+ <code>Queue managementQueue = new
JBossQueue("hornetq.management", "hornetq.management");</code>
+>>>>>>> .r7829
</pre>
<li>We create a <code>QueueRequestor</code> to send messages to
the management queue and receive replies (see <a
href="../queue-requestor/readme.html">queue-requestor
example</a>)</li>
Modified: trunk/examples/jms/message-group/readme.html
===================================================================
--- trunk/examples/jms/message-group/readme.html 2009-08-21 10:04:26 UTC (rev 7859)
+++ trunk/examples/jms/message-group/readme.html 2009-08-21 10:28:06 UTC (rev 7860)
@@ -18,7 +18,7 @@
where the 10 'Group-0' group messages are to be sent. You can see that with
message grouping enabled, all the 10 messages will be received by
the first consumer. The second consumer will receive none. </p>
- <p>Alternatively, HornetQ's connection factories can be configured to
<em>auto group</em> messages. By setting <code>autogroup</code> to
</code>true</code> on the <code>JBossConnectonFactory</code>
+ <p>Alternatively, HornetQ's connection factories can be configured to
<em>auto group</em> messages. By setting <code>autogroup</code> to
</code>true</code> on the <code>HornetQConnectionFactory</code>
(or setting
<code><autogroup>true</autogroup></code> in
<code>hornetq-jms.xml</code>'s connection factory settings), a random
unique id
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>
@@ -73,10 +73,10 @@
<code>
int msgCount = 10;
TextMessage[] groupMessages = new TextMessage[msgCount];
- for (int i = 0; i < msgCount; i++)
+ for (int i = 0; i < msgCount; i++)
{
groupMessages[i] = session.createTextMessage("Group-0 message " +
i);
- groupMessages[i].setStringProperty(JBossMessage.JMSXGROUPID,
"Group-0");
+ groupMessages[i].setStringProperty(HornetQMessage.JMSXGROUPID,
"Group-0");
groupMessages[i].setIntProperty("JMSXGroupSeq", i + 1);
producer.send(groupMessages[i]);
System.out.println("Sent message: " + groupMessages[i].getText());
Modified: trunk/examples/jms/xa-heuristic/readme.html
===================================================================
--- trunk/examples/jms/xa-heuristic/readme.html 2009-08-21 10:04:26 UTC (rev 7859)
+++ trunk/examples/jms/xa-heuristic/readme.html 2009-08-21 10:28:06 UTC (rev 7860)
@@ -6,7 +6,7 @@
<body>
<h1>JMS XA Heuristic Example</h1>
<br>
- <p>This example shows you how to make an XA heuristic decision through JBoss
Messageing Management Interface.</p>
+ <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
been prepared. </p>
@@ -19,8 +19,8 @@
Then we get the MBeanServerConnection object to manipulate the prepared
transactions. To illustrate, we roll back the first
transaction but commit the second. This will result in that only the message
'world' is received. </p>
- <p>This example uses JMX to manipulate transactions in a HornetQ Server. For
details on JMX facilities with JBoss
- Messaging, please look at the JMX Example.</p>
+ <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>
@@ -170,7 +170,7 @@
<li>We list the prepared transactions</li>
<pre>
<code>
- ObjectName serverObject = ObjectNames.getHornetQServerObjectName();
+ ObjectName serverObject = ObjectNames.getMessagingServerObjectName();
String[] infos = (String[])mbsc.invoke(serverObject,
"listPreparedTransactions", null, null);
System.out.println("Prepared transactions: ");
6177
days inactive
6177
days old
hornetq-commits@lists.jboss.org
0 comments
1 participants
participants (1)
-
do-not-reply＠jboss.org