[jboss-svn-commits] JBL Code SVN: r27699 - in labs/jbossesb/trunk/product/samples/quickstarts: bpm_orchestration2 and 2 other directories.

jboss-svn-commits at lists.jboss.org jboss-svn-commits at lists.jboss.org
Tue Jul 7 09:46:07 EDT 2009


Author: beve
Date: 2009-07-07 09:46:07 -0400 (Tue, 07 Jul 2009)
New Revision: 27699

Modified:
   labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration1/readme.txt
   labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration2/readme.txt
   labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration3/readme.txt
   labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration4/deployment.xml
   labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration4/jboss-esb.xml
Log:
Work for https://jira.jboss.org/jira/browse/JBESB-2698 "Verify quickstarts aggregator -> bpm_orchestration4"


Modified: labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration1/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration1/readme.txt	2009-07-07 13:42:30 UTC (rev 27698)
+++ labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration1/readme.txt	2009-07-07 13:46:07 UTC (rev 27699)
@@ -8,10 +8,8 @@
   1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
   2. Open another command terminal window in this folder ("Window2"), type
      'ant deployProcess'.
-  3. Switch back to Application Server console and wait for the message
-     '[SchemaExport] schema export complete' to appear on the console.
-  4. Switch back to "Window2", type 'ant startProcess'.
-  5. Switch back to Application Server console to see the output from the ESB.
+  3. Switch back to "Window2", type 'ant startProcess'.
+  4. Switch back to Application Server console to see the output from the ESB.
   
    Sample Output from "ant startProcess":
     ======================================
@@ -38,9 +36,9 @@
 	12:21:44,375 INFO  [STDOUT] Executed by the process, not by the ESB
 	12:21:44,453 INFO  [MessageSpy] Body: Service 3 Service 2 Service 1 Start It Up
   
-  6. In the http://localhost:8080/jbpm-console, you can check that the "processDefinition2" is
+  5. In the http://localhost:8080/jbpm-console, you can check that the "processDefinition2" is
      deployed and that there is one running instance.
-  7. To undeploy the esb archive, type 'ant undeploy' ("Window1").
+  6. To undeploy the esb archive, type 'ant undeploy' ("Window1").
 
 
 

Modified: labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration2/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration2/readme.txt	2009-07-07 13:42:30 UTC (rev 27698)
+++ labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration2/readme.txt	2009-07-07 13:46:07 UTC (rev 27699)
@@ -11,12 +11,10 @@
   1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
   2. Open another command terminal window in this folder ("Window2"), type
      'ant deployProcess'.
-  3. Switch back to Application Server console and wait for the message
-     'Process Definition Deployed:' to appear on the console.
-  4. In the command terminal window ("Window2"), type 
+  3. In the command terminal window ("Window2"), type 
      'ant startProcess'
-  5. Switch back to Application Server console to see the output from the ESB
-  6. In this folder ("Window1"), type 'ant undeploy'.
+  4. Switch back to Application Server console to see the output from the ESB
+  5. In this folder ("Window1"), type 'ant undeploy'.
 
 Extra Credit:
 =============

Modified: labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration3/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration3/readme.txt	2009-07-07 13:42:30 UTC (rev 27698)
+++ labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration3/readme.txt	2009-07-07 13:46:07 UTC (rev 27699)
@@ -18,7 +18,7 @@
      [STDOUT] Out: Hello start 'Service 1' 
      [STDOUT] ** End Service 1 **
 
