From jbosstools-commits at lists.jboss.org Thu Mar 19 19:44:01 2009 Content-Type: multipart/mixed; boundary="===============9136535237521040365==" MIME-Version: 1.0 From: jbosstools-commits at lists.jboss.org To: jbosstools-commits at lists.jboss.org Subject: [jbosstools-commits] JBoss Tools SVN: r14274 - trunk/jbpm/docs/reference/en/modules. Date: Thu, 19 Mar 2009 19:44:01 -0400 Message-ID: --===============9136535237521040365== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: smukhina Date: 2009-03-19 19:44:01 -0400 (Thu, 19 Mar 2009) New Revision: 14274 Modified: trunk/jbpm/docs/reference/en/modules/The_JBoss_jBPM_Int_Mech.xml trunk/jbpm/docs/reference/en/modules/guided_tour_jboss_jbpmgpd.xml Log: https://jira.jboss.org/jira/browse/JBDS-359 - spelling and validation is ch= ecked = Modified: trunk/jbpm/docs/reference/en/modules/The_JBoss_jBPM_Int_Mech.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/jbpm/docs/reference/en/modules/The_JBoss_jBPM_Int_Mech.xml 2009-0= 3-19 23:04:13 UTC (rev 14273) +++ trunk/jbpm/docs/reference/en/modules/The_JBoss_jBPM_Int_Mech.xml 2009-0= 3-19 23:44:01 UTC (rev 14274) @@ -223,7 +223,7 @@ = - Tere we are. The above objective has been achieved. + There we are. The above objective has been achieved. =
Modified: trunk/jbpm/docs/reference/en/modules/guided_tour_jboss_jbpmgpd.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/jbpm/docs/reference/en/modules/guided_tour_jboss_jbpmgpd.xml 2009= -03-19 23:04:13 UTC (rev 14273) +++ trunk/jbpm/docs/reference/en/modules/guided_tour_jboss_jbpmgpd.xml 2009= -03-19 23:44:01 UTC (rev 14274) @@ -1,221 +1,221 @@ - - - - - jBPM - JBoss - Process - Definition - - - A Guided Tour of JBoss jBPM GPD - In this chapter we suggest a step-by-step walk-through of creating = and configuring your - own simple process. Let's try to organize a new jBPM project. - A wizard for creating a jBPM project is included in the GPD plugin.= We have opted to - create a project based on a template already containing a number of adva= nced artifacts that - we will ignore for this section. In the future we will elaborate this wi= zard and offer the - possibility to create an empty jBPM project as well as projects based on= templates taken - from the jBPM tutorial. -
- - Creating a jBPM Project - This section will show you how to use the Creation wizard for crea= ting a new jBPM - project with already included source folders. - At first you should select - File >New Project... - and then - JBoss jBPM > Process Project - in the New Project dialog: -
- New Project Dialog - - - - - -
- Clicking - Next - brings us to the wizard page where it's necessary to s= pecify the - name and location for the project. We choose, for example, - HellojBPM - as the name and accept the default location. -
- Process Name and Location - - - - - -
- Thus, our project will be created in the workspace root directory = by default. If you - want to change the directory for your future project, deselect - Use default location - and click - Browse... - button to set needed location or simply type it. - On the next screen you'll be prompted to select the core jBPM= location that - we have defined in the previous chapter. -
- Core jBPM Location Specifying - - - - - -
- Clicking on - Finish - results in the project being generated. The wizard creates = four source - folders: one for the processes ( - src/main/jpdl - ), one for the java sources ( - src/main/java - ), one for the unit tests ( - src/test/java - ) and one for the resources such as the jbpm.properties and = the - hibernate.properties files ( - src/main/config - ). In addition a classpath container with all the core jBPM = libraries is - added to the project -
- Layout of the Process Project - - - - - -
- Looking inside the different source folders will reveal a number o= f other artifacts - that were generated, but we will leave these untouched for the moment. = Instead, we will - look at another wizard that enables us to create an empty process defin= ition. -
-
- - Creating an Empty Process Definition - Now when the project is set up, we can use a Creation wizard to cr= eate an empty - process definition. Bring up the - New - wizard by clicking the - File > New > Other... - menu item. The wizard opens on the - Select Wizard - page. -
- The Select Wizard Page - - - - - -
- Selecting the - JBoss jBPM - category, then the - Process Definition - item and clicking on the - Next - button brings us to the - Create Process Definition - page. -
- The Create New Process Definion Page - - - - - -
- We choose - hello - as the name of the process archive file. Click on the - Finish - button to end the wizard and open the process definition ed= itor. -
- The Process Definition Editor - - - - - -
- - - You can see in the Package Explorer that creating a process defini= tion involves - creating a folder with the name of the process definition and populatin= g this folder - with two .xml files : - gpd.xml - and - processdefinition.xml. - The - gpd.xml - contains the graphical information used by the process defi= nition editor. - The - processdefinition.xml - file contains the actual process definition info without th= e graphical - rendering info. At present, the GPD assumes that these two files are si= blings. More - sophisticated configuration will be supported later. - -
- - A Minimal Process Definition - Now we are ready to create a very simple process definition consi= sting of a begin - state, an intermediate state and an end state. - To make the configuration of actions much easier it's better= to use the - jPDL perspective. It provides the tabbed Properties Editor which allow= s to configure - all the relevant properties of the current selected item. - -
- - Adding the Nodes - At first select respectively - Start, - - State - and - End - on the tools palette and click on the canvas to add these= nodes to - the process definition. The result should look similar to this: -
- A Simple Process With Three Nodes - - - - - -
-
-
- - Adding Transitions - Then, we will connect the nodes with transitions. To do that sel= ect the - Transition - tool in the tools palette and click on the - Start - node, then move to the - State - node and click again to see the transition being drawn. P= erform the - same steps to create a transition from the - State - node to the - End - node. The result will look like: -
- A Simple Process With Transitions - - - - - -
- Now, when you've got background knowledge of simple project= creation, - let's move to more advanced tools. -
-
-
- - + + + + + jBPM + JBoss + Process + Definition + + + A Guided Tour of JBoss jBPM GPD + In this chapter we suggest a step-by-step walk-through of creating = and configuring your + own simple process. Let's try to organize a new jBPM project. + A wizard for creating a jBPM project is included in the GPD plugin.= We have opted to + create a project based on a template already containing a number of adva= nced artifacts that + we will ignore for this section. In the future we will elaborate this wi= zard and offer the + possibility to create an empty jBPM project as well as projects based on= templates taken + from the jBPM tutorial. +
+ + Creating a jBPM Project + This section will show you how to use the Creation wizard for crea= ting a new jBPM + project with already included source folders. + At first you should select + File >New Project... + and then + JBoss jBPM > Process Project + in the New Project dialog: +
+ New Project Dialog + + + + + +
+ Clicking + Next + brings us to the wizard page where it's necessary to s= pecify the + name and location for the project. We choose, for example, + HellojBPM + as the name and accept the default location. +
+ Process Name and Location + + + + + +
+ Thus, our project will be created in the workspace root directory = by default. If you + want to change the directory for your future project, deselect + Use default location + and click + Browse... + button to set needed location or simply type it. + On the next screen you'll be prompted to select the core jBPM= location that + we have defined in the previous chapter. +
+ Core jBPM Location Specifying + + + + + +
+ Clicking on + Finish + results in the project being generated. The wizard creates = four source + folders: one for the processes ( + src/main/jpdl + ), one for the java sources ( + src/main/java + ), one for the unit tests ( + src/test/java + ) and one for the resources such as the jbpm.properties and = the + hibernate.properties files ( + src/main/config + ). In addition a classpath container with all the core jBPM = libraries is + added to the project +
+ Layout of the Process Project + + + + + +
+ Looking inside the different source folders will reveal a number o= f other artifacts + that were generated, but we will leave these untouched for the moment. = Instead, we will + look at another wizard that enables us to create an empty process defin= ition. +
+
+ + Creating an Empty Process Definition + Now when the project is set up, we can use a Creation wizard to cr= eate an empty + process definition. Bring up the + New + wizard by clicking the + File > New > Other... + menu item. The wizard opens on the + Select Wizard + page. +
+ The Select Wizard Page + + + + + +
+ Selecting the + JBoss jBPM + category, then the + Process Definition + item and clicking on the + Next + button brings us to the + Create Process Definition + page. +
+ The Create New Process Defining Page + + + + + +
+ We choose + hello + as the name of the process archive file. Click on the + Finish + button to end the wizard and open the process definition ed= itor. +
+ The Process Definition Editor + + + + + +
+ + + You can see in the Package Explorer that creating a process defini= tion involves + creating a folder with the name of the process definition and populatin= g this folder + with two .xml files : + gpd.xml + and + processdefinition.xml. + The + gpd.xml + contains the graphical information used by the process defi= nition editor. + The + processdefinition.xml + file contains the actual process definition info without th= e graphical + rendering info. At present, the GPD assumes that these two files are si= blings. More + sophisticated configuration will be supported later. + +
+ + A Minimal Process Definition + Now we are ready to create a very simple process definition consi= sting of a begin + state, an intermediate state and an end state. + To make the configuration of actions much easier it's better= to use the + jPDL perspective. It provides the tabbed Properties Editor which allow= s to configure + all the relevant properties of the current selected item. + +
+ + Adding the Nodes + At first select respectively + Start, + + State + and + End + on the tools palette and click on the canvas to add these= nodes to + the process definition. The result should look similar to this: +
+ A Simple Process With Three Nodes + + + + + +
+
+
+ + Adding Transitions + Then, we will connect the nodes with transitions. To do that sel= ect the + Transition + tool in the tools palette and click on the + Start + node, then move to the + State + node and click again to see the transition being drawn. P= erform the + same steps to create a transition from the + State + node to the + End + node. The result will look like: +
+ A Simple Process With Transitions + + + + + +
+ Now, when you've got background knowledge of simple project= creation, + let's move to more advanced tools. +
+
+
+ + --===============9136535237521040365==--