January 2011 - jbosstools-commits

JBoss Tools SVN: r28413 - trunk/jbpm/docs/reference/en-US.

by jbosstools-commits＠lists.jboss.org

Author: mcaspers Date: 2011-01-19 18:39:41 -0500 (Wed, 19 Jan 2011) New Revision: 28413 Modified: trunk/jbpm/docs/reference/en-US/Revision_History.xml trunk/jbpm/docs/reference/en-US/tasks.xml Log: General Updates Modified: trunk/jbpm/docs/reference/en-US/Revision_History.xml =================================================================== --- trunk/jbpm/docs/reference/en-US/Revision_History.xml 2011-01-19 23:37:26 UTC (rev 28412) +++ trunk/jbpm/docs/reference/en-US/Revision_History.xml 2011-01-19 23:39:41 UTC (rev 28413) @@ -2,31 +2,51 @@ <!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> <appendix> - <title>Revision History</title> - <simpara> - <revhistory> - <revision> - <revnumber>1</revnumber><date>Wed Jun 09 2010</date> - <author> - <firstname>JBoss Tools</firstname><surname>Documentation Team</surname><email>irooskov(a)redhat.com</email> - </author> - <revdescription> - <simplelist> - <member>Restructured and general updates</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>0</revnumber><date>Fri Nov 20 2009</date> - <author> - <firstname>Isaac</firstname><surname>Rooskov</surname><email>irooskov(a)redhat.com</email> - </author> - <revdescription> - <simplelist> - <member>Initial creation of book by publican</member> - </simplelist> - </revdescription> - </revision> - </revhistory> - </simpara> + <title>Revision History</title> + <simpara> + <revhistory> + <revision> + <revnumber>2</revnumber> + <date>Thu Jan 20 2011</date> + <author> + <firstname>JBoss Tools</firstname> + <surname>Documentation Team</surname> + <email>mcaspers(a)redhat.com</email> + </author> + <revdescription> + <simplelist> + <member>General updates</member> + </simplelist> + </revdescription> + </revision> + <revision> + <revnumber>1</revnumber> + <date>Wed Jun 09 2010</date> + <author> + <firstname>JBoss Tools</firstname> + <surname>Documentation Team</surname> + <email>irooskov(a)redhat.com</email> + </author> + <revdescription> + <simplelist> + <member>Restructured and general updates</member> + </simplelist> + </revdescription> + </revision> + <revision> + <revnumber>0</revnumber> + <date>Fri Nov 20 2009</date> + <author> + <firstname>Isaac</firstname> + <surname>Rooskov</surname> + <email>irooskov(a)redhat.com</email> + </author> + <revdescription> + <simplelist> + <member>Initial creation of book by publican</member> + </simplelist> + </revdescription> + </revision> + </revhistory> + </simpara> </appendix> Modified: trunk/jbpm/docs/reference/en-US/tasks.xml =================================================================== --- trunk/jbpm/docs/reference/en-US/tasks.xml 2011-01-19 23:37:26 UTC (rev 28412) +++ trunk/jbpm/docs/reference/en-US/tasks.xml 2011-01-19 23:39:41 UTC (rev 28413) @@ -28,7 +28,9 @@ <para>Try to avoid using spaces in the names of installation folders. It can cause problems with Sun based VMs.</para> </note> - <para>Select <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Preferences</guimenuitem><guimenuitem>JBoss jBPM</guimenuitem><guimenuitem>Runtime Locations</guimenuitem></menuchoice>. Here you can add, edit and remove JBoss jBPM installation locations. Click the <guibutton>Add</guibutton> button. In the subsequent dialog box enter a name for a newly added jBPM runtime and point to the correct location of this package on your file system. Click the <guibutton>OK</guibutton> button twice to save the changes. + <para> + Select <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Preferences</guimenuitem><guimenuitem>JBoss jBPM</guimenuitem><guimenuitem>Runtime Locations</guimenuitem></menuchoice>. Here you can add, edit and remove JBoss jBPM installation locations. Click the <guibutton>Add</guibutton> button. In the subsequent dialog box enter a name for a newly added jBPM runtime and point to the correct location of this package on your file system. Click the <guibutton>OK</guibutton> button twice to save the changes. + </para> <figure> <title>Adding jBPM Location</title>

15 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r28412 - trunk/jbpm/docs/reference/en-US.

by jbosstools-commits＠lists.jboss.org

