10:56 a.m.
Author: ochikvina
Date: 2007-11-23 11:56:55 -0500 (Fri, 23 Nov 2007)
New Revision: 5069
Modified:
trunk/jbpm/docs/reference/en/modules/Quick_Howto_Guide.xml
trunk/jbpm/docs/reference/en/modules/Test_Drive_Proc.xml
trunk/jbpm/docs/reference/en/modules/The_JBoss_jBPM_Int_Mech.xml
Log:
http://jira.jboss.com/jira/browse/RHDS-288 chapters update
Modified: trunk/jbpm/docs/reference/en/modules/Quick_Howto_Guide.xml
===================================================================
--- trunk/jbpm/docs/reference/en/modules/Quick_Howto_Guide.xml 2007-11-23 16:55:20 UTC
(rev 5068)
+++ trunk/jbpm/docs/reference/en/modules/Quick_Howto_Guide.xml 2007-11-23 16:56:55 UTC
(rev 5069)
@@ -15,13 +15,13 @@
<section>
<title>Change the Default Core jBPM Installation</title>
- <para> You can change the default jBPM installation by means of the Eclipse
preference
+ <para> You can change the default <property>jBPM</property>
installation by means of the Eclipse preference
mechanism. Open the Preferences dialog by selecting
- 'Window->Preferences' and select the 'JBoss
jBPM'
- category (???). Using this page you can add multiple jBPM installation
locations and
+ <property>Window < Preferences</property> and select the
<property>JBoss jBPM</property>
+ category. Using this page you can add multiple
<property>jBPM</property> installation locations and
change the default one. The default installation is used for the classpath
settings when
creating a new Process Project. Changing the preferences has no influence on
already
- created projects. Getting rid of a jBPM installation that's being
referenced by a
+ created projects. Getting rid of a <property>jBPM</property>
installation that's being referenced by a
project however will cause the classpath to contain errors. </para>
@@ -41,7 +41,7 @@
<para> You can add tasks to task nodes and then configure these last ones
in a similar
manner as the Action configuration mechanism. The context menu of the tasks
contains a
- 'Properties' entry that opens a configuration dialog (???).
</para>
+ <property>Properties</property> entry that opens a configuration
dialog. </para>
<figure>
<title> The Task Configuration Dialog</title>
Modified: trunk/jbpm/docs/reference/en/modules/Test_Drive_Proc.xml
===================================================================
--- trunk/jbpm/docs/reference/en/modules/Test_Drive_Proc.xml 2007-11-23 16:55:20 UTC (rev
5068)
+++ trunk/jbpm/docs/reference/en/modules/Test_Drive_Proc.xml 2007-11-23 16:56:55 UTC (rev
5069)
@@ -16,10 +16,10 @@
and workflow management is that developers can easily leverage their usual
programming
skills and techiques. One of these well-known techniques is unit testing and test
driven
development. In this chapter we will show how developers, making use of the JBoss
jBPM GPD
- can use a technique we have baptised 'Test Driven Process
Development' to
+ can use a technique we have baptised <property>Test Driven Process
Development</property> to
create process definitions and test their correctness. </para>
- <para> When creating the 'Hello jBPM' project the create
process project
+ <para> When creating the <property>Hello jBPM</property> project
the create process project
wizard has already put in place all the library requirements we need to start
writing jBPM
unit tests. These are contained in the jBPM Library container and the most
important of it
is - suprisingly - the jar file containing the core jBPM classes. It must be
noted that it
@@ -27,11 +27,11 @@
settings. More on this later in the book. </para>
<para> With that extra knowledge on the project settings, you can create your
first test. To do
- this, we create the 'com.jbay' package in the
- 'test/java' source folder. Then we bring up the context menu on
this
- package and select 'New->JUnit Test Case' (Figure 3.1,
"Create a
+ this, we create the <property>com.jbay</property> package in the
+ <property>test/java</property> source folder. Then we bring up the
context menu on this
+ package and select <property>New > JUnit Test Case</property>
(Figure 3.1, "Create a
Test" and Figure 3.2, "Create Test Dialog"). We call
the test
- class ''HelloTest'. </para>
+ class <property>HelloTest</property>. </para>
<figure>
<title>Create a Test</title>
@@ -61,7 +61,7 @@
object is fed to the constructor of a process instance object. We have a process
instance
object, but this process is not yet started, so we can safely assert that its
root token
still resides in the start node. After signalling the token will move to the next
state and
- the process will be in the 'auction' state. Finally another
signal will
+ the process will be in the <property>auction</property> state.
Finally another signal will
end the process. </para>
<figure>
@@ -99,7 +99,7 @@
<para> Of course, this simple scenario was not very interesting, but the
purpose of it was to
show how you can reuse your development skills in a very straightforward way when
doing
process development. To see how more interesting processes and process test
scenario's can
- be developed, we suggest you to read the JBoss jBPM User Guide and to study the
API
+ be developed, we suggest you to read the <property>JBoss jBPM User
Guide</property> and to study the API
reference. Moreover some more examples will be given later in this
book.</para>
</chapter>
Modified: trunk/jbpm/docs/reference/en/modules/The_JBoss_jBPM_Int_Mech.xml
===================================================================
--- trunk/jbpm/docs/reference/en/modules/The_JBoss_jBPM_Int_Mech.xml 2007-11-23 16:55:20
UTC (rev 5068)
+++ trunk/jbpm/docs/reference/en/modules/The_JBoss_jBPM_Int_Mech.xml 2007-11-23 16:56:55
UTC (rev 5069)
@@ -12,9 +12,9 @@
</chapterinfo>
<title>Actions : The JBoss jBPM Integration Mechanism</title>
- <para> In this chapter we will show how to do software integration with JBoss
jBPM. The standard
+ <para> In this chapter we will show how to do software integration with
<property>JBoss jBPM</property>. The standard
mechanism to realize this is to wrap the functionality you want to integrate in a
class that
- implements the ActionHandler interface. </para>
+ implements the <property>ActionHandler</property> interface.
</para>
<section>
<title>Creating a Hello World Action</title>
@@ -22,7 +22,7 @@
<para> Each Hello World process should integrate one or more Hello World
actions, so this is
what we will be doing. We can integrate custom code at different points in
the process
definition. To do this we have to specify an action handler, represented by
an
- implementation of the ActionHandler interface, and attach this piece of code
to a
+ implementation of the <property>ActionHandler</property>
interface, and attach this piece of code to a
particular event. These events are amongst others, going over a transition,
leaving or
enterning nodes, after and before signalling. </para>
@@ -37,11 +37,11 @@
</figure>
<para> To make things a little bit more concrete, we will implement an
action handler. To do
- this, create a new class called HelloActionHandler, which implements the
ActionHandler
- interface and implement the execute method as shown in Figure 4.1,
"A Simple
- Hello Action" and Figure 4.2, "A Simple Hello
Action". This
- test will add a variable named 'greeting' to the collection
of process
- variables and puts a message in it : "Hello from
ActionHandler". </para>
+ this, create a new class called
<property>HelloActionHandler</property>, which implements the
<property>ActionHandler</property>
+ interface and implement the execute method as shown in Figure 5.1,
"A Simple
+ Hello Action" and Figure 5.2, "A Simple Hello
Action". This
+ test will add a variable named <property>greeting</property> to
the collection of process
+ variables and puts a message in it : <property>Hello from
ActionHandler</property>. </para>
<figure>
<title>A Simple Hello Action</title>
@@ -64,9 +64,9 @@
it to the first state. We want to associate the execution of the action with
the event
of going over the transition from the start state to the first state. So
after the
signal, the process should be in the first state as in the previous scenario.
But
- moreover, the 'greeting' variable should exist and contain
the string
- "Hello from ActionHandler". That's what we assert
in the last
- lines of the test method shown in Figure 4.3, "Create the Hello
Action
+ moreover, the <property>greeting</property> variable should exist
and contain the string
+ <property>Hello from ActionHandler</property>. That's
what we assert in the last
+ lines of the test method shown in Figure 5.3, "Create the Hello
Action
Test" </para>
<figure>
@@ -79,7 +79,7 @@
</mediaobject>
</figure>
- <para> Running the tests now results in a failure. This is shown in Figure
4.4,
+ <para> Running the tests now results in a failure. This is shown in Figure
5.4,
"Test Results Before Integration" As a matter of fact, we
did not
associate the action with any particular event in the process definition, so
the process
variable did not get set. </para>
@@ -96,7 +96,7 @@
<para> Let's do something about it and add an action to the first
transition of our
sample process. This is done by bringing up the context menu of the
transition in the
- tree page of the outline view, as shown in Figure 4.5, "Adding an
Action to a
+ tree page of the outline view, as shown in Figure 5.5, "Adding an
Action to a
Transition". </para>
<figure>
@@ -111,10 +111,10 @@
<para> Right-clicking the action brings up a popupmenu with an entry to
edit the properties
of the selected action. Clicking on this menu entry opens a configuration
dialog for
actions. For now we will only configure the name and class properties of this
action.
- The rest will be treated later. We enter 'hello' as the
name of the
- action and click on the 'Browse...' button to open a choose
class
- dialog where we can look for the classes implementing the ActionHandler
interface in our
- project's classpath (Figure 4.6, "The Choose Action
Handler
+ The rest will be treated later. We enter
<property>hello</property> as the name of the
+ action and click on the <property>Browse...</property> button to
open a choose class
+ dialog where we can look for the classes implementing the
<property>ActionHandler</property> interface in our
+ project's classpath (Figure 5.6, "The Choose Action
Handler
Dialog"). </para>
<figure>
@@ -138,9 +138,9 @@
</figure>
<para> We choose our previously created
'HelloActionHandler' class and
- push the 'OK' button (Figure 4.7, "The Action
Configuration
+ push the <property>OK</property> button (Figure 5.7,
"The Action Configuration
Dialog"). After the selection of the action handler for the action,
we can run
- the test and observe it gives us a green light (Figure 4.8, "The
Action
+ the test and observe it gives us a green light (Figure 5.8, "The
Action
Configuration Dialog"). </para>
<figure>
@@ -158,7 +158,7 @@
<title> Integration Points</title>
<para> The different integration points in a process definition are
thoroughly documented in
- the JBoss jBPM User Guide. As you see on Figure 4.9, "Adding an
Event Action" different
+ the <property>JBoss jBPM User Guide</property>. As you see on
Figure 5.9, "Adding an Event Action" different
kinds of actions can be added to for instance nodes. Adding such an action
will create
an event object in the outline view and add an action as a child of this
newly created
event. In the same way, actions can be added to the process definition
object. Moreover,