[jboss-svn-commits] JBL Code SVN: r13184 - labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration2.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Fri Jul 6 15:36:19 EDT 2007
Author: bernard.tison
Date: 2007-07-06 15:36:19 -0400 (Fri, 06 Jul 2007)
New Revision: 13184
Modified:
labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration2/build.xml
labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration2/readme.txt
Log:
JBESB-661
Modified: labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration2/build.xml
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration2/build.xml 2007-07-06 19:27:34 UTC (rev 13183)
+++ labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration2/build.xml 2007-07-06 19:36:19 UTC (rev 13184)
@@ -11,6 +11,12 @@
<import file="../conf/base-build.xml"/>
<property name="project.process.dir" value="processDefinition1"/>
+
+ <target name="quickstart-specific-dependencies">
+ <path id="quickstart-dependencies-classpath">
+ <fileset dir="${product.dir}/services/jbpm/lib/ext/build-time/" includes="bsh.jar"/>
+ </path>
+ </target>
<target name="quickstart-specific-assemblies">
<copy overwrite="true" file="${project.process.dir}/processdefinition.xml" todir="${classes}/${project.process.dir}" />
@@ -27,16 +33,10 @@
<antcall target="deployProcess"/>
</target>
- <target name="runtest">
- <echo>Use "ant deployProcess" followed by "ant startProcess"</echo>
- </target>
+ <target name="runtest">
+ <echo>Use "ant deployProcess" followed by "ant startProcess"</echo>
+ </target>
- <target name="run">
- <echo>"ant run" - the run target is not supported in this example</echo>
- <echo>Use "ant deploy" to get an .esb archive running in either</echo>
- <echo>the ESB Server or the ESB embedded in JBoss Application Server</echo>
- </target>
-
<target name="deployProcess" depends="compile" description="Sends a message to deploy the process definition">
<echo>Sends a message to deploy the process definition</echo>
<java fork="yes" classname="org.jboss.soa.esb.samples.quickstarts.bpm_orchestration2.test.SendJMSMessageDeploy" failonerror="true">
Modified: labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration2/readme.txt
===================================================================
--- labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration2/readme.txt 2007-07-06 19:27:34 UTC (rev 13183)
+++ labs/jbossesb/trunk/product/samples/quickstarts/bpm_orchestration2/readme.txt 2007-07-06 19:36:19 UTC (rev 13184)
@@ -8,14 +8,15 @@
To Run standalone mode:
=======================
-NOTE: This quickstart does NOT presently running in standalone mode. It must be
-executed as a .esb archive in either the ESB Server or JBoss Application Server.
-These steps are listed here for our testing/debugging purposes.
1. Open two command windows in the directory called "bpm_orchestration2"
2. In command window 1, execute "ant deploy-jms-dests"
-3. In command window 1, execute "ant run"
-4. In command window 2, execute "ant deployProcess"
-5. In command window 2, execute "ant startProcess"
+3. In command window 1, execute "ant run" - starts the ESB in standalone mode
+4. In command window 2, execute "ant deployProcess" - sends a message that fires
+a service that loads the process definition from the file system and into the
+repository.
+5. In command window 2, execute "ant startProcess" - this sends a messge that
+causes a new process instance to be created and "signaled", since this process
+definition contains no wait-states it will execute until completion.
To Run '.esb' archive mode:
===========================
More information about the jboss-svn-commits
mailing list