Author: mcaspers Date: 2011-01-19 18:37:26 -0500 (Wed, 19 Jan 2011) New Revision: 28412 Modified: trunk/jbpm/docs/reference/en-US/the_views.xml Log: General Updates Modified: trunk/jbpm/docs/reference/en-US/the_views.xml =================================================================== --- trunk/jbpm/docs/reference/en-US/the_views.xml 2011-01-19 23:19:53 UTC (rev 28411) +++ trunk/jbpm/docs/reference/en-US/the_views.xml 2011-01-19 23:37:26 UTC (rev 28412) @@ -1,385 +1,374 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="reference"> - <chapterinfo> - <keywordset> - <keyword>jBPM</keyword> - </keywordset> - </chapterinfo> - <title>Reference</title> - <section> - <title>Wizards</title> - <section> - <title>Process Project Wizard</title> - <para>This wizard helps to create new jBPM project.It is available with clicking - <property>File->New->Other->jBPM 3 Project</property> in the menu bar.</para> - <figure> - <title>New Process Project Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/the_views/jbpm_2.png"/> - </imageobject> - </mediaobject> - </figure> - <para>It consists of several pages:</para> - <itemizedlist> - <listitem><para>On the first page you can adjust the name of the project and the directory where it will be created.</para> - <para>If "<property>Use default</property>" option is checked the output directory will be the workspace, - othervise the user should specify it by himself using <property>Browse</property> button.</para> - <figure> - <title>New Process Project Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/the_views/jbpm_1.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - <listitem><para>On the second page you should point the location of your jbpm runtime.</para></listitem> - <listitem><para>The last page is only available for unabling/disabling - <emphasis>Generate simple process definition,action handling and Unit test</emphasis>.If you unable the option all the mentioned code will be generated automatically.</para></listitem> - </itemizedlist> - - </section> - <section> - <title>New JBPM Action Wizard</title> - <para>This wizard is available by clicking - <property>File->New->Other->jBPM 3 Action Handler</property>.</para> - - <figure> - <title>New JBPM Action Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/the_views/jbpm_3.png"/> - </imageobject> - </mediaobject> - </figure> - <para>It includes the next options to adjust:</para> - - <table> - <title>New JBPM Action Wizard. Options.</title> - <tgroup cols="3"> - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" colwidth="3*"/> - <colspec colnum="3" align="left" colwidth="1*"/> - - <thead> - <row> - <entry>Option</entry> - <entry>Description</entry> - <entry>Default</entry> - </row> - </thead> - <tbody> - - <row> - <entry>Source folder</entry> - <entry>The path to the source folder relative to the selected project</entry> - <entry>The source folder of the project selected in the <emphasis><property>Project</property></emphasis> field</entry> - </row> - - <row> - <entry>Package</entry> - <entry>Enter a package to contain an Action Handler. - Either type a valid package name or click - <emphasis><property>Browse</property></emphasis> - to select a package via the dialog box.</entry> - <entry><blank></entry> - </row> - - <row> - <entry>Enclosing type</entry> - <entry>Select the enclosing type of your jBPM action using - <emphasis><property>Browse</property></emphasis> - button.</entry> - <entry><blank></entry> - </row> - <row> - <entry>Modifiers</entry> - <entry>Select the modifiers that will be added to the generated class.</entry> - <entry>Public</entry> - </row> - <row> - <entry>Name</entry> - <entry>Type a name for a new Action Handler</entry> - <entry><blank></entry> - </row> - - <row> - <entry>Superclass</entry> - <entry>Type or click <emphasis><property>Browse</property></emphasis> - to select a superclass for an Action Handler</entry> - <entry>org.jbpm.graph.def.ActionHandler</entry> - </row> - - <row> - <entry>Interface</entry> - <entry>Type or click <emphasis><property>Add</property></emphasis> - to select an interface/interfaces for an Action Handler</entry> - <entry>org.jbpm.graph.def.ActionHandler</entry> - </row> + <chapterinfo> + <keywordset> + <keyword>jBPM</keyword> + </keywordset> + </chapterinfo> + <title>Reference</title> + <section> + <title>Wizards</title> + <section> + <title>Process Project Wizard</title> + <para> + This wizard is used to create new jBPM project. It is available by selecting <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>New</guimenuitem><guimenuitem>Other</guimenuitem><guimenuitem>jBPM 3 Project</guimenuitem></menuchoice>. + </para> + <figure> + <title>New Process Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/the_views/jbpm_2.png"/> + </imageobject> + </mediaobject> + </figure> + <para>It consists of several pages:</para> + <itemizedlist> + <listitem> + <para>On the first page you can adjust the name of the project and the directory where it will be created.</para> + <para> + If the <guilabel>Use default</guilabel> option is checked the output directory will be the workspace, otherwise the user should specify the location by clicking the <guibutton>Browse</guibutton> button. + </para> + <figure> + <title>New Process Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/the_views/jbpm_1.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>On the second page you should point the location of your jbpm runtime.</para> + </listitem> + <listitem> + <para> + The last page is only available for enabling and disabling <emphasis>Generate simple process definition,action handling and Unit test</emphasis>. If you enable the option all the mentioned code will be generated automatically. + </para> + </listitem> + </itemizedlist> - <row> - <entry>Which method stubs you would like to create?</entry> - <entry>Select the stubs that you would like to be created automatically.</entry> - <entry><itemizedlist> - <listitem><para>Constructors from superclass</para></listitem> - <listitem><para>Inherited abstract methods</para></listitem> - </itemizedlist> - </entry> - </row> - - <row> - <entry>Do you want to add comments?</entry> - <entry>Select <property>Generate comments</property> check box if you want comment mask - to be generated before the class definition. - </entry> - <entry><blank></entry> - </row> - </tbody> - </tgroup> - </table> - </section> + </section> + <section> + <title>New JBPM Action Wizard</title> + <para> + This wizard is available by selecting <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>New</guimenuitem><guimenuitem>Other</guimenuitem><guimenuitem>jBPM 3 Action Handler</guimenuitem></menuchoice>. + </para> + + <figure> + <title>New JBPM Action Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/the_views/jbpm_3.png"/> + </imageobject> + </mediaobject> + </figure> + <para>It includes the next options to adjust:</para> + + <table> + <title>New JBPM Action Wizard. Options.</title> + <tgroup cols="3"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" colwidth="3*"/> + <colspec colnum="3" align="left" colwidth="1*"/> + + <thead> + <row> + <entry>Option</entry> + <entry>Description</entry> + <entry>Default</entry> + </row> + </thead> + <tbody> + + <row> + <entry>Source folder</entry> + <entry>The path to the source folder relative to the selected project</entry> + <entry>The source folder of the project selected in the <emphasis><property>Project</property> + </emphasis> field</entry> + </row> + + <row> + <entry>Package</entry> + <entry> + Enter a package to contain an Action Handler. Either type a valid package name or click the <guibutton>Browse</guibutton> to select a package via the dialog box. + </entry> + <entry><blank></entry> + </row> + + <row> + <entry>Enclosing type</entry> + <entry>Select the enclosing type of your jBPM action click the <guibutton>Browse</guibutton> button.</entry> + <entry><blank></entry> + </row> + <row> + <entry>Modifiers</entry> + <entry>Select the modifiers that will be added to the generated class.</entry> + <entry>Public</entry> + </row> + <row> + <entry>Name</entry> + <entry>Type a name for a new Action Handler</entry> + <entry><blank></entry> + </row> + + <row> + <entry>Superclass</entry> + <entry>Type or click the <guibutton>Browse</guibutton> button to select a superclass for an Action Handler</entry> + <entry>org.jbpm.graph.def.ActionHandler</entry> + </row> + + <row> + <entry>Interface</entry> + <entry>Type or click the <guibutton>Add</guibutton> button to select an interface/interfaces for an Action Handler</entry> + <entry>org.jbpm.graph.def.ActionHandler</entry> + </row> + + <row> + <entry>Which method stubs you would like to create?</entry> + <entry>Select the stubs that you would like to be created automatically.</entry> + <entry> + <itemizedlist> + <listitem> + <para>Constructors from superclass</para> + </listitem> + <listitem> + <para>Inherited abstract methods</para> + </listitem> + </itemizedlist> + </entry> + </row> + + <row> + <entry>Do you want to add comments?</entry> + <entry>Select <guilabel>Generate comments</guilabel> check box if you want comment mask to be generated before the class definition.</entry> + <entry><blank></entry> + </row> + </tbody> + </tgroup> + </table> + </section> - - </section> - - <section id="the_views" xreflabel="the_views"> - <?dbhtml filename="the_views.html"?> - <title>The views</title> - <para>Here, it will be explained how to work with views and editors provided by JBDS.</para> - <para>The views are used for representation and navigation the resources you are working on at - the moment. One of the advantages of all the views is that all modifications made in the - current active file are immediately displayed in them. Let’s get acquainted more closely - with those that the <property>jPDL perspective</property> provides. </para> - <figure> - <title>The jPDL Perspective Views and Editors</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/the_views/the_views_0.png" scale="80"/> - </imageobject> - </mediaobject> - </figure> + </section> - <para>As you can see in the picture above, the <property>jPDL perspective</property> contains a - complete set of functionality that's necessary for working on the jBPM project.</para> + <section id="the_views" xreflabel="the_views"> + <?dbhtml filename="the_views.html"?> + <title>The views</title> + <para>Here, it will be explained how to work with views and editors provided by JBDS.</para> + <para> + The views are used to represent and navigate through the resources you are currently working on. One of the advantages of all the views is that they immediately reflect all modifications made in the current active file. Let's explore the views that the <property>jPDL perspective</property> provides in more detail. + </para> - <section id="the_outline_view"> - <?dbhtml filename="the_outline_view.html"?> - <title>The Outline View</title> - <para>To have a way to quickly see an outline of the process use the <emphasis> - <property>Outline view</property> - </emphasis> that is presented as the classical tree. If it is not visible select <emphasis> - <property>Window > Show view > Outline</property>. </emphasis></para> + <figure> + <title>The jPDL Perspective Views and Editors</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/the_views/the_views_0.png" scale="80"/> + </imageobject> + </mediaobject> + </figure> - <figure> - <title>The Overview View</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/the_views/the_views_1.png"/> - </imageobject> - </mediaobject> - </figure> - </section> + <para> + As you can see in the picture above, the <property>jPDL perspective</property> contains a complete set of functionality that's necessary for working on the jBPM project. + </para> - <section id="the_overview"> - <?dbhtml filename="the_outline_view.html"?> - <title>The Overview</title> - <para>The main advantage of this view is that it gives visual representation of the whole - current developing process. Besides, the <emphasis> - <property>Overview</property> - </emphasis> comes as a scrollable thumbnail which enables a better navigation of the - process structure if it's too large.</para> + <section id="the_outline_view"> + <?dbhtml filename="the_outline_view.html"?> + <title>The Outline View</title> + <para> + The <emphasis><property>Outline view</property></emphasis> provides a classical tree that allows you to quickly view the outline of a process. If it is not visible select <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Show view</guimenuitem><guimenuitem>Outline</guimenuitem></menuchoice>. + </para> - <figure> - <title>The Overview</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/the_views/the_views_2.png"/> - </imageobject> - </mediaobject> - </figure> - </section> + <figure> + <title>The Overview View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/the_views/the_views_1.png"/> + </imageobject> + </mediaobject> + </figure> + </section> - <section id="the_properties_view"> - <?dbhtml filename="the_properties_view.html"?> - <title>The Properties View</title> - <para> Here, we dwell on the JBDS <property>Properties view</property>.</para> - <para>Notice if it's not visible you can access it by navigating <emphasis> - <property>Window > Show view > Properties</property>. </emphasis></para> - <para>The view shows the relevant properties of the selected item in the tabbed form. Every - item has its own set of properties, which can be directly editable in the Properties - view or by brining up the context menu.</para> + <section id="the_overview"> + <?dbhtml filename="the_outline_view.html"?> + <title>The Overview</title> + <para> + This view provides a visual representation of the entire current developing process. The <emphasis><property>Overview</property></emphasis> comes as a scrollable thumbnail which enables a better navigation of the process structure if it is too large. + </para> - <figure> - <title>The Properties View of selected Transition</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/the_views/the_views_3.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>The Overview</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/the_views/the_views_2.png"/> + </imageobject> + </mediaobject> + </figure> + </section> - <para>For example, on the picture above the Properties view displays all the properties for - a selected transition. Its name has been changed to <emphasis> - <property>to_auction</property>. </emphasis> We've done it directly in - active General tab of the view. The same way let's change the name for the - second transition to <emphasis> - <property>to_end</property>. </emphasis></para> - <para>If no one item is selected, the view represents the properties of the whole process - definition. </para> + <section id="the_properties_view"> + <?dbhtml filename="the_properties_view.html"?> + <title>The Properties View</title> + <para> Here, we dwell on the JBDS <property>Properties view</property>.</para> + <para> + The Properties view can be displayed by selecting <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Show view</guimenuitem><guimenuitem>Properties</guimenuitem></menuchoice>. + </para> + <para> + This view will list the relevant properties of the selected item in the tabbed form. Every item has its own set of properties, which can be directly edited in the Properties view or by brining up the context menu. + </para> - <figure> - <title>The Properties View of Process Definition</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/the_views/the_views_4.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>The Properties View of selected Transition</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/the_views/the_views_3.png"/> + </imageobject> + </mediaobject> + </figure> - <para>In this case, it contains six tabs. The first one is the <emphasis> - <property>General</property>.</emphasis> It allows to specify a process name and add - necessary description. To illustrate let's change the process definition name - to <emphasis> - <property>jbay</property>. </emphasis></para> - </section> + <para> + For example, on the picture above the Properties view displays all the properties for a selected transition. Its name has been changed to <emphasis><property>to_auction</property></emphasis>. We have done it directly in active General tab of the view. The same way let's change the name for the second transition to <emphasis><property>to_end</property></emphasis>. + </para> + <para>If no one item is selected, the view represents the properties of the whole process definition. </para> - <section id="jbpm_gpd_editor"> - <?dbhtml filename="direct_editing.html"?> - <title>The jBPM Graphical Process Designer editor.</title> - <para>The <property>jBPM GPD editor</property> includes four modes: Diagram, Deployment, - Design and Source, which are available as switchable tabs at the bottom of the editor. - Let's dwell on each of them.</para> + <figure> + <title>The Properties View of Process Definition</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/the_views/the_views_4.png"/> + </imageobject> + </mediaobject> + </figure> - <section id="the_diagram_mode"> - <title>The Diagram mode</title> - <para> In this mode we define the process in the form of a diagram by means of tools - provided on the left-hand side of the jBPM GPD. </para> + <para> + In this case, it contains six tabs. The first one is the <emphasis><property>General</property>.</emphasis> It allows to specify a process name and add necessary description. To illustrate let's change the process definition name to <emphasis><property>jbay</property></emphasis>. + </para> + </section> - <figure> - <title>The Diagram mode</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/the_views/the_views_5.png"/> - </imageobject> - </mediaobject> - </figure> + <section id="jbpm_gpd_editor"> + <?dbhtml filename="direct_editing.html"?> + <title>The jBPM Graphical Process Designer editor.</title> + <para> + The <property>jBPM GPD editor</property> includes four modes: Diagram, Deployment, Design and Source, which are available as switchable tabs at the bottom of the editor. + </para> - <para>Besides, some properties can be directly edited in the <property>Diagram - mode</property> of the graphical editor. One example of this is the <emphasis> - <property>name</property> - </emphasis> property of nodes. You can edit this directly by selecting the node of - which you want to change the name and then click once inside this node. This enables - an editor in the node. We change the name of the node to <emphasis> - <property>auction</property>. </emphasis></para> - </section> + <section id="the_diagram_mode"> + <title>The Diagram mode</title> + <para> In this mode we define the process in the form of a diagram using the tools provided on the left-hand side of the jBPM GPD. </para> - <section id="source_mode"> - <?dbhtml filename="the_source_view.html"?> - <title>The Source Mode</title> - <para>Now, that we have defined a simple process definition, we can have a look at the - XML that is being generated under the covers. To see this XML click on the Source - tab of the graphical process designer editor.</para> + <figure> + <title>The Diagram mode</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/the_views/the_views_5.png"/> + </imageobject> + </mediaobject> + </figure> - <figure> - <title>The Source Mode</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/the_views/the_views_6.png"/> - </imageobject> - </mediaobject> - </figure> - <para>The <property>Source mode</property> enables to easily manipulate our XML. That is - manually inserting and editing necessary elements or attributes. In addition, here - you can take advantage of content assist.</para> - - <para>A template is added to better render the jBPM task forms in the Visual editor. - Now the jBPM Graphical Process designer can create facelets that are associated with tasks and are rendered in the jBPM console.</para> - <figure> - <title>A task form in VPE</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/the_views/the_views_6a.png"/> - </imageobject> - </mediaobject> - </figure> - </section> + <para> + Some properties can be directly edited in the <property>Diagram mode</property> of the graphical editor. One example of this is the <emphasis><property>name</property></emphasis> property of nodes. You can edit this directly by selecting the node of which you want to change the name and then clicking once inside this node. This enables an editor in the node. We then change the name of the node to <emphasis><property>auction</property></emphasis>. + </para> + </section> - <section id="design_mode"> - <?dbhtml filename="the_design_view.html"?> - <title>The Design Mode</title> - <para>One more way to edit your file is to use <property>Design mode</property>. You can - see it in the next picture:</para> - <figure> - <title>The Design Mode</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/the_views/the_views_7.png"/> - </imageobject> - </mediaobject> - </figure> + <section id="source_mode"> + <?dbhtml filename="the_source_view.html"?> + <title>The Source Mode</title> + <para> + Now, that we have defined a simple process definition, we can have a look at the XML that is being generated under the covers. To see this XML click on the Source tab of the graphical process designer editor. + </para> - <para>As you can see above, this mode looks like a table in the first column of which - the process structure is performed. Here, you can also insert, remove and edit - elements or attributes, moreover add comments and instructions. Their values can be - directly edited in the second column of the Design mode table.</para> - <para>For instance, let’s add a comment on the second transition. For that, you should - bring up the context menu for it and choose <emphasis> - <property>Add Before > Comment</property>. </emphasis></para> + <figure> + <title>The Source Mode</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/the_views/the_views_6.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + The <property>Source mode</property> provides a way to easily manipulate the raw XML source. In addition, here you can take advantage of content assist. + </para> - <figure> - <title>Adding a Comment</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/the_views/the_views_8.png"/> - </imageobject> - </mediaobject> - </figure> - <para>Then, we can put the text <emphasis>This transition leads to the end - state</emphasis> in the right column as its value.</para> + <para> + A template is added to better render the jBPM task forms in the Visual editor. Now the jBPM Graphical Process designer can create facelets that are associated with tasks and are rendered in the jBPM console. + </para> + <figure> + <title>A task form in VPE</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/the_views/the_views_6a.png"/> + </imageobject> + </mediaobject> + </figure> + </section> - <figure> - <title>Comment is added</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/the_views/the_views_9.png"/> - </imageobject> - </mediaobject> - </figure> + <section id="design_mode"> + <?dbhtml filename="the_design_view.html"?> + <title>The Design Mode</title> + <para>One more way to edit your file is to use the <property>Design mode</property>. This mode is shown in the next picture:</para> + <figure> + <title>The Design Mode</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/the_views/the_views_7.png"/> + </imageobject> + </mediaobject> + </figure> - </section> + <para> + The Design mode presents a table. The process structure is shown in the first column. Here, you can also insert, remove and edit elements or attributes, moreover add comments and instructions. Their values can be directly edited in the second column of the Design mode table. + </para> + <para>For instance, let’s add a comment on the second transition. For that, you should bring up the context menu for it and select <menuchoice><guimenuitem>Add Before</guimenuitem><guimenuitem>Comment</guimenuitem></menuchoice>. + </para> - <section id="deployment_mode"> - <?dbhtml filename="the_deployment_view.html"?> - <title>The Deployment Mode</title> - <para>Finally, to adjust the deployment settings of the project you should switch on to - the tab that opens the <property>Deployment mode</property>. On the picture below - the <property>Deployment mode</property> is performed with default settings. Here, - you can easily modify them or, if the settings won't match your needs, to - reset defaults. </para> - <figure> - <title>The Deployment Mode</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/the_views/the_views_10.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Adding a Comment</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/the_views/the_views_8.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Then, we can enter the text <emphasis>This transition leads to the end state</emphasis> in the right column as its value.</para> - <para>The <property>Test Connections</property> button can be used to check whether all your settings are valid before - deploying the process.</para> + <figure> + <title>Comment is added</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/the_views/the_views_9.png"/> + </imageobject> + </mediaobject> + </figure> - <para>To deploy the process on the server you should click the <property>Delpoy Process Archive</property> button.</para> + </section> - <para>However, prior to testing the connection and deploying the process on the server you need to - make sure the server is configured to support jBPM functionality and is running.</para> + <section id="deployment_mode"> + <?dbhtml filename="the_deployment_view.html"?> + <title>The Deployment Mode</title> + <para> + Finally, to adjust the deployment settings of the project you should select the tab that opens the <property>Deployment mode</property>. On the picture below the <property>Deployment mode</property> is performed with default settings. Here, you can easily modify them or, if the settings do not match your needs, to reset them to their defaults. + </para> + <figure> + <title>The Deployment Mode</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/the_views/the_views_10.png"/> + </imageobject> + </mediaobject> + </figure> - <para>Please, also note that if authentication for deployment is required you may use the process deployer that is available at <property>/gpd-deployer/upload</property>.</para> - - <para>Now that we've seen how to work with <property>jPDL - perspective</property>, let's pass on to the project testing.</para> - </section> - </section> -</section> + <para>The <guibutton>Test Connections</guibutton> button can be used to check whether all your settings are valid before deploying the process.</para> + + <para>To deploy the process on the server you should click the <guibutton>Delpoy Process Archive</guibutton> button.</para> + + <para> + However, prior to testing the connection and deploying the process on the server you need to make sure the server is configured to support jBPM functionality and is running. + </para> + + <para> + Please, also note that if authentication for deployment is required you may use the process deployer that is available at <filename>/gpd-deployer/upload</filename>. + </para> + </section> + </section> + </section> </chapter> \ No newline at end of file

