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

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

Author: tfennelly
Date: 2007-05-04 10:16:15 -0400 (Fri, 04 May 2007)
New Revision: 11678

Modified:
   labs/jbossesb/trunk/product/samples/quickstarts/webservice_bpel/build.xml
   labs/jbossesb/trunk/product/samples/quickstarts/webservice_bpel/readme.txt
Log:
updated readme.txt

Modified: labs/jbossesb/trunk/product/samples/quickstarts/webservice_bpel/build.xml
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/webservice_bpel/build.xml	2007-05-04 12:06:33 UTC (rev 11677)
+++ labs/jbossesb/trunk/product/samples/quickstarts/webservice_bpel/build.xml	2007-05-04 14:16:15 UTC (rev 11678)
@@ -77,7 +77,7 @@
         <echo>7.   Start your favorite SOAP client (e.g. SOAPUI) and load the 'RetailerService' WSDL (http://localhost:18080/active-bpel/services/RetailerService?wsdl).</echo>
         <echo>8.   Load the SOAP client with the sample order in 'bpel/resources/sampleData/submit-order-01.xml'.</echo>
         <echo>9.   Submit the new order using the SOAP UI client.</echo>
-        <echo>10.   View the state of the new process in 'Active Processes' on the BPEL Console.  Will appear as 'Running'.</echo>
+        <echo>10.  View the state of the new process in 'Active Processes' on the BPEL Console.  Will appear as 'Running'.</echo>
         <echo>11.  Drill into the 'Running' OrderProcess process (select it).</echo>
         <echo>12.  Drill down, you will see that the process is waiting on an acknowledgement/notification from the OrderManager service (WaitForNotificationFromOrderManager).</echo>
         <echo>13.  Goto http://localhost:8080/order-manager/ (note, not port '18080').  From here, you can approve the order.</echo>        

Modified: labs/jbossesb/trunk/product/samples/quickstarts/webservice_bpel/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/webservice_bpel/readme.txt	2007-05-04 12:06:33 UTC (rev 11677)
+++ labs/jbossesb/trunk/product/samples/quickstarts/webservice_bpel/readme.txt	2007-05-04 14:16:15 UTC (rev 11678)
@@ -1,19 +1,28 @@
 Overview:
 =========
-   TODO
+   This Quickstart demonsrates how the ActiveBPEL BPEL Engine can be used to
+   orchestrate business process flow through JBoss ESB.
 
+   See docs folder.
 
+Requirements:
+=============
+   This quickstart currently only works on a specific version of JBoss AS (+ EJB3 profile):
+        "Release ID: JBoss [Zion] 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)"
+
+   This is down to the fact that some of the JBossWS components are very new and rely
+   on the version of JBossWS shipped with the above version of the AS.  This issue will
+   be resolved for the 4.2 GA release.
+
+
 Before Running:
 ===============
-1. Update the "jbosshome.dir" property in the quickstarts.properties file in "../".
+1. Update the "jbosshome.dir" property in the quickstarts.properties file in "../conf".
 2. Make sure the jbossesb.sar is deployed on your JBoss Application Server.
    In the ESB "install" folder update deployment.properties and then run "ant".
-   This example does require you to use a version for 4.0.4+ with the EJB3 profile.
-3. Make sure the JBoss Application server is running.
 
 
 To Run:
 =======
-1. In the first command window, execute "ant".  This will compile the project, build
-the needed jars and deploy the ESB archive component to the Application Server.  If you are 
-monitoring the Application Server console you will see it hot deploy the WAR.
+1. Run "ant clean deploy" from this folder and follow the instructions printed to the
+   console at the end of the deploy.