-  4. Enter the jBPM console (http://localhost:8080/jbpm-console/sa/processes.jsf), and
+  4. Enter the jBPM console (http://localhost:8080/jbpm-console/app/processes.jsf), and
      login.   Once logged in, examine each process that you see using the "Examine" link 
      and find the "Instance ID" for the process that has a Key of "Demo1". 
      
@@ -74,8 +74,8 @@
 	It goes to sleep and waits some external "signal" event occurs.  A waiting/sleeping
 	process instance is held in the database. 
 	
-	Please review the document called:  jBPMIntegrationGuide.pdf
-	http://anonsvn.labs.jboss.com/labs/jbossesb/branches/JBESB_4_2_1_GA_CP/product/docs/services/jBPMIntegrationGuide.pdf
+	Please review the "jBPM Integration" chapter in the document called: ServicesGuide.pdf
+	http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/docs/ServicesGuide.pdf
 	
 	Tip: If you use the jbpm-console (http://localhost:8080) and the Graphical Process
 	Designer provided by Red Hat Developer Studio then you can visually "see" the process

Modified: labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration4/deployment.xml
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration4/deployment.xml	2009-07-07 13:42:30 UTC (rev 27698)
+++ labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration4/deployment.xml	2009-07-07 13:46:07 UTC (rev 27699)
@@ -3,4 +3,20 @@
   <depends>jboss.esb:deployment=jbrules.esb</depends>
   <depends>jboss.esb:deployment=jbpm.esb</depends>
   <depends>jboss.esb:deployment=smooks.esb</depends>
-</jbossesb-deployment>
\ No newline at end of file
+  <depends>jboss.messaging.destination:service=Queue,name=quickstart_bpm_orchestration4_start_esb</depends>
+  <depends>jboss.messaging.destination:service=Queue,name=quickstart_bpm_orchestration4_start_gw</depends>
+  <depends>jboss.messaging.destination:service=Queue,name=quickstart_bpm_orchestration4_start_sync_esb</depends>
+  <depends>jboss.messaging.destination:service=Queue,name=quickstart_bpm_orchestration4_start_sync_esb_reply</depends>
+  <depends>jboss.messaging.destination:service=Queue,name=quickstart_bpm_orchestration4_query_sync_esb</depends>
+  <depends>jboss.messaging.destination:service=Queue,name=quickstart_bpm_orchestration4_query_sync_esb_reply</depends>
+  <depends>jboss.messaging.destination:service=Queue,name=quickstart_bpm_orchestration4_intake_service_esb</depends>
+  <depends>jboss.messaging.destination:service=Queue,name=quickstart_bpm_orchestration4_intake_service_esb_reply</depends>
+  <depends>jboss.messaging.destination:service=Queue,name=quickstart_bpm_orchestration4_discount_service_esb</depends>
+  <depends>jboss.messaging.destination:service=Queue,name=quickstart_bpm_orchestration4_discount_service_esb_reply</depends>
+  <depends>jboss.messaging.destination:service=Queue,name=quickstart_bpm_orchestration4_shipping_service_esb</depends>
+  <depends>jboss.messaging.destination:service=Queue,name=quickstart_bpm_orchestration4_shipping_service_esb_reply</depends>
+  <depends>jboss.messaging.destination:service=Queue,name=quickstart_bpm_orchestration4_monitor</depends>
+  <depends>jboss.messaging.destination:service=Queue,name=quickstart_bpm_orchestration4_ConciergeManager</depends>
+  <depends>jboss.messaging.destination:service=Queue,name=quickstart_bpm_orchestration4_DistributionManager</depends>
+  <depends>jboss.messaging.destination:service=Queue,name=quickstart_bpm_orchestration4_BasicShipping</depends>
+</jbossesb-deployment>

Modified: labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration4/jboss-esb.xml
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration4/jboss-esb.xml	2009-07-07 13:42:30 UTC (rev 27698)
+++ labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration4/jboss-esb.xml	2009-07-07 13:46:07 UTC (rev 27699)
@@ -65,7 +65,7 @@
 				<jms-listener name="ESB-Listener"
 					busidref="startEsbChannel"/>
 			</listeners>
-				<actions>
+				<actions mep="OneWay">
 				<action name="setup_key"
 						class="org.jboss.soa.esb.actions.scripting.GroovyActionProcessor">
 						<property name="script"
@@ -85,7 +85,7 @@
 				</action>
 				<action name="dump2" class="org.jboss.soa.esb.actions.SystemPrintln">
 					<property name="message" value="After" />
-					<property name="printfull" value="true"/>
+					<property name="printfull" value="false"/>
 				</action>
 			</actions>
 		</service>
@@ -114,7 +114,7 @@
                 </action>
                 <action name="dump2" class="org.jboss.soa.esb.actions.SystemPrintln">
                     <property name="message" value="After" />
-                    <property name="printfull" value="true"/>
+                    <property name="printfull" value="false"/>
                 </action>
             </actions>
         </service>
@@ -149,7 +149,7 @@
 				
 				<action name="dump1" class="org.jboss.soa.esb.actions.SystemPrintln">
 					<property name="message" value="INTAKE START" />
-					<property name="printfull" value="true"/>
+					<property name="printfull" value="false"/>
 				</action>
 				
 				<action name="groovy"
@@ -159,7 +159,7 @@
 				</action>
 				
 				<action name="dump" class="org.jboss.soa.esb.actions.SystemPrintln">
-					<property name="printfull" value="true"/>
+					<property name="printfull" value="false"/>
 				</action>
 
         <action name="capture-original-message" class="org.jboss.soa.esb.actions.scripting.GroovyActionProcessor">




More information about the jboss-svn-commits mailing list