15 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r28411 - trunk/build.

by jbosstools-commits＠lists.jboss.org

Author: nickboldt Date: 2011-01-19 18:19:53 -0500 (Wed, 19 Jan 2011) New Revision: 28411 Modified: trunk/build/publish.sh Log: check api for job, not build Modified: trunk/build/publish.sh =================================================================== --- trunk/build/publish.sh 2011-01-19 23:19:34 UTC (rev 28410) +++ trunk/build/publish.sh 2011-01-19 23:19:53 UTC (rev 28411) @@ -55,7 +55,7 @@ # JBDS-1361 - fetch XML and then sed it into plain text rl=${STAGINGDIR}/logs/SVN_REVISION rm -f ${rl}.txt ${rl}.xml -wget -q --no-clobber -O ${rl}.xml "http://hudson.qa.jboss.com/hudson/job/${JOB_NAME}/${BUILD_NUMBER}/api/xml..." +wget -q --no-clobber -O ${rl}.xml "http://hudson.qa.jboss.com/hudson/job/${JOB_NAME}/api/xml?depth=1&xpath=/..." sed -e "s#<module>$http[^<>]\+$</module><revision>$[0-9]\+$</revision>#\1\@\2\n#g" ${rl}.xml | \ sed -e "s#<kind>$[^<>]\+$</kind>#\1\n#g" | sed -e "s#<[^<>]\+>##g" > ${rl}.txt

