Author: kidz
Date: Tue Aug 2 07:23:13 2005
New Revision: 227013
URL: http://svn.apache.org/viewcvs?rev=227013&view=rev
Log:
Added state changes picture
Modified:
webservices/muse/trunk/src/examples/enterprise/Muse_Example.htm
Modified: webservices/muse/trunk/src/examples/enterprise/Muse_Example.htm
URL:
http://svn.apache.org/viewcvs/webservices/muse/trunk/src/examples/enterprise/Muse_Example.htm?rev=227013&r1=227012&r2=227013&view=diff
==============================================================================
--- webservices/muse/trunk/src/examples/enterprise/Muse_Example.htm (original)
+++ webservices/muse/trunk/src/examples/enterprise/Muse_Example.htm Tue Aug 2
07:23:13 2005
@@ -151,10 +151,13 @@
control of these processes. The set of properties allows to monitor the state
of processes running on the business process resource. For the specific
BusinessProcess
instance the way to learn what is the number of running processes is to get
- a property value for NumberOfRunningProcesses before executing any of
suspend/terminate/resume
+ a property value for NumberOfRunningProcesses before executing any of
suspend/terminate/resume/complete
operations. Once you terminate all processes at the BusinessProces instance
it is not possible to restart the running processes. You can suspend them and
- resume as much as you want, but termination means “out of the
pool.”</P>
+ resume as much as you want, but termination means “out of the
list.”</P>
+ <P>The possible state changes for BuinessProcess are as follows:</P>
+ <img src="images/bp_states.jpg" >
+ <P>Sending appropriate commands will influence exposed by BusinessProcess
properties values.</P>
<p></p>
<h4>EnterpriseApplication</h4>
<P>The Resource Service of EnrerpriseApplication type represents the Enterprise
@@ -255,18 +258,18 @@
</H2>
<P>In order to run the MUSE example application, you need to build and deploy
it to MUSE web application.</P>
-<P> The base of the deployment is the existing MUSE Web App comming with the
MUSE
+<P> The base of the deployment is the existing MUSE Web App coming with the
MUSE
distribution. There are two options: </P>
<ul>
<li>You already followed deployment steps for MUSE distribution. You have
MUSE
deployed to your Web Server </li>
- <li>You did not deployed MUSE app yet.</li>
+ <li>You did not deployed MUSE App yet.</li>
</ul>
<p>The goal of MUSE example deployment is to add the example's ResourceServices
to MUSE Web App. </p>
<p>Example application is composed of several sub-projects, which correspond to
each Resource Service. Each sub-project contains build.properties file.
Before
- you can build and deploy the MUSE example app you need to edit the
build.properties
+ you can build and deploy the MUSE example App you need to edit the
build.properties
file in all sub-projects to correctly point to the MUSE Web App. The
examples/logic directory contains back-end implementation, the example/services
contains Resource Services implementations. You need to edit build.properties
files in all subprojects. If the app
is already deployed to WebServer, point to this deployment. If it is not
deployed
yet point to the distribution webapps/muse directory, then after the MUSE
example
@@ -318,8 +321,8 @@
</H2>
<P>The /requests subdirectory contains examples of soap requests. Those
requests
show what are the wire level soap requests corresponding to different MUSE
operations
- and properties, and custom operations and properties defined in MUSE exampl
- app. You can add more requests modeled on those provided, and use them for
your
+ and properties, and custom operations and properties defined in MUSE example
+ App. You can add more requests modeled on those provided, and use them for
your
request sequence. Be aware that the Resource Services validates the requests
and the xml request file needs to be:</P>
<ul>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
