Author: abogachuk Date: 2010-03-10 11:36:41 -0500 (Wed, 10 Mar 2010) New Revision: 20741 Modified: trunk/jbpm/docs/reference/en-US/Introduction.xml trunk/jbpm/docs/reference/en-US/Test_Drive_Proc.xml trunk/jbpm/docs/reference/en-US/guided_tour_jboss_jbpmgpd.xml trunk/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_6.png trunk/jbpm/docs/reference/en-US/images/the_views/the_views_10.png Log: https://jira.jboss.org/jira/browse/JBDS-1136 -updated some screens and text in the guide according to info reported by Jiri. All the issues were resolved Modified: trunk/jbpm/docs/reference/en-US/Introduction.xml =================================================================== --- trunk/jbpm/docs/reference/en-US/Introduction.xml 2010-03-10 16:29:30 UTC (rev 20740) +++ trunk/jbpm/docs/reference/en-US/Introduction.xml 2010-03-10 16:36:41 UTC (rev 20741) @@ -67,10 +67,10 @@ <row> <entry> - <link linkend="minimal_process_definition">jBDL support</link> + <link linkend="minimal_process_definition">jPDL support</link> </entry> <entry>Enables managing workflow processes as well as human tasks and interactions between - them. jBDL combines the best both Java and declarative process techniques.</entry> + them. jPDL combines the best both Java and declarative process techniques.</entry> </row> <row> @@ -146,7 +146,7 @@ <section> <title>Other relevant resources on the topic</title> - <para>All JBoss Developer Studio/JBoss Tools release documentation you can find at<ulink url="http://docs.jboss.org/tools/">http://docs.jboss.org/too... in the corresponding release directory.</para> + <para>All JBoss Developer Studio/JBoss Tools release documentation you can find at<ulink url="http://docs.jboss.org/tools/">http://docs.jboss.org/too... in the corresponding release directory.</para> <para>There is some extra information on <ulink url="http://www.jboss.org/community/wiki/JBPMWiki">JBoss Wiki. </ulink></para> <para>The latest documentation builds are available at <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">htt... </section> Modified: trunk/jbpm/docs/reference/en-US/Test_Drive_Proc.xml =================================================================== --- trunk/jbpm/docs/reference/en-US/Test_Drive_Proc.xml 2010-03-10 16:29:30 UTC (rev 20740) +++ trunk/jbpm/docs/reference/en-US/Test_Drive_Proc.xml 2010-03-10 16:36:41 UTC (rev 20741) @@ -87,13 +87,13 @@ </mediaobject> </figure> - <para>By default JUnite 3 version of testing framework is selected. Of course, you can choose + <para>By default JUnit 3 version of testing framework is selected. Of course, you can choose new advanced JUnit 4 version. In this case you&apos;ll be prompted to add new JUnit Library to your build path. To add it automatically just click on the appropriate link. In the <emphasis> <property>Class under test</property> </emphasis> section you can specify the class to test.</para> - + <para>In this guide we will use JUnit 3 version.</para> <figure> <title>A First Test Scenario</title> Modified: trunk/jbpm/docs/reference/en-US/guided_tour_jboss_jbpmgpd.xml =================================================================== --- trunk/jbpm/docs/reference/en-US/guided_tour_jboss_jbpmgpd.xml 2010-03-10 16:29:30 UTC (rev 20740) +++ trunk/jbpm/docs/reference/en-US/guided_tour_jboss_jbpmgpd.xml 2010-03-10 16:36:41 UTC (rev 20741) @@ -147,15 +147,19 @@ creating a folder with the name of the process definition and populating this folder with two .xml files : <emphasis> <property>gpd.xml</property> - </emphasis> and <emphasis> - <property>processdefinition.xml</property>. </emphasis></para> + </emphasis> , <emphasis> + <property>processdefinition.xml</property> </emphasis> and a .jpg file:<emphasis> + <property>processimage.jpg</property></emphasis>.</para> <para>The <emphasis> <property>gpd.xml</property> </emphasis> contains the graphical information used by the process definition editor. The <emphasis> <property>processdefinition.xml</property> - </emphasis> file contains the actual process definition info without the graphical - rendering info. At present, the GPD assumes that these two files are siblings. More + </emphasis> file contains the actual process definition info. + The graphical view of the process is automatically saved in <emphasis> + <property>processimage.jpg</property> + </emphasis>file. + At present, the GPD assumes that these three files are siblings. More sophisticated configuration will be supported later.</para> <section id="minimal_process_definition"> @@ -164,7 +168,7 @@ <para>Now we are ready to create a very simple process definition consisting of a begin state, an intermediate state and an end state.</para> <para>To make the configuration of actions much easier it&apos;s better to use the - jPDL perspective. It provides the tabbed Properties Editor which allows to configure + <emphasis>><property>"jBPM jPDL 3"</property></emphasis> perspective. It provides the tabbed Properties Editor which allows to configure all the relevant properties of the current selected item. </para> <section id="adding_the_nodes"> Modified: trunk/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_6.png =================================================================== (Binary files differ) Modified: trunk/jbpm/docs/reference/en-US/images/the_views/the_views_10.png =================================================================== (Binary files differ)