15 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r28410 - trunk/build/aggregate/site.

by jbosstools-commits＠lists.jboss.org

Author: nickboldt Date: 2011-01-19 18:19:34 -0500 (Wed, 19 Jan 2011) New Revision: 28410 Modified: trunk/build/aggregate/site/build.xml Log: add fetch for build.properties file so we can later collect metadata Modified: trunk/build/aggregate/site/build.xml =================================================================== --- trunk/build/aggregate/site/build.xml 2011-01-19 23:07:50 UTC (rev 28409) +++ trunk/build/aggregate/site/build.xml 2011-01-19 23:19:34 UTC (rev 28410) @@ -59,21 +59,28 @@  <var unset="true" name="ALL_ZIPS" /> <var unset="true" name="wget.return" /> -  <exec executable="wget" dir="${aggegate.zips.dir}" failonerror="false" failifexecutionfails="true" resultproperty="wget.return" outputproperty="null"> <arg line="${location.cleaned}/logs/zip.list.txt -q --no-clobber" /> </exec> -  -  + <echo level="verbose">Fetch SVN_REVISION.txt if it exists (return 8 if not found)</echo> <var name="svnRevTXT" value="${aggegate.zips.dir}/SVN_REVISION.txt" /> - <var name="svnRevXML" value="${aggegate.zips.dir}/SVN_REVISION.xml" /> <exec executable="wget" dir="${aggegate.zips.dir}" failonerror="false" failifexecutionfails="true" resultproperty="wget.return" outputproperty="null"> <arg line="${location.cleaned}/logs/SVN_REVISION.txt -q --no-clobber" /> </exec> + + <echo level="verbose">Fetch SVN_REVISION.xml if it exists (return 8 if not found)</echo> + <var name="svnRevXML" value="${aggegate.zips.dir}/SVN_REVISION.xml" /> <exec executable="wget" dir="${aggegate.zips.dir}" failonerror="false" failifexecutionfails="true" resultproperty="wget.return" outputproperty="null"> <arg line="${location.cleaned}/logs/SVN_REVISION.xml -q --no-clobber" /> </exec> + + <echo level="verbose">Fetch build.properties if it exists (return 8 if not found)</echo> + <var name="buildProperties" value="${aggegate.zips.dir}/build.properties" /> + <exec executable="wget" dir="${aggegate.zips.dir}" failonerror="false" failifexecutionfails="true" resultproperty="wget.return" outputproperty="null"> + <arg line="${location.cleaned}/logs/build.properties -q --no-clobber" /> + </exec> + <if> <and> <equals arg1="${wget.return}" arg2="0" /> @@ -90,12 +97,19 @@ <for list="${ALL_ZIPS}" delimiter=", " keepgoing="true" param="zipPath"> <sequential> <propertyregex override="true" property="relativePath" defaultvalue="" input="@{zipPath}" regexp="(.+)/([^/]+.zip)" replace="\1" /> + <propertyregex override="true" property="svnrevPath" defaultvalue="" input="@{zipPath}" regexp=".zip" replace=".SVN_REVISION" /> + <propertyregex override="true" property="svnrevPath" defaultvalue="${svnrevPath}" input="${svnrevPath}" regexp="-Sources-|-Update-" replace="-" /> + + <propertyregex override="true" property="buildPropertiesPath" defaultvalue="" input="@{zipPath}" regexp=".zip" replace=".build.properties" /> + <propertyregex override="true" property="buildPropertiesPath" defaultvalue="${buildPropertiesPath}" input="${buildPropertiesPath}" regexp="-Sources-|-Update-" replace="-" /> + <mkdir dir="${aggegate.zips.dir}/${relativePath}" />  <echo level="verbose">repoNum = @{repoNum} relativePath = ${relativePath} svnrevPath = ${svnrevPath} +buildPropertiesPath = ${buildPropertiesPath} zipPath = @{zipPath} DEST = ${aggegate.zips.dir}/@{zipPath} </echo> @@ -120,6 +134,8 @@ </if> </else> </if> + +  <if> <available file="${svnRevTXT}" type="file" /> <then> @@ -132,11 +148,17 @@ <copy file="${svnRevXML}" tofile="${aggegate.zips.dir}/${svnrevPath}.xml" /> </then> </if> - + <if> + <available file="${buildProperties}" type="file" /> + <then> + <copy file="${buildProperties}" tofile="${aggegate.zips.dir}/${buildPropertiesPath}.txt" /> + </then> + </if> </sequential> </for> <var name="relativePath" unset="true" /> <var name="svnrevPath" unset="true" /> + <var name="buildPropertiesPath" unset="true" /> </then> </if> <var unset="true" name="ALL_ZIPS" /> @@ -147,7 +169,9 @@ </else> </if> <var name="location.cleaned" unset="true" /> - <delete file="${svnRevFile}" quiet="true" /> + <delete file="${svnRevXML}" quiet="true" /> + <delete file="${svnRevTXT}" quiet="true" /> + <delete file="${buildProperties}" quiet="true" /> <var name="svnRevFile" unset="true" /> </sequential> </macrodef> @@ -353,15 +377,26 @@ </antcall> </target> - <target name="test.collect.zips.from.list" depends="init"> + <target name="test.collect.zips.from.list.xml" depends="init"> <property name="isTest" value="true" /> <antcall target="collect.zips"> + <param name="inputRepos" value="1,2,3" /> + <param name="inputRepo1" value="http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.2_trunk...." /> + <param name="inputRepo2" value="http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.2_trunk...." /> + <param name="inputRepo3" value="http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.2_trunk...." /> + </antcall> + </target> + + <target name="test.collect.zips.from.list.txt" depends="init"> + <property name="isTest" value="true" /> + <antcall target="collect.zips"> <param name="inputRepos" value="1,2,3,4,5" /> - <param name="inputRepo1" value="http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.2_trunk...." /> + <param name="inputRepo1" value="http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.2_trunk...." /> <param name="inputRepo2" value="http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.2_trunk...." /> <param name="inputRepo3" value="http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.2_trunk...." /> <param name="inputRepo4" value="http://download.jboss.org/jbosstools/builds/staging/jbosstools-savara-1.1..." /> <param name="inputRepo5" value="http://download.jboss.org/jbosstools/builds/staging/jbosstools-savara-1.1..." /> + </antcall> </target> @@ -373,7 +408,7 @@ </antcall> </target> - <target name="test.collect.zips" depends="test.collect.zips.from.metadata,test.collect.zips.from.list"> + <target name="test.collect.zips" depends="test.collect.zips.from.metadata,test.collect.zips.from.list.txt,test.collect.zips.from.list.xml"> <delete dir="${aggegate.zips.dir}" quiet="true" /> </target> @@ -381,7 +416,7 @@ <delete dir="${aggegate.zips.dir}" quiet="true" /> </target> - <target name="collect.metadata" description="collect svn revision files + other metadata (JOB_NAME BUILD_ID, BUILD_NUMBER, WORKSPACE, HUDSON_SLAVE)"> + <target name="collect.metadata" description="collect svn revision files + other metadata (JOB_NAME, BUILD_ID, BUILD_NUMBER, WORKSPACE, HUDSON_SLAVE)">  </target>

