[hornetq-commits] JBoss hornetq SVN: r8787 - in trunk/examples/javaee: jca-config and 3 other directories.

do-not-reply at jboss.org do-not-reply at jboss.org
Mon Jan 11 08:31:00 EST 2010


Author: ataylor
Date: 2010-01-11 08:31:00 -0500 (Mon, 11 Jan 2010)
New Revision: 8787

Modified:
   trunk/examples/javaee/ejb-jms-transaction/readme.html
   trunk/examples/javaee/jca-config/readme.html
   trunk/examples/javaee/jms-bridge/readme.html
   trunk/examples/javaee/mdb-cmt-setrollbackonly/readme.html
   trunk/examples/javaee/mdb-cmt-tx-not-supported/readme.html
Log:
fixed example read me's part 4

Modified: trunk/examples/javaee/ejb-jms-transaction/readme.html
===================================================================
--- trunk/examples/javaee/ejb-jms-transaction/readme.html	2010-01-11 12:15:25 UTC (rev 8786)
+++ trunk/examples/javaee/ejb-jms-transaction/readme.html	2010-01-11 13:31:00 UTC (rev 8787)
@@ -7,10 +7,8 @@
   </head>
   <body onload="prettyPrint()">
      <h1>EJB/JMS Transaction Example</h1>
-     
-     <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:</p>
+     <p>The example application will invoke an EJB which within the JBoss AS (Application Server)  which will:</p>
      <ol>
         <li>send a JMS message</li>
         <li>update a database from the same transaction</li>

Modified: trunk/examples/javaee/jca-config/readme.html
===================================================================
--- trunk/examples/javaee/jca-config/readme.html	2010-01-11 12:15:25 UTC (rev 8786)
+++ trunk/examples/javaee/jca-config/readme.html	2010-01-11 13:31:00 UTC (rev 8787)
@@ -8,13 +8,18 @@
   <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 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-Driven Beans or DataSource integration on the application server.</p>
+     <p>This example is composed of two message-driven beans (MDB), MDBQueueA and MDBQueueB, and a stateless session
+         bean StatelessSender and a main class MDBRemoteClientExample.<p>
+     <p>MDBRemoteClientExample will invoke the StatelessSender bean which will in tirun send a message to 2 queues which
+         will then be consumed by each MDB.</p>
+     <p>MDBQueueA is on the same server as the StatelessSender bean and consumes the message locally.</p>
+     <p>MDBQueueB is on the second server who's JCA Adapter is configured to consume remotely from the first 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-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">

Modified: trunk/examples/javaee/jms-bridge/readme.html
===================================================================
--- trunk/examples/javaee/jms-bridge/readme.html	2010-01-11 12:15:25 UTC (rev 8786)
+++ trunk/examples/javaee/jms-bridge/readme.html	2010-01-11 13:31:00 UTC (rev 8787)
@@ -9,7 +9,7 @@
      <h1>JMS Bridge Example</h1>
      
      <p>This example shows how to configure and run a JMS Bridge in JBoss AS 5.<br />
-         A bridge receives messages from a <em>source</em> JMS destination and resend them to a <em>target</em> destination.</p>
+         A bridge receives messages from a <em>source</em> JMS destination and forwards them to a <em>target</em> destination.</p>
      <p>The source and target destinations can be on different servers, even from different JMS providers. For example, you can use this
          JMS Bridge to bridge a legacy JMS provider to HornetQ during migration.</p>
          
@@ -17,7 +17,7 @@
      <ul>
          <li>the source and target destinations are hosted by a single JBoss AS 5 instance</li>
          <li>the bridge is run on the same JBoss AS 5 instance</li>
-         <li>every time a message is consumed by the bridge from the source, it is resent to the target</li>
+         <li>every time a message is consumed by the bridge from the source, it is forward to the target</li>
          <li>The application client will send a message to the source and consume the "same" message from the target to
              show that the two destinations were indeed bridged.</li>
      </ul>

Modified: trunk/examples/javaee/mdb-cmt-setrollbackonly/readme.html
===================================================================
--- trunk/examples/javaee/mdb-cmt-setrollbackonly/readme.html	2010-01-11 12:15:25 UTC (rev 8786)
+++ trunk/examples/javaee/mdb-cmt-setrollbackonly/readme.html	2010-01-11 13:31:00 UTC (rev 8787)
@@ -10,7 +10,7 @@
 
      <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
+         The example will send deploy a simple MDB and demonstrate sending a message and the MDB consuming it twice
      </p>
      
      <h2>JBoss AS configuration</h2>

Modified: trunk/examples/javaee/mdb-cmt-tx-not-supported/readme.html
===================================================================
--- trunk/examples/javaee/mdb-cmt-tx-not-supported/readme.html	2010-01-11 12:15:25 UTC (rev 8786)
+++ trunk/examples/javaee/mdb-cmt-tx-not-supported/readme.html	2010-01-11 13:31:00 UTC (rev 8787)
@@ -10,7 +10,8 @@
 
      <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.
+         The example will send deploy a simple MDB and demonstrate sending a message and the MDB consuming it but without
+         using a transaction as this MDB does not support them.
      </p>
      
      <h2>JBoss AS configuration</h2>



More information about the hornetq-commits mailing list