[jboss-svn-commits] JBL Code SVN: r8639 - labs/jbossesb/trunk/product/samples/quickstarts

[jboss-svn-commits at lists.jboss.org]

Author: burrsutter
Date: 2007-01-02 16:12:29 -0500 (Tue, 02 Jan 2007)
New Revision: 8639

Modified:
   labs/jbossesb/trunk/product/samples/quickstarts/readme.txt
Log:


Modified: labs/jbossesb/trunk/product/samples/quickstarts/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/readme.txt	2007-01-02 21:03:46 UTC (rev 8638)
+++ labs/jbossesb/trunk/product/samples/quickstarts/readme.txt	2007-01-02 21:12:29 UTC (rev 8639)
@@ -15,17 +15,17 @@
 - Assumes you are running JBossMQ on JBoss Application Server. Other JMS
 solutions should work as well but the configuration files contained in the
 quickstarts are focused on JBossMQ.
-- Ant is required to execute the quickstart samples
-- MySQL is the assumed deployment for the jUDDI registry
+- MySQL is the assumed deployment for the jUDDI registry however if you have properly
+deployed the SAR all RMI-based registrations should work out of the box.
 You should review the the RegistryConfiguration.pdf document 
 for proper setup of jUDDI and change the juddi.properties file accordingly.
-mysql-connector-java-3.1.12-bin.jar is included in each projects "lib" folder
-to allow each service to register itself (by updating the jUDDI MySQL db).
 - The file "esb-quickstart-service.xml" should be dropped into your "deploy"
 directory for your application server if you are using JBossMQ in JBossAS.  This
 will setup the JMS queues for the quickstart samples.
 
-The following is a brief outline of the various quickstarts:
+The following is a brief outline of the various quickstarts. If this is your first
+time working with the JBoss ESB we recommend at least trying "helloworld", "helloworld_action"
+and "more_action".
 
 * helloworld - Uses a JMS Gateway combined with a Listener.  If this is your
 first time using the JBoss ESB then start by exercising this simple 
@@ -34,8 +34,7 @@
 * helloworld_action - Builds on the concepts of the helloworld example but also
 show the use of multiple methods in a given action, how to "chain" action
 invocations into a particular sequence for a listener and how to respond
-(request/reply).  This means of responding via custom JMS code will eventually
-go away but as of 11/27/2006 it is the way to handle the response.
+(request/reply).  This example uses the notification feature.
 
 * more_action - demonstrates numerous tips & tricks to using the JBoss ESB actions. The first option
 shows what happens if you don't specify a "process" attribute.  The second option illustrates how to
@@ -49,22 +48,3 @@
 how a particular message should follow through the various services. This example also shows you that you
 can setup multiple services in a single esb-config.xml.
 
-Rapid Registry Configuration
-These examples require that the jUDDI database be setup properly and that
-the database be accessible from the environment from which the listener is
-executed.  JBoss ESB ships with the SQL configuration scripts needed to setup
-the jUDDI database. Execute the following scripts
-install\jUDDI-registry\sql\mysql\create_database.sql
-install\jUDDI-registry\sql\mysql\insert_publishers.sql
-and then modify the quickstarts\juddi.properties 
-juddi.isUseDataSource=false
-juddi.jdbcDriver=com.mysql.jdbc.Driver
-juddi.jdbcUrl=jdbc:mysql://localhost:3306/juddi
-juddi.jdbcUsername=root
-juddi.jdbcPassword=admin
-# jUDDI DataSource to use
-# juddi.dataSource=java:comp/env/jdbc/MySqlDS
-
-There are times when the listener starts that it fails to register and you'll
-get an exception/stack trace on the console.  Simply stop the listener and
-restart.