15 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r28409 - trunk/jbpm/docs/reference/en-US.

by jbosstools-commits＠lists.jboss.org

Author: mcaspers Date: 2011-01-19 18:07:50 -0500 (Wed, 19 Jan 2011) New Revision: 28409 Modified: trunk/jbpm/docs/reference/en-US/tasks.xml Log: General Updates Modified: trunk/jbpm/docs/reference/en-US/tasks.xml =================================================================== --- trunk/jbpm/docs/reference/en-US/tasks.xml 2011-01-19 22:35:33 UTC (rev 28408) +++ trunk/jbpm/docs/reference/en-US/tasks.xml 2011-01-19 23:07:50 UTC (rev 28409) @@ -192,35 +192,19 @@ <title>Actions : The JBoss jBPM Integration Mechanism</title> - <para> In this chapter we will show how to do software integration with <property>JBoss - jBPM</property>. The standard mechanism to implement this is to wrap the functionality you - want to integrate in a class that implements the <emphasis> - <property>ActionHandler</property> - </emphasis> interface. In order to demonstrate it let's specify Hello World action for our - process.</para> + <para> + This chapter will demonstrate how to integrate with <property>JBoss jBPM</property>. The standard mechanism to implement this is to wrap the functionality you want to integrate in a class that implements the <emphasis><property>ActionHandler</property></emphasis> interface. In order to demonstrate it let's specify a simple Hello World action for our process. + </para> <section> <title>Creating a Hello World Action</title> - <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 <emphasis> - <property>ActionHandler</property> - </emphasis> interface, and attach this piece of code to a particular event. These events - are amongst others, going over a transition, leaving or entering nodes, after and before - signalling. </para> + <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 <emphasis><property>ActionHandler</property></emphasis> interface, and attach this piece of code to a particular event. These events are amongst others, going over a transition, leaving or entering nodes, after and before signaling. + </para> - <para> To make things a little bit more concrete, let's create a new class called <emphasis> - <property>HelloActionHandler</property>. - </emphasis> For that firstly we'll create a new package <emphasis> - <property>com.jbay.action</property> - </emphasis> in the <emphasis> - <property>src/java/main</property> - </emphasis> folder of our project. Then, we should call New Class Creation wizard as - usual by right-clicking and navigating <emphasis> - <property>New > Class</property>. - </emphasis> + <para> + To make things a little bit more concrete, let's create a new class called <emphasis><property>HelloActionHandler</property></emphasis>. For that firstly we will create a new package <code>com.jbay.action</code> in the <filename>src/java/main</filename> folder of our project. Then, we should call New Class Creation wizard as usual selecting <menuchoice><guimenuitem>New</guimenuitem><guimenuitem>Class</guimenuitem></menuchoice> from the context menu. </para> <figure> @@ -233,29 +217,17 @@ </mediaobject> </figure> - <para>Notice that two first gaps have been filled automatically. Here, instead of <emphasis> - <property>Package</property> - </emphasis> option <emphasis> - <property>Enclose type</property> - </emphasis> option can be selected where a type in which to enclose a new class should - be specified.</para> + <para> + Notice that two first gaps have been filled automatically. Here, instead of the <emphasis><property>Package</property></emphasis> option, the <emphasis><property>Enclose type</property></emphasis> option can be selected to define the type in which the new class should be created will be enclosed. + </para> - <para>In our case, we leave everything as it is, just type <emphasis> - <property>HelloActionHandler</property> - </emphasis> as a name of new class and add <emphasis> - <property>org.jbpm.graph.ActionHendler</property> - </emphasis> interface as it's shown in the picture above.</para> + <para> + In our case, we leave everything as it is, just type <code>HelloActionHandler</code> as a name of new class and add <code>org.jbpm.graph.ActionHendler</code> interface as it is shown in the picture above. + </para> - <para>Thus, our <emphasis> - <property>HelloActionHandler</property> - </emphasis> implements the <emphasis> - <property>ActionHandler</property> - </emphasis> interface including the <emphasis> - <property>execute</property> - </emphasis> method as shown in the next figure. Here, we add a variable named <emphasis> - <property>greeting</property> - </emphasis> to the collection of process variables and put a message in it : - <emphasis>"Hello from ActionHandler"</emphasis>. </para> + <para> + Thus, our <code>HelloActionHandler</code> implements the <code>ActionHandler</code> interface, including the <code>execute</code> method as shown in the next figure. Here, we add a variable named <code>greeting</code> to the collection of process variables and put a message in it: <code>"Hello from ActionHandler"</code>. + </para> <figure> <title>A Simple Hello Action</title> @@ -267,27 +239,23 @@ </mediaobject> </figure> - <para>Now, as we have <emphasis> - <property>HelloActionHandler</property> - </emphasis> class defined, let's explore how we can handle it.</para> + <para>Now, as we have <code>HelloActionHandler</code> class defined, let's explore how we can handle it.</para> </section> <section> <title>Integrating the Hello World Action</title> - <para>The main purpose of this chapter is to provide you with the steps associating our - Hello World action with a particular event and test the correctness of our actions as - well.</para> + <para> + The main purpose of this chapter is to provide you with the steps required to associate our Hello World action with a particular event and test the validity of our actions as well. + </para> - <para> As good Testcity citizens we will first create a Unit Test that proves the behaviour - we want to achieve by adding the <emphasis> - <property>ActionHandler</property> - </emphasis> to the process. So we implement another test.</para> + <para> + In order to validate our code we will first create a Unit Test that proves the behavior we want to achieve by adding the <code>ActionHandler</code> to the process. So we implement another test. + </para> - <para>At first, let's return to the - code we already saw in the previous chapter and add new test method <emphasis> - <property>testActionHendler</property> - </emphasis> to it. </para> + <para> + At first, let's return to the code we already saw in the previous chapter and add new test method <code>testActionHendler</code> to it. + </para> <figure> <title>Create the Hello Action Test</title> @@ -299,24 +267,14 @@ </mediaobject> </figure> - <para>We assert - that no variable called <emphasis> - <property>greeting</property> - </emphasis> exist. Then we give the process a signal to move it to the auction state. We - want to associate the execution of the action with the event of going over the - transition from the start state to the auction state. So after the signal, the process - should be in the auction state as in the previous scenario. But moreover, the <emphasis> - <property>greeting</property> - </emphasis> variable should exist and contain the string <emphasis>"Hello from - ActionHandler"</emphasis>. That's what we assert in the last lines of the test - method.</para> - - + <para> + We assert that no variable called <code>greeting</code> exist. Then we give the process a signal to move it to the action state. We want to associate the execution of the action with the event of going over the transition from the start state to the action state. So after the signal, the process should be in the action state as in the previous scenario. But moreover, the <code>greeting</code> variable should exist and contain the string <code>"Hello from ActionHandler"</code>. That is what we assert in the last lines of the test method. + </para> + + <para> + Running the tests now results in a failure. The point is that we did not associate the action with any particular event in the process definition, so the process variable did not get set. + </para> - <para> Running the tests now results in a failure. The point is that we did not associate - the action with any particular event in the process definition, so the process variable - did not get set. </para> - <figure> <title>Test Results Before Integration</title> @@ -327,12 +285,9 @@ </mediaobject> </figure> - <para> Let's do something about it and add an action to the first transition of our - sample process. To do this you can use the Actions tab in the Properties Editor that is - under the graphical canvas. Bring up the popup menu of the action element container and - chose New Action as it's shown on the figure below. The other way to add an action - to the transition is simply to use the dropdown menu that is available under the action - icon in the right upper corner of the Properties View.</para> + <para> + Let's do something about it and add an action to the first transition of our sample process. To do this you can use the Actions tab in the Properties Editor that is under the graphical canvas. Bring up the popup menu of the action element container and chose New Action as it's shown on the figure below. The other way to add an action to the transition is simply to use the dropdown menu that is available under the action icon in the right upper corner of the Properties View. + </para> <figure> <title>Adding an Action to a Transition</title> @@ -356,10 +311,9 @@ </mediaobject> </figure> - <para>The first of these three pages allows you to give the Action a name. The last page - contains some advanced attributes such as whether the Action is asynchronous. The - Details page is the most important. It allows to choose and configure the actual action - handler implementation. </para> + <para> + The first of these three pages allows you to give the Action a name. The last page contains some advanced attributes such as whether the Action is asynchronous. The Details page is the most important. It allows to choose and configure the actual action handler implementation. + </para> <figure> <title>The Details page of an Action Configuration Dialog</title> @@ -372,9 +326,7 @@ </figure> - <para>Clicking on the <emphasis> - <property>Search...</property> - </emphasis> button brings us to a Choose Class dialog.</para> + <para>Clicking on the <guibutton>Search...</guibutton> button brings us to a Choose Class dialog.</para> <figure> @@ -388,9 +340,9 @@ </figure> - <para> We choose our previously created 'HelloActionHandler' class and - push the <property>OK</property> button. After the selection of the action handler for - the action, we can run the test and observe it gives us a green light.</para> + <para> + We choose our previously created <code>HelloActionHandler</code> class and click the <guibutton>OK</guibutton> button. After selecting the action handler for the action, we can run the test and observe it gives us a green light. + </para> <figure> <title>Test Results</title> @@ -408,11 +360,9 @@ <section> <title> Integration Points</title> - <para> The different integration points in a process definition are thoroughly documented in - the <ulink url="http://docs.jboss.com/jbpm/v3/userguide/">JBoss jBPM User Guide</ulink>. Instance nodes can contain many action - elements. Each of these will appear in the Action element list of the Actions tab. But - each Action also has a properties view of itself. You can navigate to this view by - selecting the added Action in the outline view. </para> + <para> + The different integration points in a process definition are thoroughly documented in the <ulink url="http://docs.jboss.com/jbpm/v3/userguide/">JBoss jBPM User Guide</ulink>. Instance nodes can contain many action elements. Each of these will appear in the Action element list of the Actions tab. But each Action also has a properties view of itself. You can navigate to this view by selecting the added Action in the outline view. + </para> </section> </section> @@ -421,23 +371,14 @@ <title>Quick Howto Guide</title> - <para>This chapter contains additional information related to the <property>JBoss - jBPM</property>.</para> + <para>This chapter contains additional information related to the <property>JBoss jBPM</property>.</para> <section id="change_core_jbpm_inst"> <title>Change the Default Core jBPM Installation</title> - <para> You can change the default <property>jBPM</property> installation by means of the - Eclipse preference mechanism. Open the Preferences dialog by selecting <emphasis> - <property>Window > Preferences</property> - </emphasis> and select the <emphasis> - <property>JBoss jBPM > Runtime Location</property> - </emphasis> 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 <property>jBPM</property> - installation that's being referenced by a project however will cause the - classpath to contain errors. </para> + <para> + You can change the default <property>jBPM</property> installation by means of the Eclipse preference mechanism. Open the Preferences dialog by selecting <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Preferences</guimenuitem></menuchoice> and select the <guilabel>JBoss jBPM > Runtime Location</guilabel> 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 <property>jBPM</property> installation that is being referenced by a project however will cause the classpath to contain errors. + </para> <figure> @@ -456,10 +397,9 @@ <para>Here, we'll examine how you can configure the Task nodes in jBPM jPDL GPD.</para> - <para> You can add Tasks to Task nodes and then configure them in a similar manner as the - Action configuration mechanism. Let's consider the process definition similar - to the previous one that contains three nodes: Start state, Task node and End state. The - <property>Properties view</property> for selected Task node includes several tabs. </para> + <para> + You can add Tasks to Task nodes and then configure them in a similar manner Actions are configured. Let's consider the process definition similar to the previous one that contains three nodes: Start state, Task node and End state. The <property>Properties view</property> for the selected Task node includes several tabs. + </para> <figure> <title>The Properties View of the selected Task Node</title> @@ -470,8 +410,9 @@ </mediaobject> </figure> - <para>We should choose the Task tab and then bring up the context menu or click the button - in the top right corner of the view to add a Task to our Task node.</para> + <para> + We should choose the Task tab and then bring up the context menu or click the button in the top right corner of the view to add a Task to our Task node. + </para> <figure> <title>Adding a Task to the Task Node</title> @@ -482,8 +423,7 @@ </mediaobject> </figure> - <para>Every added Task has its own configuration possibilities. You can access them through - the <property>Properties view</property> as well.</para> + <para>Every added Task has its own configuration possibilities. You can access them through the <property>Properties view</property> as well.</para> <figure> <title>The Task properties</title> @@ -494,10 +434,9 @@ </mediaobject> </figure> - <para>The <property>General page</property> is a place where you can specify the name of a - Task and its description. For instance, let it be <emphasis> - <property>approve oder</property> - </emphasis> with appropriate description that you can see in the figure below.</para> + <para> + The <property>General page</property> is a place where you can specify the name of a Task and its description. For instance, let it be <emphasis><property>approve oder</property></emphasis> with appropriate description that you can see in the figure below. + </para> <figure> <title>The Task General Page</title> @@ -508,16 +447,9 @@ </mediaobject> </figure> - <para>Now, look at <property>Details page</property>. First, you should specify the due date - that is a mandatory property for the Task. The due date is the date on which the task - should be accomplished. Here you can also set a Task priority as well as signalling, - notifying or blocking. The <emphasis> - <property>Blocking</property> - </emphasis> attribute indicates that the process will not be able to continue if this - task is still unaccomplished. The <emphasis> - <property>Generate Form...</property> - </emphasis> button is for creating a simple task form that can be rendered by the jBPM - console.</para> + <para> + Now, look at <property>Details page</property>. First, you should specify the due date that is a mandatory property for the Task. The due date is the date on which the task should be accomplished. Here you can also set a Task priority as well as signaling, notifying or blocking. The <emphasis><property>Blocking</property></emphasis> attribute indicates that the process will not be able to continue if this task is still unaccomplished. The <guibutton>Generate Form...</guibutton> button is for creating a simple task form that can be rendered by the jBPM console. + </para> <figure> <title>The Task Details Page</title> @@ -528,14 +460,9 @@ </mediaobject> </figure> - <para>For our example, we specify the due date as 2 business days, choose the high priority - and also check the <emphasis> - <property>Signalling</property> - </emphasis> and <emphasis> - <property>Notify</property> - </emphasis> attributes. It means that the Task should be accomplished in 2 business days - and the assignee will be notified by email when the task is assigned. To specify how the - Task should be assigned switch on to the <property>Assignment page</property>.</para> + <para> + For our example, we specify the due date as 2 business days, choose the high priority and also check the <emphasis><property>Signaling</property></emphasis> and <emphasis><property>Notify</property></emphasis> attributes. It means that the Task should be accomplished in 2 business days and the assignee will be notified by email when the task is assigned. To specify how the Task should be assigned switch on to the <property>Assignment page</property>. + </para> <figure> <title>The Task Assignment Page</title> @@ -546,8 +473,7 @@ </mediaobject> </figure> - <para>On the <property>Reminder page</property> you can specify whether the assignee will be reminded of the task - that awaits him.</para> + <para>On the <property>Reminder page</property> you can specify whether the assignee will be reminded of the task that awaits him.</para> <figure> <title>The Task Reminder Page</title> @@ -558,8 +484,7 @@ </mediaobject> </figure> - <para>In our case, the assignee will be reminded by email after two business hours and - continue to get reminding every business hour after that.</para> + <para>In our case, the assignee will be reminded by email after two business hours and continue to get reminding every business hour after that.</para> <para>In the next figure you can see our configuring generated into XML.</para> <figure> <title>The Task Reminder Page</title> @@ -569,8 +494,9 @@ </imageobject> </mediaobject> </figure> - <para>We hope, our guide will help you to get started with the jPDL process language and jBPM - workflow on the whole. Besides, for additional information you are welcome on <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss forum</ulink>.</para> + <para> + We hope, our guide will help you to get started with the jPDL process language and jBPM workflow on the whole. Besides, for additional information you are welcome on <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss forum</ulink>. + </para> </section> </section>

15 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r28408 - trunk/build/aggregate/site.

by jbosstools-commits＠lists.jboss.org

Author: nickboldt Date: 2011-01-19 17:35:33 -0500 (Wed, 19 Jan 2011) New Revision: 28408 Modified: trunk/build/aggregate/site/build.xml Log: collect .xml and .txt files for SVN_REVISION from upstream builds while collecting their .zip files Modified: trunk/build/aggregate/site/build.xml =================================================================== --- trunk/build/aggregate/site/build.xml 2011-01-19 22:35:08 UTC (rev 28407) +++ trunk/build/aggregate/site/build.xml 2011-01-19 22:35:33 UTC (rev 28408) @@ -42,6 +42,8 @@ </taskdef> </target> + <target name="custom.build" description="aggregate update site extras" depends="init,check.target,add.associate.sites,add.web.content,pack.zip,collect.zips,collect.metadata,create.summary.file" /> +  @@ -62,6 +64,16 @@ <arg line="${location.cleaned}/logs/zip.list.txt -q --no-clobber" /> </exec>  + +  + <var name="svnRevTXT" value="${aggegate.zips.dir}/SVN_REVISION.txt" /> + <var name="svnRevXML" value="${aggegate.zips.dir}/SVN_REVISION.xml" /> + <exec executable="wget" dir="${aggegate.zips.dir}" failonerror="false" failifexecutionfails="true" resultproperty="wget.return" outputproperty="null"> + <arg line="${location.cleaned}/logs/SVN_REVISION.txt -q --no-clobber" /> + </exec> + <exec executable="wget" dir="${aggegate.zips.dir}" failonerror="false" failifexecutionfails="true" resultproperty="wget.return" outputproperty="null"> + <arg line="${location.cleaned}/logs/SVN_REVISION.xml -q --no-clobber" /> + </exec> <if> <and> <equals arg1="${wget.return}" arg2="0" /> @@ -78,10 +90,12 @@ <for list="${ALL_ZIPS}" delimiter=", " keepgoing="true" param="zipPath"> <sequential> <propertyregex override="true" property="relativePath" defaultvalue="" input="@{zipPath}" regexp="(.+)/([^/]+.zip)" replace="\1" /> + <propertyregex override="true" property="svnrevPath" defaultvalue="" input="@{zipPath}" regexp=".zip" replace=".SVN_REVISION" /> <mkdir dir="${aggegate.zips.dir}/${relativePath}" />  <echo level="verbose">repoNum = @{repoNum} relativePath = ${relativePath} +svnrevPath = ${svnrevPath} zipPath = @{zipPath} DEST = ${aggegate.zips.dir}/@{zipPath} </echo> @@ -96,7 +110,6 @@ <exec executable="wget" dir="${aggegate.zips.dir}" failonerror="false" failifexecutionfails="false" resultproperty="wget.return" outputproperty="null"> <arg line="${location.cleaned}/@{zipPath} -q --no-clobber" /> </exec> -  <if> <not> <equals arg1="${wget.return}" arg2="0" /> @@ -107,9 +120,23 @@ </if> </else> </if> + <if> + <available file="${svnRevTXT}" type="file" /> + <then> + <copy file="${svnRevTXT}" tofile="${aggegate.zips.dir}/${svnrevPath}.txt" /> + </then> + </if> + <if> + <available file="${svnRevXML}" type="file" /> + <then> + <copy file="${svnRevXML}" tofile="${aggegate.zips.dir}/${svnrevPath}.xml" /> + </then> + </if> + </sequential> </for> <var name="relativePath" unset="true" /> + <var name="svnrevPath" unset="true" /> </then> </if> <var unset="true" name="ALL_ZIPS" /> @@ -120,6 +147,8 @@ </else> </if> <var name="location.cleaned" unset="true" /> + <delete file="${svnRevFile}" quiet="true" /> + <var name="svnRevFile" unset="true" /> </sequential> </macrodef> @@ -308,8 +337,6 @@ </for> </target> - <target name="custom.build" description="aggregate update site extras" depends="init,check.target,add.associate.sites,add.web.content,pack.zip,collect.zips" /> - <target name="test.collect.zips.from.metadata" depends="init"> <property name="isTest" value="true" /> <antcall target="collect.zips"> @@ -354,4 +381,20 @@ <delete dir="${aggegate.zips.dir}" quiet="true" /> </target> + <target name="collect.metadata" description="collect svn revision files + other metadata (JOB_NAME BUILD_ID, BUILD_NUMBER, WORKSPACE, HUDSON_SLAVE)"> +  + </target> + + <target name="create.summary.file" description="create summary file with list of generated files, sizes, and SVN revisions all linked and ordered by source build job"> +  + </target> + + <target name="test.create.summary.file" depends="test.collect.zips"> + <property name="isTest" value="true" /> + <antcall target="collect.metadata"> + </antcall> + <antcall target="create.summary.file"> + </antcall> + </target> + </project>

15 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r28407 - trunk/build.

by jbosstools-commits＠lists.jboss.org

Author: nickboldt Date: 2011-01-19 17:35:08 -0500 (Wed, 19 Jan 2011) New Revision: 28407 Modified: trunk/build/publish.sh Log: publish.sh now uses Hudson xml api to fetch SVN_REVISION and creates both xml and txt files Modified: trunk/build/publish.sh =================================================================== --- trunk/build/publish.sh 2011-01-19 19:08:40 UTC (rev 28406) +++ trunk/build/publish.sh 2011-01-19 22:35:08 UTC (rev 28407) @@ -52,27 +52,13 @@ bl=${STAGINGDIR}/logs/BUILDLOG.txt wget -q http://hudson.qa.jboss.com/hudson/job/${JOB_NAME}/${BUILD_NUMBER}/console... -O ${bl} -# JBDS-1361 - instead of SVN_REVISION, scrape ${bl} (BUILDLOG.txt) -# Updating http://anonsvn.jboss.org/repos/tdesigner/branches/7.1 -# ... -# At revision 1063 -# Updating http://anonsvn.jboss.org/repos/jbosstools/trunk/build -# ... -# At revision 25503 -# -- or -- -# Checking out https://svn.jboss.org/repos/jbosstools/branches/jbosstools-3.2.0.Beta1 -# ... -# At revision 25538 -rl=${STAGINGDIR}/logs/SVN_REVISION.txt +# JBDS-1361 - fetch XML and then sed it into plain text +rl=${STAGINGDIR}/logs/SVN_REVISION +rm -f ${rl}.txt ${rl}.xml +wget -q --no-clobber -O ${rl}.xml "http://hudson.qa.jboss.com/hudson/job/${JOB_NAME}/${BUILD_NUMBER}/api/xml..." +sed -e "s#<module>$http[^<>]\+$</module><revision>$[0-9]\+$</revision>#\1\@\2\n#g" ${rl}.xml | \ + sed -e "s#<kind>$[^<>]\+$</kind>#\1\n#g" | sed -e "s#<[^<>]\+>##g" > ${rl}.txt -# convert input above to: -# http://anonsvn.jboss.org/repos/tdesigner/branches/7.1@1063 -# http://anonsvn.jboss.org/repos/jbosstools/trunk/build@25503 -# https://svn.jboss.org/repos/jbosstools/branches/jbosstools-3.2.0.Beta1@25538 -sed -ne "/Updating $http.\+$\|Checking out $http.\+$\|At revision $[0-9]\+$/ p" ${bl} | \ - sed -e "/At revision/ s/At revision /\@/" | sed -e N -e '/http/ s/\n//' | \ - sed -e "/Checking out\|Updating/,+1 s/$Checking out \|Updating $$.\+$/\2/g" > ${rl} - METAFILE="${BUILD_ID}-H${BUILD_NUMBER}.txt" if [[ ${SVN_REVISION} ]]; then METAFILE="${BUILD_ID}-H${BUILD_NUMBER}-r${SVN_REVISION}.txt" Property changes on: trunk/build/publish.sh ___________________________________________________________________ Name: svn:executable + *

15 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r28406 - branches/jbosstools-3.2.0.CR1/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench.

by jbosstools-commits＠lists.jboss.org

Author: vyemialyanchyk Date: 2011-01-19 14:08:40 -0500 (Wed, 19 Jan 2011) New Revision: 28406 Modified: branches/jbosstools-3.2.0.CR1/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/LazyDatabaseSchemaWorkbenchAdapter.java Log: https://issues.jboss.org/browse/JBIDE-8155 - fixed Modified: branches/jbosstools-3.2.0.CR1/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/LazyDatabaseSchemaWorkbenchAdapter.java =================================================================== --- branches/jbosstools-3.2.0.CR1/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/LazyDatabaseSchemaWorkbenchAdapter.java 2011-01-19 19:04:24 UTC (rev 28405) +++ branches/jbosstools-3.2.0.CR1/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/LazyDatabaseSchemaWorkbenchAdapter.java 2011-01-19 19:08:40 UTC (rev 28406) @@ -56,7 +56,9 @@ @SuppressWarnings("unchecked") public synchronized Object[] getChildren(Object o, final IProgressMonitor monitor) { LazyDatabaseSchema dbs = getLazyDatabaseSchema( o ); + ConsoleConfiguration consoleConfiguration = dbs.getConsoleConfiguration(); + try{ DefaultDatabaseCollector db = readDatabaseSchema(monitor, consoleConfiguration, dbs.getReverseEngineeringStrategy()); @@ -113,16 +115,15 @@ JDBCReader reader = JDBCReaderFactory.newJDBCReader(configuration.getProperties(), settings, strategy); db = new DefaultDatabaseCollector(reader.getMetaDataDialect()); reader.readDatabaseSchema(db, settings.getDefaultCatalogName(), settings.getDefaultSchemaName(), new ProgressListenerMonitor(monitor)); - return db; } catch(HibernateException he) { - HibernateConsolePlugin.getDefault().logErrorMessage(HibernateConsoleMessages.LazyDatabaseSchemaWorkbenchAdapter_problem_while_reading_database_schema, he); + throw he; } finally { if (connectionProvider!=null) { connectionProvider.close(); } } - return null; + return db; } }); }

15 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r28405 - trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench.

by jbosstools-commits＠lists.jboss.org

Author: vyemialyanchyk Date: 2011-01-19 14:04:24 -0500 (Wed, 19 Jan 2011) New Revision: 28405 Modified: trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/LazyDatabaseSchemaWorkbenchAdapter.java Log: https://issues.jboss.org/browse/JBIDE-8155 - fixed Modified: trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/LazyDatabaseSchemaWorkbenchAdapter.java =================================================================== --- trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/LazyDatabaseSchemaWorkbenchAdapter.java 2011-01-19 18:48:26 UTC (rev 28404) +++ trunk/hibernatetools/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/workbench/LazyDatabaseSchemaWorkbenchAdapter.java 2011-01-19 19:04:24 UTC (rev 28405) @@ -115,16 +115,15 @@ JDBCReader reader = JDBCReaderFactory.newJDBCReader(configuration.getProperties(), settings, strategy); db = new DefaultDatabaseCollector(reader.getMetaDataDialect()); reader.readDatabaseSchema(db, settings.getDefaultCatalogName(), settings.getDefaultSchemaName(), new ProgressListenerMonitor(monitor)); - return db; } catch(HibernateException he) { - HibernateConsolePlugin.getDefault().logErrorMessage(HibernateConsoleMessages.LazyDatabaseSchemaWorkbenchAdapter_problem_while_reading_database_schema, he); + throw he; } finally { if (connectionProvider!=null) { connectionProvider.close(); } } - return null; + return db; } }); }

15 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r28404 - trunk/as/plugins/org.jboss.ide.eclipse.as.rse.core/src/org/jboss/ide/eclipse/as/rse/core.

by jbosstools-commits＠lists.jboss.org

Author: rob.stryker(a)jboss.com Date: 2011-01-19 13:48:26 -0500 (Wed, 19 Jan 2011) New Revision: 28404 Modified: trunk/as/plugins/org.jboss.ide.eclipse.as.rse.core/src/org/jboss/ide/eclipse/as/rse/core/RSELaunchDelegate.java Log: JBIDE-7753 - adds a 10 second delay as a quick fix for now. Modified: trunk/as/plugins/org.jboss.ide.eclipse.as.rse.core/src/org/jboss/ide/eclipse/as/rse/core/RSELaunchDelegate.java =================================================================== --- trunk/as/plugins/org.jboss.ide.eclipse.as.rse.core/src/org/jboss/ide/eclipse/as/rse/core/RSELaunchDelegate.java 2011-01-19 16:19:02 UTC (rev 28403) +++ trunk/as/plugins/org.jboss.ide.eclipse.as.rse.core/src/org/jboss/ide/eclipse/as/rse/core/RSELaunchDelegate.java 2011-01-19 18:48:26 UTC (rev 28404) @@ -35,6 +35,7 @@ import org.eclipse.rse.services.shells.IShellService; import org.eclipse.rse.subsystems.shells.core.subsystems.servicesubsystem.IShellServiceSubSystem; import org.eclipse.wst.server.core.IServer; +import org.eclipse.wst.server.core.model.ServerBehaviourDelegate; import org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller; import org.jboss.ide.eclipse.as.core.server.internal.JBossServer; import org.jboss.ide.eclipse.as.core.server.internal.JBossServerBehavior; @@ -86,14 +87,7 @@ try { hs = service.runCommand("/", command, new String[]{}, new NullProgressMonitor()); hs.addOutputListener(listener); - int x = 0; - while( x < 30000) { - x+=1000; - try { - Thread.sleep(1000); - } catch(InterruptedException ie) { - } - } + delay(30); // Now launch ping thread } catch(SystemMessageException sme) { @@ -114,6 +108,18 @@ beh.setServerStarted(); } + private static void delay(int delay) { + int x = 1; + while( x < (delay)) { + x+=1; + try { + Thread.sleep(1000); + } catch(InterruptedException ie) { + } + } + } + + public static void launchCommandNoResult(JBossServerBehavior behaviour, int delay, String command) { IShellService service = null; try { @@ -125,11 +131,7 @@ try { final IHostShell hs = service.runCommand("/", command, new String[]{}, new NullProgressMonitor()); if( hs != null ) { - try { - Thread.sleep(delay); - } catch(InterruptedException ie) { - // ignore - } + delay(delay/1000); } } catch( SystemMessageException sme) { // TODO @@ -159,7 +161,7 @@ } behaviour.setServerStopping(); - + final JBossServerBehavior behaviour2 = behaviour; final String command = command2; IShellService service = null; try { @@ -182,10 +184,10 @@ if( saving[0] ) { output[0] = out[i].getString(); saving[0] = false; - try { - Thread.sleep(1000); - } catch(InterruptedException ie) {} + delay(10); + behaviour2.setServerStopped(); hs.exit(); + return; } /* * This is an extreme hack, because for some reason, @@ -202,7 +204,6 @@ } }); - behaviour.setServerStopped(); } catch( SystemMessageException sme) { // TODO behaviour.setServerStarted(); // unable to stop the server

15 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbosstools-commits January 2011