December 2007 - jbosstools-commits

JBoss Tools SVN: r5466 - in trunk/seam/tests/org.jboss.tools.seam.core.test: src/org/jboss/tools/seam/core/test and 1 other directory.

by jbosstools-commits＠lists.jboss.org

Author: dazarov Date: 2007-12-28 07:09:06 -0500 (Fri, 28 Dec 2007) New Revision: 5466 Added: trunk/seam/tests/org.jboss.tools.seam.core.test/projects/SeamWebWarTestProject/src/action/org/domain/SeamWebWarTestProject/session/ContextVariableTest.2 trunk/seam/tests/org.jboss.tools.seam.core.test/projects/SeamWebWarTestProject/src/action/org/domain/SeamWebWarTestProject/session/ContextVariableTest.3 trunk/seam/tests/org.jboss.tools.seam.core.test/projects/SeamWebWarTestProject/src/action/org/domain/SeamWebWarTestProject/session/ContextVariableTest.java Modified: trunk/seam/tests/org.jboss.tools.seam.core.test/src/org/jboss/tools/seam/core/test/SeamValidatorsTest.java Log: http://jira.jboss.com/jira/browse/JBIDE-1550 Added: trunk/seam/tests/org.jboss.tools.seam.core.test/projects/SeamWebWarTestProject/src/action/org/domain/SeamWebWarTestProject/session/ContextVariableTest.2 =================================================================== --- trunk/seam/tests/org.jboss.tools.seam.core.test/projects/SeamWebWarTestProject/src/action/org/domain/SeamWebWarTestProject/session/ContextVariableTest.2 (rev 0) +++ trunk/seam/tests/org.jboss.tools.seam.core.test/projects/SeamWebWarTestProject/src/action/org/domain/SeamWebWarTestProject/session/ContextVariableTest.2 2007-12-28 12:09:06 UTC (rev 5466) @@ -0,0 +1,53 @@ +package org.domain.SeamWebWarTestProject.session; + +import java.util.ArrayList; +import java.util.List; + +import org.jboss.seam.annotations.Factory; +import org.jboss.seam.annotations.Name; +import org.jboss.seam.annotations.Role; +import org.jboss.seam.annotations.In; +import org.jboss.seam.annotations.Out; +import org.jboss.seam.annotations.Logger; +import org.jboss.seam.annotations.datamodel.DataModel; +import org.jboss.seam.log.Log; +import org.jboss.seam.core.FacesMessages; + +@Name("messageList") +@Role(name="messageList") +public class ContextVariableTest { + + @Logger private Log log; + + @In FacesMessages facesMessages; + + @Out(value="output") + private String output; + + public void contextVariableTest() + { + //implement your business logic here + log.info("contextVariableTest.contextVariableTest() action called"); + } + + @DataModel + private List<String> messageList=new ArrayList<String>(); + + @Factory("messageList") + public void findMessages() { + + } + + @Factory("messageList") + public void findMessages2() { + + } + + public List<String> getList(){ + return messageList; + } + + public String getOutput(){ + return output; + } +} Added: trunk/seam/tests/org.jboss.tools.seam.core.test/projects/SeamWebWarTestProject/src/action/org/domain/SeamWebWarTestProject/session/ContextVariableTest.3 =================================================================== --- trunk/seam/tests/org.jboss.tools.seam.core.test/projects/SeamWebWarTestProject/src/action/org/domain/SeamWebWarTestProject/session/ContextVariableTest.3 (rev 0) +++ trunk/seam/tests/org.jboss.tools.seam.core.test/projects/SeamWebWarTestProject/src/action/org/domain/SeamWebWarTestProject/session/ContextVariableTest.3 2007-12-28 12:09:06 UTC (rev 5466) @@ -0,0 +1,48 @@ +package org.domain.SeamWebWarTestProject.session; + +import java.util.ArrayList; +import java.util.List; + +import org.jboss.seam.annotations.Factory; +import org.jboss.seam.annotations.Name; +import org.jboss.seam.annotations.Role; +import org.jboss.seam.annotations.In; +import org.jboss.seam.annotations.Out; +import org.jboss.seam.annotations.Logger; +import org.jboss.seam.annotations.datamodel.DataModel; +import org.jboss.seam.log.Log; +import org.jboss.seam.core.FacesMessages; + +@Name("contextVariableTest") +@Role(name="role1") +public class ContextVariableTest { + + @Logger private Log log; + + @In("messageList5") FacesMessages facesMessages; + + @Out(value="output") + private String output; + + public void contextVariableTest() + { + //implement your business logic here + log.info("contextVariableTest.contextVariableTest() action called"); + } + + @DataModel + private List<String> messageList=new ArrayList<String>(); + + @Factory("messageList") + public void findMessages() { + + } + + public List<String> getList(){ + return messageList; + } + + public String getOutput(){ + return output; + } +} Added: trunk/seam/tests/org.jboss.tools.seam.core.test/projects/SeamWebWarTestProject/src/action/org/domain/SeamWebWarTestProject/session/ContextVariableTest.java =================================================================== --- trunk/seam/tests/org.jboss.tools.seam.core.test/projects/SeamWebWarTestProject/src/action/org/domain/SeamWebWarTestProject/session/ContextVariableTest.java (rev 0) +++ trunk/seam/tests/org.jboss.tools.seam.core.test/projects/SeamWebWarTestProject/src/action/org/domain/SeamWebWarTestProject/session/ContextVariableTest.java 2007-12-28 12:09:06 UTC (rev 5466) @@ -0,0 +1,48 @@ +package org.domain.SeamWebWarTestProject.session; + +import java.util.ArrayList; +import java.util.List; + +import org.jboss.seam.annotations.Factory; +import org.jboss.seam.annotations.Name; +import org.jboss.seam.annotations.Role; +import org.jboss.seam.annotations.In; +import org.jboss.seam.annotations.Out; +import org.jboss.seam.annotations.Logger; +import org.jboss.seam.annotations.datamodel.DataModel; +import org.jboss.seam.log.Log; +import org.jboss.seam.core.FacesMessages; + +@Name("contextVariableTest") +@Role(name="role1") +public class ContextVariableTest { + + @Logger private Log log; + + @In FacesMessages facesMessages; + + @Out(value="output") + private String output; + + public void contextVariableTest() + { + //implement your business logic here + log.info("contextVariableTest.contextVariableTest() action called"); + } + + @DataModel + private List<String> messageList=new ArrayList<String>(); + + @Factory("messageList") + public void findMessages() { + + } + + public List<String> getList(){ + return messageList; + } + + public String getOutput(){ + return output; + } +} Modified: trunk/seam/tests/org.jboss.tools.seam.core.test/src/org/jboss/tools/seam/core/test/SeamValidatorsTest.java =================================================================== --- trunk/seam/tests/org.jboss.tools.seam.core.test/src/org/jboss/tools/seam/core/test/SeamValidatorsTest.java 2007-12-28 11:34:08 UTC (rev 5465) +++ trunk/seam/tests/org.jboss.tools.seam.core.test/src/org/jboss/tools/seam/core/test/SeamValidatorsTest.java 2007-12-28 12:09:06 UTC (rev 5466) @@ -628,11 +628,61 @@ IPreferenceStore store = SeamCorePlugin.getDefault().getPreferenceStore(); System.out.println("UNKNOWN_EL_VARIABLE_NAME value- "+store.getString(SeamPreferences.UNKNOWN_EL_VARIABLE_NAME)); + ISeamProject seamProject = getSeamProject(project); + + IFile contextVariableTestFile = project.getFile("src/action/org/domain/SeamWebWarTestProject/session/ContextVariableTest.java"); + + refreshProject(project); + + int number = getMarkersNumber(contextVariableTestFile); + assertTrue("Problem marker was found in contextVariableTestFile.java", number == 0); + // Duplicate variable name System.out.println("Test - Duplicate variable name"); + IFile contextVariableTestFile2 = project.getFile("src/action/org/domain/SeamWebWarTestProject/session/ContextVariableTest.2"); + try{ + contextVariableTestFile.setContents(contextVariableTestFile2.getContents(), true, false, new NullProgressMonitor()); + contextVariableTestFile.touch(new NullProgressMonitor()); + }catch(Exception ex){ + JUnitUtils.fail("Error in changing 'ContextVariableTest.java' content to " + + "'ContextVariableTest.2'", ex); + } + + refreshProject(project); + + String[] messages = getMarkersMessage(contextVariableTestFile); + + assertTrue("Not all problem markers 'Duplicate variable name' was found", messages.length == 4); + + assertTrue("Problem marker 'Duplicate variable name' not found", "Duplicate variable name: messageList".equals(messages[0])); + + int[] lineNumbers = getMarkersNumbersOfLine(contextVariableTestFile); + + assertTrue("Problem marker has wrong line number", (lineNumbers[0] == 16)||(lineNumbers[0] == 17)||(lineNumbers[0] == 36)||(lineNumbers[0] == 41)); + // Unknown variable name System.out.println("Test - Unknown variable name"); + + IFile contextVariableTestFile3 = project.getFile("src/action/org/domain/SeamWebWarTestProject/session/ContextVariableTest.3"); + try{ + contextVariableTestFile.setContents(contextVariableTestFile3.getContents(), true, false, new NullProgressMonitor()); + contextVariableTestFile.touch(new NullProgressMonitor()); + }catch(Exception ex){ + JUnitUtils.fail("Error in changing 'ContextVariableTest.java' content to " + + "'ContextVariableTest.3'", ex); + } + + refreshProject(project); + + messages = getMarkersMessage(contextVariableTestFile); + + assertTrue("Problem marker 'Unknown variable name' not found", "Unknown context variable name: messageList5".equals(messages[0])); + + lineNumbers = getMarkersNumbersOfLine(contextVariableTestFile); + + assertTrue("Problem marker has wrong line number", lineNumbers[0] == 22); + } public void testExpressionLanguageValidator() {

16 years, 12 months

1
0
0 / 0

JBoss Tools SVN: r5465 - in trunk/jbpm/docs: build and 27 other directories.

by jbosstools-commits＠lists.jboss.org

Author: ochikvina Date: 2007-12-28 06:34:08 -0500 (Fri, 28 Dec 2007) New Revision: 5465 Added: trunk/jbpm/docs/build/ trunk/jbpm/docs/build/reference/ trunk/jbpm/docs/build/reference/en/ trunk/jbpm/docs/build/reference/en/html/ trunk/jbpm/docs/build/reference/en/html/GuidedTourJBossjBPMGPD.html trunk/jbpm/docs/build/reference/en/html/Quick_Howto_Guide.html trunk/jbpm/docs/build/reference/en/html/TargetAudience.html trunk/jbpm/docs/build/reference/en/html/Test_Drive_Proc_Development.html trunk/jbpm/docs/build/reference/en/html/The_JBoss_jBPM_Int_Mech.html trunk/jbpm/docs/build/reference/en/html/css/ trunk/jbpm/docs/build/reference/en/html/css/html.css trunk/jbpm/docs/build/reference/en/html/css/images/ trunk/jbpm/docs/build/reference/en/html/css/images/bg_table.gif trunk/jbpm/docs/build/reference/en/html/css/images/ico_important.gif trunk/jbpm/docs/build/reference/en/html/css/images/ico_note.gif trunk/jbpm/docs/build/reference/en/html/images/ trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/ trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/defaltImage.png trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_1.png trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_2.png trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_3.png trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_4.png trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_5.png trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_6.png trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_7.png trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_8.png trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_9.png trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/ trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/defaltImage.png trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc.png trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_1.png trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_1a.png trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_1b.png trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_2.png trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_2a.png trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_2b.png trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_3.png trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_4.png trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_5.png trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/ trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/defaltImage.png trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_1.png trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_10.png trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_2.png trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_3.png trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_4.png trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_5.png trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_6.png trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_7.png trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_8.png trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/ trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/default.png trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour1.png trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour10.png trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour11.png trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour12.png trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour13.png trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour14.png trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour15.png trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour2.png trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour2_b.png trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour3.png trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour4.png trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour5.png trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour6.png trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour7.png trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour8.png trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour9.png trunk/jbpm/docs/build/reference/en/html/images/runtime_installation/ trunk/jbpm/docs/build/reference/en/html/images/runtime_installation/runtime_installation1.png trunk/jbpm/docs/build/reference/en/html/images/the_views/ trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views.png trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views1.png trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views10.png trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views2.png trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views3.png trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views4.png trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views5.png trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views6.png trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views7.png trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views8.png trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views9.png trunk/jbpm/docs/build/reference/en/html/index.html trunk/jbpm/docs/build/reference/en/html/jboss_jbpm_runtime_installation.html trunk/jbpm/docs/build/reference/en/html/script/ trunk/jbpm/docs/build/reference/en/html/script/toggle.js trunk/jbpm/docs/build/reference/en/html/the_views.html trunk/jbpm/docs/build/reference/en/html_single/ trunk/jbpm/docs/build/reference/en/html_single/css/ trunk/jbpm/docs/build/reference/en/html_single/css/html.css trunk/jbpm/docs/build/reference/en/html_single/css/images/ trunk/jbpm/docs/build/reference/en/html_single/css/images/bg_table.gif trunk/jbpm/docs/build/reference/en/html_single/css/images/ico_important.gif trunk/jbpm/docs/build/reference/en/html_single/css/images/ico_note.gif trunk/jbpm/docs/build/reference/en/html_single/images/ trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/ trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/defaltImage.png trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_1.png trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_2.png trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_3.png trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_4.png trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_5.png trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_6.png trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_7.png trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_8.png trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_9.png trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/ trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/defaltImage.png trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc.png trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_1.png trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_1a.png trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_1b.png trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_2.png trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_2a.png trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_2b.png trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_3.png trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_4.png trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_5.png trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/ trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/defaltImage.png trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_1.png trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_10.png trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_2.png trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_3.png trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_4.png trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_5.png trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_6.png trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_7.png trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_8.png trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/ trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/default.png trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour1.png trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour10.png trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour11.png trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour12.png trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour13.png trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour14.png trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour15.png trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour2.png trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour2_b.png trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour3.png trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour4.png trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour5.png trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour6.png trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour7.png trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour8.png trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour9.png trunk/jbpm/docs/build/reference/en/html_single/images/runtime_installation/ trunk/jbpm/docs/build/reference/en/html_single/images/runtime_installation/runtime_installation1.png trunk/jbpm/docs/build/reference/en/html_single/images/the_views/ trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views.png trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views1.png trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views10.png trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views2.png trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views3.png trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views4.png trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views5.png trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views6.png trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views7.png trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views8.png trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views9.png trunk/jbpm/docs/build/reference/en/html_single/index.html trunk/jbpm/docs/build/reference/en/html_single/script/ trunk/jbpm/docs/build/reference/en/html_single/script/toggle.js trunk/jbpm/docs/build/reference/en/pdf/ trunk/jbpm/docs/build/reference/en/pdf/jBPM_Tools_Ref.pdf trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_3.png trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_4.png trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_5.png trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_6.png trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_7.png trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_8.png trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_9.png Modified: trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_2.png 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 trunk/jbpm/docs/reference/en/modules/jboss_jbpm_runtime_installation.xml Log: http://jira.jboss.com/jira/browse/JBDS-233 - adding screenshots Added: trunk/jbpm/docs/build/reference/en/html/GuidedTourJBossjBPMGPD.html =================================================================== --- trunk/jbpm/docs/build/reference/en/html/GuidedTourJBossjBPMGPD.html (rev 0) +++ trunk/jbpm/docs/build/reference/en/html/GuidedTourJBossjBPMGPD.html 2007-12-28 11:34:08 UTC (rev 5465) @@ -0,0 +1,91 @@ +<html><head> + <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> + <title>Chapter 3. A Guided Tour of JBoss jBPM GPD</title><link rel="stylesheet" href="css/html.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"><meta name="keywords" content="jBPM, JBoss, Process, Definition"><link rel="start" href="index.html" title="jBPM Tools Reference Guide"><link rel="up" href="index.html" title="jBPM Tools Reference Guide"><link rel="prev" href="jboss_jbpm_runtime_installation.html" title="Chapter 2. JBoss jBPM Runtime Installation"><link rel="next" href="the_views.html" title="Chapter 4. The views"><script xmlns="http://www.w3.org/TR/xhtml1/transitional" type="text/javascript" src="script/toggle.js"></script></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 3. A Guided Tour of JBoss jBPM GPD</th></tr><tr><td width="20%" a! lign="left"><a accesskey="p" href="jboss_jbpm_runtime_installation.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="the_views.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="GuidedTourJBossjBPMGPD"></a>Chapter 3. A Guided Tour of JBoss jBPM GPD</h2></div></div></div><p>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.</p><p>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 advanced artifacts that + we will ignore for this section. In the future we will elaborate this wizard and offer the + possibility to create an empty jBPM project as well as projects based on templates taken + from the jBPM tutorial.</p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="CreatingjBPMProject"></a>3.1. Creating a jBPM Project</h2></div></div></div><p>This section will show you how to use the Creation wizard for creating a new jBPM + project with already included source folders.</p><p>At first you should select <span class="emphasis"><em> + <span class="property">File >New Project...</span> + </em></span> and then <span class="emphasis"><em> + <span class="property">JBoss jBPM > Process Project</span> + </em></span> in the New Project dialog:</p><div class="figure"><a name="d0e243"></a><div class="figure-contents"><div class="mediaobject"><img src="images/guided_tour_jboss_jbpmgpd/guided_tour1.png" alt="New Project Dialog"></div></div><p class="title"><b>Figure 3.1. New Project Dialog</b></p></div><br class="figure-break"><p> Clicking <span class="emphasis"><em> + <span class="property">Next</span> + </em></span> brings us to the wizard page where it's necessary to specify the + name and location for the project. We choose, for example, <span class="emphasis"><em> + <span class="property">HellojBPM</span> + </em></span> as the name and accept the default location. </p><div class="figure"><a name="d0e263"></a><div class="figure-contents"><div class="mediaobject"><img src="images/guided_tour_jboss_jbpmgpd/guided_tour2.png" alt="Process Name and Location"></div></div><p class="title"><b>Figure 3.2. Process Name and Location</b></p></div><br class="figure-break"><p>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 <span class="emphasis"><em> + <span class="property">Use default location</span> + </em></span> and click <span class="emphasis"><em> + <span class="property">Browse...</span></em></span> button to set needed location or simply type it.</p><p>On the next screen you'll be prompted to select the core jBPM location that we have defined in the previous chapter.</p><div class="figure"><a name="d0e284"></a><div class="figure-contents"><div class="mediaobject"><img src="images/guided_tour_jboss_jbpmgpd/guided_tour2_b.png" alt="Process Name and Location"></div></div><p class="title"><b>Figure 3.3. Process Name and Location</b></p></div><br class="figure-break"><p>Clicking on <span class="emphasis"><em> + <span class="property">Finish</span> + </em></span> results in the project being generated. The wizard creates four source + folders: one for the processes (<span class="emphasis"><em> + <span class="property">src/main/jpdl</span> + </em></span>), one for the java sources (<span class="emphasis"><em> + <span class="property">src/main/java</span> + </em></span>), one for the unit tests (<span class="emphasis"><em> + <span class="property">src/test/java</span> + </em></span>) and one for the resources such as the jbpm.properties and the + hibernate.properties files (<span class="emphasis"><em> + <span class="property">src/main/config</span> + </em></span>). In addition a classpath container with all the core jBPM libraries is + added to the project</p><div class="figure"><a name="d0e322"></a><div class="figure-contents"><div class="mediaobject"><img src="images/guided_tour_jboss_jbpmgpd/guided_tour3.png" alt="Layout of the Process Project"></div></div><p class="title"><b>Figure 3.4. Layout of the Process Project</b></p></div><br class="figure-break"><p>Looking inside the different source folders will reveal a number of 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 definition.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="creating_an_empty_process_definition"></a>3.2. Creating an Empty Process Definition</h2></div></div></div><p>Now when the project is set up, we can use a Creation wizard to create an empty + process definition. Bring up the <span class="emphasis"><em> + <span class="property">New</span> + </em></span> wizard by clicking the <span class="emphasis"><em> + <span class="property">File > New > Other...</span> + </em></span> menu item. The wizard opens on the <span class="emphasis"><em> + <span class="property">Select Wizard</span> + </em></span> page.</p><div class="figure"><a name="d0e354"></a><div class="figure-contents"><div class="mediaobject"><img src="images/guided_tour_jboss_jbpmgpd/guided_tour4.png" alt="The Select Wizard Page"></div></div><p class="title"><b>Figure 3.5. The Select Wizard Page</b></p></div><br class="figure-break"><p>Selecting the <span class="emphasis"><em> + <span class="property">JBoss jBPM</span> + </em></span> category, then the <span class="emphasis"><em> + <span class="property">Process Definition</span> + </em></span> item and clicking on the <span class="emphasis"><em> + <span class="property">Next</span> + </em></span> button brings us to the <span class="emphasis"><em> + <span class="property">Create Process Definition</span> + </em></span> page.</p><div class="figure"><a name="d0e386"></a><div class="figure-contents"><div class="mediaobject"><img src="images/guided_tour_jboss_jbpmgpd/guided_tour5.png" alt="The Create New Process Definion Page"></div></div><p class="title"><b>Figure 3.6. The Create New Process Definion Page</b></p></div><br class="figure-break"><p>We choose <span class="emphasis"><em> + <span class="property">hello</span> + </em></span> as the name of the process archive file. Click on the <span class="emphasis"><em> + <span class="property">Finish</span> + </em></span> button to end the wizard and open the process definition editor.</p><div class="figure"><a name="d0e406"></a><div class="figure-contents"><div class="mediaobject"><img src="images/guided_tour_jboss_jbpmgpd/guided_tour6.png" alt="The Process Definition Editor"></div></div><p class="title"><b>Figure 3.7. The Process Definition Editor</b></p></div><br class="figure-break"><p>You can see in the Package Explorer that creating a process definition involves + creating a folder with the name of the process definition and populating this folder + with two .xml files : <span class="emphasis"><em> + <span class="property">gpd.xml</span> + </em></span> and <span class="emphasis"><em> + <span class="property">processdefinition.xml</span> + </em></span>.</p><p>The <span class="emphasis"><em> + <span class="property">gpd.xml</span> + </em></span> contains the graphical information used by the process + definition editor. The <span class="emphasis"><em> + <span class="property">processdefinition.xml</span> + </em></span> file contains the actual process definition info without the graphical + rendering info. At present, the GPD assumes that these two files are siblings. More + sophisticated configuration will be supported later.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="minimal_process_definition"></a>3.2.1. A Minimal Process Definition</h3></div></div></div><p>Now we are ready to create a very simple process definition consisting of a begin + state, an intermediate state and an end state.</p><p>To make the configuration of actions much easier it's better to use the + jPDL perspective. It provides the tabbed Properties Editor which allows to configure + all the relevant properties of the current selected item. </p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="adding_the_nodes"></a>3.2.1.1. Adding the Nodes</h4></div></div></div><p>At first select respectively <span class="emphasis"><em> + <span class="property">Start</span> + </em></span>, <span class="emphasis"><em> + <span class="property">State</span> + </em></span> and <span class="emphasis"><em> + <span class="property">End</span> + </em></span> on the tools palette and click on the canvas to add these nodes to + the process definition. The result should look similar to this:</p><div class="figure"><a name="d0e472"></a><div class="figure-contents"><div class="mediaobject"><img src="images/guided_tour_jboss_jbpmgpd/guided_tour7.png" alt="A Simple Process With Three Nodes"></div></div><p class="title"><b>Figure 3.8. A Simple Process With Three Nodes</b></p></div><br class="figure-break"></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="adding_transitions"></a>3.2.1.2. Adding Transitions</h4></div></div></div><p>Then, we will connect the nodes with transitions. To do that select the <span class="emphasis"><em> + <span class="property">Transition</span> + </em></span> tool in the tools palette and click on the <span class="emphasis"><em> + <span class="property">Start</span> + </em></span> node, then move to the <span class="emphasis"><em> + <span class="property">State</span> + </em></span> node and click again to see the transition being drawn. Perform the + same steps to create a transition from the <span class="emphasis"><em> + <span class="property">State</span> + </em></span> node to the <span class="emphasis"><em> + <span class="property">End</span> + </em></span> node. The result will look like:</p><div class="figure"><a name="d0e514"></a><div class="figure-contents"><div class="mediaobject"><img src="images/guided_tour_jboss_jbpmgpd/guided_tour8.png" alt="A Simple Process With Transitions"></div></div><p class="title"><b>Figure 3.9. A Simple Process With Transitions</b></p></div><br class="figure-break"></div></div><p>Now, when you've got background knowledge of simple project creation, let's move to more advanced tools.</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="jboss_jbpm_runtime_installation.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="the_views.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 2. JBoss jBPM Runtime Installation </td><td width="20%" align="center"><a accesskey="! h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 4. The views</td></tr></table></div></body></html> \ No newline at end of file Added: trunk/jbpm/docs/build/reference/en/html/Quick_Howto_Guide.html =================================================================== --- trunk/jbpm/docs/build/reference/en/html/Quick_Howto_Guide.html (rev 0) +++ trunk/jbpm/docs/build/reference/en/html/Quick_Howto_Guide.html 2007-12-28 11:34:08 UTC (rev 5465) @@ -0,0 +1,35 @@ +<html><head> + <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> + <title>Chapter 7. Quick Howto Guide</title><link rel="stylesheet" href="css/html.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"><meta name="keywords" content="jBPM, , , , "><link rel="start" href="index.html" title="jBPM Tools Reference Guide"><link rel="up" href="index.html" title="jBPM Tools Reference Guide"><link rel="prev" href="The_JBoss_jBPM_Int_Mech.html" title="Chapter 6. Actions : The JBoss jBPM Integration Mechanism"><script xmlns="http://www.w3.org/TR/xhtml1/transitional" type="text/javascript" src="script/toggle.js"></script></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 7. Quick Howto Guide</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="The_JBoss_jBPM_Int_Mech.html">Prev</a> </td><th width="60%" align="center">&nbs! p;</th><td width="20%" align="right"> </td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Quick_Howto_Guide"></a>Chapter 7. Quick Howto Guide</h2></div></div></div><p>This chapter contains additional information related to the <span class="property">JBoss + jBPM</span>.</p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="change_core_jbpm_inst"></a>7.1. Change the Default Core jBPM Installation</h2></div></div></div><p> You can change the default <span class="property">jBPM</span> installation by means of the + Eclipse preference mechanism. Open the Preferences dialog by selecting <span class="emphasis"><em> + <span class="property">Window > Preferences</span> + </em></span> and select the <span class="emphasis"><em> + <span class="property">JBoss jBPM > Runtime Location</span> + </em></span> category. Using this page you can add multiple <span class="property">jBPM</span> + 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 <span class="property">jBPM</span> + installation that's being referenced by a project however will cause the + classpath to contain errors. </p><div class="figure"><a name="d0e1200"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Quick_Howto_Guide/quick_howto_guide_1.png" alt="The jBPM Preferences Page"></div></div><p class="title"><b>Figure 7.1. The jBPM Preferences Page</b></p></div><br class="figure-break"></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e1206"></a>7.2. Configuring Task Nodes</h2></div></div></div><p>Here, we'll examine how you can configure the Task nodes in jBPM jPDL GPD.</p><p> 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 + Properties view for selected Task node includes several tabs. </p><div class="figure"><a name="d0e1213"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Quick_Howto_Guide/quick_howto_guide_2.png" alt="The Properties View of the selected Task Node"></div></div><p class="title"><b>Figure 7.2. The Properties View of the selected Task Node</b></p></div><br class="figure-break"><p>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.</p><div class="figure"><a name="d0e1221"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Quick_Howto_Guide/quick_howto_guide_3.png" alt="Adding a Task to the Task Node"></div></div><p class="title"><b>Figure 7.3. Adding a Task to the Task Node</b></p></div><br class="figure-break"><p>Every added Task has its own configuration possibilities. You can access them through + the Properties view as well.</p><div class="figure"><a name="d0e1229"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Quick_Howto_Guide/quick_howto_guide_4.png" alt="The Task properties"></div></div><p class="title"><b>Figure 7.4. The Task properties</b></p></div><br class="figure-break"><p>On the <span class="property">General</span> page is a place where you can specify the name of + a Task and its description. For instance, let it be <span class="emphasis"><em> + <span class="property">approve oder</span> + </em></span> with appropriate description that you can see in the figure below.</p><div class="figure"><a name="d0e1246"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Quick_Howto_Guide/quick_howto_guide_5.png" alt="The Task General Page"></div></div><p class="title"><b>Figure 7.5. The Task General Page</b></p></div><br class="figure-break"><p>Now, look at <span class="property">Details page</span>. 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 blocking attribute indicates that the process will not be + able to continue if this task is still unaccomplished. The <span class="emphasis"><em> + <span class="property">Generate Form...</span> + </em></span> button is for creating a simple task form that can be rendered by the jBPM + console.</p><div class="figure"><a name="d0e1263"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Quick_Howto_Guide/quick_howto_guide_6.png" alt="The Task Details Page"></div></div><p class="title"><b>Figure 7.6. The Task Details Page</b></p></div><br class="figure-break"><p>For our example, we specify the due date as 2 business days, choose the high priority + and also check the signalling and notifying 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 + <span class="property">Assignment</span> page.</p><div class="figure"><a name="d0e1274"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Quick_Howto_Guide/quick_howto_guide_7.png" alt="The Task Assignment Page"></div></div><p class="title"><b>Figure 7.7. The Task Assignment Page</b></p></div><br class="figure-break"><p>On the Reminder page you can specify whether the assignee will be reminded of the task + that awaits him.</p><div class="figure"><a name="d0e1282"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Quick_Howto_Guide/quick_howto_guide_8.png" alt="The Task Reminder Page"></div></div><p class="title"><b>Figure 7.8. The Task Reminder Page</b></p></div><br class="figure-break"><p>In our case, the assignee will be reminded by email after two business hours and continue + to get reminding every business hour after that.</p><p>In the next figure you can see our configuring generated into XML.</p><div class="figure"><a name="d0e1292"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Quick_Howto_Guide/quick_howto_guide_9.png" alt="The Task Reminder Page"></div></div><p class="title"><b>Figure 7.9. The Task Reminder Page</b></p></div><br class="figure-break"></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="The_JBoss_jBPM_Int_Mech.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> </td></tr><tr><td width="40%" align="left" valign="top">Chapter 6. Actions : The JBoss jBPM Integration Mechanism </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> </td></tr></table><! /div></body></html> \ No newline at end of file Added: trunk/jbpm/docs/build/reference/en/html/TargetAudience.html =================================================================== --- trunk/jbpm/docs/build/reference/en/html/TargetAudience.html (rev 0) +++ trunk/jbpm/docs/build/reference/en/html/TargetAudience.html 2007-12-28 11:34:08 UTC (rev 5465) @@ -0,0 +1,29 @@ +<html><head> + <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> + <title>Chapter 1. Introduction</title><link rel="stylesheet" href="css/html.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"><meta name="keywords" content="jBPM, Target, developers, Audience"><link rel="start" href="index.html" title="jBPM Tools Reference Guide"><link rel="up" href="index.html" title="jBPM Tools Reference Guide"><link rel="prev" href="index.html" title="jBPM Tools Reference Guide"><link rel="next" href="jboss_jbpm_runtime_installation.html" title="Chapter 2. JBoss jBPM Runtime Installation"><script xmlns="http://www.w3.org/TR/xhtml1/transitional" type="text/javascript" src="script/toggle.js"></script></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 1. Introduction</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="index.htm! l">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="jboss_jbpm_runtime_installation.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Introduction"></a>Chapter 1. Introduction</h2></div></div></div><p>All developers and process analysts who are beginning to use JBoss jBPM should read this + Getting Started guide. It will give them a jumpstart showing how to create a process definition.</p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="Preface"></a>1.1. Preface</h2></div></div></div><p>This document introduces the use of the JBoss jBPM Graphical Process Designer (GPD) to + create workflow processes. It will help first time users with the following tasks :</p><div class="itemizedlist"><ul type="disc"><li><p>Install the JBoss jBPM GPD Eclipse plugin available from the JBoss jBPM download + area</p></li><li><p>Set up a Java project in Eclipse and prepare it to do test driven process + development</p></li><li><p>Using the creation wizard to create an empty process definition</p></li><li><p>Use the designer palette to draw the first processdefinition</p></li><li><p>Show how the xml processdefinition can be inspected as an xml file</p></li><li><p>Set up a Java project in Eclipse and prepare it to do test driven process + development</p></li><li><p>Write an example process test case</p></li></ul></div><p>If you have questions, please feel free to contact Koen Aers (koen.aers(a)jboss.com) or Tom Baeyens (tom.baeyens(a)jboss.com) for more + information.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="feature_list"></a>1.2. Feature list</h2></div></div></div><p> JBoss jBPM is a workflow that enables creating and automatization business processes. Look + at the list of features below to understand its main functionality.</p><div class="table"><a name="d0e69"></a><p class="title"><b>Table 1.1. Key Functionality for JBoss jBPM</b></p><div class="table-contents"><table summary="Key Functionality for JBoss jBPM" border="1"><colgroup><col><col></colgroup><thead><tr><th>Feature</th><th>Benefit</th></tr></thead><tbody><tr><td> + <a class="link" href="GuidedTourJBossjBPMGPD.html#minimal_process_definition" title="3.2.1. A Minimal Process Definition">jBDL support</a> + </td><td>Enables managing workflow processes as well as human tasks and interactions between + them. jBDL combines the best both Java and declarative process techniques.</td></tr><tr><td> + <a class="link" href="GuidedTourJBossjBPMGPD.html" title="Chapter 3. A Guided Tour of JBoss jBPM GPD">Support of Graphical Process Designer (GPD)</a> + </td><td>Is used for simplifying declarative process development and visualizations of all + actions.</td></tr><tr><td> + <a class="link" href="GuidedTourJBossjBPMGPD.html#CreatingjBPMProject" title="3.1. Creating a jBPM Project">Project Creation wizard</a> + </td><td>Allows to create a new jBPM template project that already includes all advanced + artifacts and core jBPM libraries.</td></tr><tr><td> + <a class="link" href="GuidedTourJBossjBPMGPD.html#minimal_process_definition" title="3.2.1. A Minimal Process Definition">Rich palette of pre-build process nodes</a> + </td><td>Provides process-building functionality and gives opportunity even non-programmers to + develop processes.</td></tr><tr><td> + <a class="link" href="the_views.html#source_mode" title="4.4.2. The Source Mode">Support of XML code view</a> + </td><td>Shows the corresponding XML that's generated automatically in the Source view of the process + definition editor when developing the process.</td></tr><tr><td> + <a class="link" href="the_views.html#the_properties_view" title="4.3. The Properties View">Properties view</a> + </td><td>Facilitates configuring and editing of all nodes properties.</td></tr><tr><td>Interaction with all of the J2EE based integration technologies including Web Services, + Java Messaging, J2EE Connectors, JBDC, EJBs.</td><td>Enables implementation, provides better functionality and flexibility.</td></tr><tr><td>Integration with jBoss Seam</td><td>Allows to write applications with complex workflows and provides easier interactions + between them.</td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="index.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="jboss_jbpm_runtime_installation.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">jBPM Tools Reference Guide </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 2. JBoss jBPM Runtime Installation</td></tr></table></div></body></html> \ No newline at end of file Added: trunk/jbpm/docs/build/reference/en/html/Test_Drive_Proc_Development.html =================================================================== --- trunk/jbpm/docs/build/reference/en/html/Test_Drive_Proc_Development.html (rev 0) +++ trunk/jbpm/docs/build/reference/en/html/Test_Drive_Proc_Development.html 2007-12-28 11:34:08 UTC (rev 5465) @@ -0,0 +1,48 @@ +<html><head> + <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> + <title>Chapter 5. Test Driven Process Development</title><link rel="stylesheet" href="css/html.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"><meta name="keywords" content="jBPM, , , , "><link rel="start" href="index.html" title="jBPM Tools Reference Guide"><link rel="up" href="index.html" title="jBPM Tools Reference Guide"><link rel="prev" href="the_views.html" title="Chapter 4. The views"><link rel="next" href="The_JBoss_jBPM_Int_Mech.html" title="Chapter 6. Actions : The JBoss jBPM Integration Mechanism"><script xmlns="http://www.w3.org/TR/xhtml1/transitional" type="text/javascript" src="script/toggle.js"></script></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 5. Test Driven Process Development</th></tr><tr><td width="20%" align="left"><! a accesskey="p" href="the_views.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="The_JBoss_jBPM_Int_Mech.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Test_Drive_Proc_Development"></a>Chapter 5. Test Driven Process Development</h2></div></div></div><p> One of the most important advantages of JBoss jBPM's lightweight approach to BPM + and workflow management is that developers can easily leverage their usual programming + skills and techniques. One of these well-known techniques is Unit Testing and Test Driven + Development. </p><p>In this chapter we will show how developers, making use of the JBoss jBPM GPD, can use a + technique we have baptized <span class="property">Test Driven Process Development</span> to create + process definitions and test their correctness. </p><p> When creating the <span class="emphasis"><em> + <span class="property">HellojBPM</span> + </em></span> project the Project Creation wizard has already put in place all the library + requirements we need to start writing the jBPM unit tests. They are contained in the jBPM + Library container and the most important of them is the <span class="emphasis"><em> + <span class="property">.jar</span> + </em></span> file containing the core jBPM classes. While working on the project you could + find them all in the Package Explorer.</p><div class="figure"><a name="d0e777"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Test_Drive_Proc/test_driv_proc.png" alt="The jBPM Libraries"></div></div><p class="title"><b>Figure 5.1. The jBPM Libraries</b></p></div><br class="figure-break"><p>It must be noted that it is possible to change the location of the core jBPM installation + by changing the preference settings. More on this <a class="link" href="Quick_Howto_Guide.html#change_core_jbpm_inst" title="7.1. Change the Default Core jBPM Installation">see + later</a> in this book.</p><p> With that extra knowledge on the project settings, you can create your first test. To do + this, we create the <span class="emphasis"><em> + <span class="property">com.jbay</span> + </em></span> package in the <span class="emphasis"><em> + <span class="property">test/java</span> + </em></span> source folder. Then we bring up the context menu on this package and select <span class="emphasis"><em> + <span class="property">New > Other...</span> + </em></span></p><div class="figure"><a name="d0e807"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Test_Drive_Proc/test_driv_proc_1a.png" alt="Call the JUnit Test Case Creation wizard"></div></div><p class="title"><b>Figure 5.2. Call the JUnit Test Case Creation wizard</b></p></div><br class="figure-break"><p> And then <span class="emphasis"><em> + <span class="property">Java > JUnit > JUnit Test Case</span> + </em></span> to call the specialized JUnite Test case creation wizard.</p><div class="figure"><a name="d0e821"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Test_Drive_Proc/test_driv_proc_1b.png" alt="Call the JUnit Test Case Creation wizard"></div></div><p class="title"><b>Figure 5.3. Call the JUnit Test Case Creation wizard</b></p></div><br class="figure-break"><p>The wizard looks as follows:</p><div class="figure"><a name="d0e829"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Test_Drive_Proc/test_driv_proc_2a.png" alt="Create Test Dialog"></div></div><p class="title"><b>Figure 5.4. Create Test Dialog</b></p></div><br class="figure-break"><p>By default JUnite 3 version of testing framework is selected. Of course, you can choose + new advanced JUnit 4 version. In this case you'll be prompted to add new JUnit + Library to your build path. To add it automatically just click on the appropriate link.</p><div class="figure"><a name="d0e837"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Test_Drive_Proc/test_driv_proc_2b.png" alt="A First Test Scenario"></div></div><p class="title"><b>Figure 5.5. A First Test Scenario</b></p></div><br class="figure-break"><p>Then, we call the test class <span class="emphasis"><em> + <span class="property">HelloTest</span> + </em></span> and press <span class="emphasis"><em> + <span class="property">Finish</span> + </em></span> button to complete.</p><p> Next, we should write a simple test scenario as shown on the next figure. Let's + study the code of this test case. </p><div class="figure"><a name="hello_test"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Test_Drive_Proc/test_driv_proc_3.png" alt="A First Test Scenario"></div></div><p class="title"><b>Figure 5.6. A First Test Scenario</b></p></div><br class="figure-break"><p>In the first line of the method, a jBPM process archive object is created. We use a + constructor accepting the filename of the archive. In our case it is the <span class="emphasis"><em> + <span class="property">hello</span> + </em></span> file we created earlier and which lives in the <span class="emphasis"><em> + <span class="property">src/main/jpdl</span> + </em></span> folder of our project. After asserting that this object is really created, we + extract a process definition object from it. This 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 <span class="emphasis"><em> + <span class="property">auction</span> + </em></span> state. Finally another signal will end the process. </p><p> After writing this test we can check whether it works as expected by running it .</p><div class="figure"><a name="d0e887"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Test_Drive_Proc/test_driv_proc_4.png" alt="Running the Process Test"></div></div><p class="title"><b>Figure 5.7. Running the Process Test</b></p></div><br class="figure-break"><p>All went well as we have a green light:</p><div class="figure"><a name="d0e895"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Test_Drive_Proc/test_driv_proc_5.png" alt="Successful Test Run"></div></div><p class="title"><b>Figure 5.8. Successful Test Run</b></p></div><br class="figure-break"><p> 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 <a class="ulink" href="http://docs.jboss.com/jbpm/v3/userguide/" target="_top">JBoss jBPM User Guide</a> and to + study the API reference. Moreover some more examples will be given later in this book.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="the_views.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="The_JBoss_jBPM_Int_Mech.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 4. The views </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 6. Actions : The JBoss jBPM Integration Mechanism</td></tr></table></div></body></html> \ No newline at end of file Added: trunk/jbpm/docs/build/reference/en/html/The_JBoss_jBPM_Int_Mech.html =================================================================== --- trunk/jbpm/docs/build/reference/en/html/The_JBoss_jBPM_Int_Mech.html (rev 0) +++ trunk/jbpm/docs/build/reference/en/html/The_JBoss_jBPM_Int_Mech.html 2007-12-28 11:34:08 UTC (rev 5465) @@ -0,0 +1,79 @@ +<html><head> + <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> + <title>Chapter 6. Actions : The JBoss jBPM Integration Mechanism</title><link rel="stylesheet" href="css/html.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"><meta name="keywords" content="jBPM, , , , "><link rel="start" href="index.html" title="jBPM Tools Reference Guide"><link rel="up" href="index.html" title="jBPM Tools Reference Guide"><link rel="prev" href="Test_Drive_Proc_Development.html" title="Chapter 5. Test Driven Process Development"><link rel="next" href="Quick_Howto_Guide.html" title="Chapter 7. Quick Howto Guide"><script xmlns="http://www.w3.org/TR/xhtml1/transitional" type="text/javascript" src="script/toggle.js"></script></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 6. Actions : The JBoss jBPM Integration Mechanism</th></tr! ><tr><td width="20%" align="left"><a accesskey="p" href="Test_Drive_Proc_Development.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="Quick_Howto_Guide.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="The_JBoss_jBPM_Int_Mech"></a>Chapter 6. Actions : The JBoss jBPM Integration Mechanism</h2></div></div></div><p> In this chapter we will show how to do software integration with <span class="property">JBoss + jBPM</span>. The standard mechanism to implement this is to wrap the functionality you + want to integrate in a class that implements the <span class="emphasis"><em> + <span class="property">ActionHandler</span> + </em></span> interface. In order to demonstrate it let's specify Hello World action for our + process.</p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e931"></a>6.1. Creating a Hello World Action</h2></div></div></div><p>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 <span class="emphasis"><em> + <span class="property">ActionHandler</span> + </em></span> 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. </p><p> To make things a little bit more concrete, let's create a new class called <span class="emphasis"><em> + <span class="property">HelloActionHandler</span> + </em></span>. For that firstly we'll create a new package <span class="emphasis"><em> + <span class="property">com.jbay.action</span> + </em></span> in the <span class="emphasis"><em> + <span class="property">src/java/main</span> + </em></span> folder of our project. Then, we should call New Class Creation wizard as + usual by right-clicking and navigating <span class="emphasis"><em> + <span class="property">New > Class</span> + </em></span>. </p><div class="figure"><a name="d0e968"></a><div class="figure-contents"><div class="mediaobject"><img src="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_1.png" alt="Creating HelloActionHendler Class"></div></div><p class="title"><b>Figure 6.1. Creating HelloActionHendler Class</b></p></div><br class="figure-break"><p>Notice that two first gaps have been filled automatically. Here, instead of <span class="emphasis"><em> + <span class="property">Package</span> + </em></span> option <span class="emphasis"><em> + <span class="property">Enclose type</span> + </em></span> option can be selected where a type in which to enclose a new class should + be specified.</p><p>In our case, we leave everything as it is, just type <span class="emphasis"><em> + <span class="property">HelloActionHandler</span> + </em></span> as a name of new class and add <span class="emphasis"><em> + <span class="property">org.jbpm.graph.ActionHendler</span> + </em></span> interface as it's shown in the picture above.</p><p>Thus, our <span class="emphasis"><em> + <span class="property">HelloActionHandler</span> + </em></span> implements the <span class="emphasis"><em> + <span class="property">ActionHandler</span> + </em></span> interface including the <span class="emphasis"><em> + <span class="property">execute</span> + </em></span> method as shown in the next figure. Here, we add a variable named <span class="emphasis"><em> + <span class="property">greeting</span> + </em></span> to the collection of process variables and put a message in it : + <span class="emphasis"><em>"Hello from ActionHandler"</em></span>. </p><div class="figure"><a name="d0e1031"></a><div class="figure-contents"><div class="mediaobject"><img src="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_2.png" alt="A Simple Hello Action"></div></div><p class="title"><b>Figure 6.2. A Simple Hello Action</b></p></div><br class="figure-break"><p>Now, as we have <span class="emphasis"><em> + <span class="property">HelloActionHandler</span> + </em></span> class defined, let's explore how we can handle it.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e1045"></a>6.2. Integrating the Hello World Action</h2></div></div></div><p>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.</p><p> As good Testcity citizens we will first create a Unit Test that proves the behaviour + we want to achieve by adding the <span class="emphasis"><em> + <span class="property">ActionHandler</span> + </em></span> to the process. So we implement another test.</p><p>At first, let's return to the + code we already saw <a class="link" href="Test_Drive_Proc_Development.html#hello_test" title="Figure 5.6. A First Test Scenario">in the previous chapter</a> and add new test method <span class="emphasis"><em> + <span class="property">testActionHendler</span></em></span> to it. </p><div class="figure"><a name="d0e1068"></a><div class="figure-contents"><div class="mediaobject"><img src="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_3.png" alt="Create the Hello Action Test"></div></div><p class="title"><b>Figure 6.3. Create the Hello Action Test</b></p></div><br class="figure-break"><p>We assert + that no variable called <span class="emphasis"><em> + <span class="property">greeting</span> + </em></span> 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 <span class="emphasis"><em> + <span class="property">greeting</span> + </em></span> variable should exist and contain the string "Hello from + ActionHandler". That's what we assert in the last lines of the test + method.</p><p> 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. </p><div class="figure"><a name="d0e1090"></a><div class="figure-contents"><div class="mediaobject"><img src="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_4.png" alt="Test Results Before Integration"></div></div><p class="title"><b>Figure 6.4. Test Results Before Integration</b></p></div><br class="figure-break"><p> 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.</p><div class="figure"><a name="d0e1098"></a><div class="figure-contents"><div class="mediaobject"><img src="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_5.png" alt="Adding an Action to a Transition"></div></div><p class="title"><b>Figure 6.5. Adding an Action to a Transition</b></p></div><br class="figure-break"><p>After adding the action a tabbed view with three pages will appear.</p><div class="figure"><a name="d0e1106"></a><div class="figure-contents"><div class="mediaobject"><img src="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_6.png" alt="Configuration Dialog for an Action"></div></div><p class="title"><b>Figure 6.6. Configuration Dialog for an Action</b></p></div><br class="figure-break"><p>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. </p><div class="figure"><a name="d0e1114"></a><div class="figure-contents"><div class="mediaobject"><img src="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_7.png" alt="The Details page of an Action Configuration Dialog"></div></div><p class="title"><b>Figure 6.7. The Details page of an Action Configuration Dialog</b></p></div><br class="figure-break"><p>Clicking on the <span class="emphasis"><em> + <span class="property">Search...</span> + </em></span> button brings us to a Choose Class dialog.</p><div class="figure"><a name="d0e1128"></a><div class="figure-contents"><div class="mediaobject"><img src="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_8.png" alt="The Choose Action Handler Dialog"></div></div><p class="title"><b>Figure 6.8. The Choose Action Handler Dialog</b></p></div><br class="figure-break"><p> We choose our previously created 'HelloActionHandler' class and + push the <span class="property">OK</span> button. After the selection of the action handler for + the action, we can run the test and observe it gives us a green light.</p><div class="figure"><a name="d0e1139"></a><div class="figure-contents"><div class="mediaobject"><img src="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_10.png" alt="Test Results"></div></div><p class="title"><b>Figure 6.9. Test Results</b></p></div><br class="figure-break"><p>Tere we are. The above objective has been achieved.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e1147"></a>6.3.  Integration Points</h2></div></div></div><p> The different integration points in a process definition are thoroughly documented in + the <a class="ulink" href="http://docs.jboss.com/jbpm/v3/userguide/" target="_top">JBoss jBPM User Guide</a>. 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. </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Test_Drive_Proc_Development.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="Quick_Howto_Guide.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 5. Test Driven Process Development </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 7. Quick Howto Guide</td></tr></table></div></body></html> \ No newline at end of file Added: trunk/jbpm/docs/build/reference/en/html/css/html.css =================================================================== --- trunk/jbpm/docs/build/reference/en/html/css/html.css (rev 0) +++ trunk/jbpm/docs/build/reference/en/html/css/html.css 2007-12-28 11:34:08 UTC (rev 5465) @@ -0,0 +1,346 @@ +* { + LINE-HEIGHT: 20px; FONT-FAMILY: verdana, helvetica, sans-serif +} +DIV.navheader TABLE, DIV.navheader TABLE td, DIV.navfooter TABLE, DIV.navfooter TABLE td{ + BORDER-RIGHT: 0px; BORDER-TOP: 0px; MARGIN: 0px; BORDER-LEFT: 0px; BORDER-BOTTOM: 0px; FONT-SIZE: 11px; padding : 0px; +} +A { + COLOR: #2a7bd4; FONT-FAMILY: verdana, helvetica, sans-serif +} +A:hover { + COLOR: #003399; FONT-FAMILY: verdana, helvetica, sans-serif +} +A:visited { + COLOR: #888888; FONT-FAMILY: verdana, helvetica, sans-serif +} +P { + FONT-SIZE: 12px; COLOR: #000000; margin : 5px 0px 5px 0px; +} +OL { + FONT-SIZE: 12px; COLOR: #000000; margin-top : 5px; margin-bottom : 5px; +} +UL { + FONT-SIZE: 12px; COLOR: #000000; margin-top : 5px; margin-bottom : 5px; +} +LI { + FONT-SIZE: 12px; COLOR: #000000; margin-top : 5px; margin-bottom : 5px; +} +DL { + FONT-SIZE: 12px; COLOR: #000000; margin-top : 5px; margin-bottom : 5px; +} +DT { + FONT-SIZE: 12px; COLOR: #000000; margin-top : 5px; margin-bottom : 5px; +} +DD { + FONT-SIZE: 12px; COLOR: #000000; margin-top : 5px; margin-bottom : 5px; +} +BLOCKQUOTE { + FONT-SIZE: 12px; COLOR: #000000 +} +TD { + COLOR: #000000 +} +TH { + COLOR: #000000 +} +SPAN { + COLOR: #000000 +} +SPAN.property { + COLOR: #008cca; +} +SPAN.italic { + FONT-STYLE: italic; +} + +BLOCKQUOTE { + MARGIN-RIGHT: 0px +} + +P.title { + MARGIN-BOTTOM: 5px; + MARGIN-top: 20px; +} + +div.book div.chapter .title { + text-align: left; +} + + +div.book .title { + text-align: center; +} + +.mediaobject{ + padding : 5px 10px 5px 35px; +} +H1 { + MARGIN: 0px; FONT-SIZE: 22px; COLOR: #ff6600; PADDING: 45px 0px 10px 0px; +} +H2 { + MARGIN: 0px; FONT-SIZE: 18px; COLOR: #2a7bd4; PADDING: 25px 0px 10px 0px; +} +H3 { + MARGIN: 0px; FONT-SIZE: 15px; COLOR: #000000; PADDING: 20px 0px 10px 0px; +} +H4 { + MARGIN: 0px; FONT-SIZE: 12px; COLOR: #000000; PADDING: 15px 0px 10px 0px; +} +H5 { + MARGIN: 0px; FONT-SIZE: 12px; COLOR: #000000; PADDING: 15px 0px 10px 0px; +} +H6 { + MARGIN: 0px; FONT-SIZE: 11px; COLOR: #000000; PADDING: 5px 0px 0px 0px; +} + +div.book div.section div.mediaobject{ +text-align:left; +} + + +div.book div.mediaobject{ +text-align:left; +} + +div.mediaobject, div.mediaobject img *{ +text-align:left; + +} + +DIV.note{ + BORDER: #CECECE 1px solid; PADDING: 3px 10px 10px 50px; line-height : 14px; MARGIN: 10px 0px 10px 0px; FONT-SIZE: 11px; WIDTH: 500px; BACKGROUND-COLOR: #FFFDD3; + background-image : url('Images/ico_note.gif'); background-repeat : no-repeat; background-position :top left; +} + +DIV.note *{ + line-height : 14px; +} + +.note P { + MARGIN-TOP: 0px; MARGIN-BOTTOM: 1em; PADDING-BOTTOM: 0px; PADDING-TOP: 0px +} +.important P { + MARGIN-TOP: 0px; MARGIN-BOTTOM: 1em; PADDING-BOTTOM: 0px; PADDING-TOP: 0px +} +DIV.important { + BORDER: #CECECE 1px solid; PADDING: 3px 10px 10px 50px; line-height : 14px; MARGIN: 10px 0px 10px 0px; FONT-SIZE: 11px; WIDTH: 500px; BACKGROUND-COLOR: #CFE3FF; + background-image : url('Images/ico_important.gif'); background-repeat : no-repeat; background-position :top left; +} + +DIV.important *{ + line-height : 14px; +} + +.important pre.XML { +PADDING: 1px 1px 1px 10px; + +} + + +TABLE { + BORDER: #cccccc 1px solid; FONT-SIZE: 11px; BORDER-COLLAPSE: collapse; border-spacing: 0; empty-cells: hide; margin-bottom : 10px; +} + +table *{ + line-height : 14px; +} + + +.table TH { + WHITE-SPACE: nowrap; BACKGROUND-COLOR: #EEF5FF; TEXT-ALIGN: center; BORDER-BOTTOM: #CAE1FF 2px solid; PADDING: 2px 8px 2px 8px; + background-image : url('Images/bg_table.gif'); background-repeat : repeat-x; background-position :top left; +} +TD { + PADDING: 4px 8px 4px 8px; BORDER-BOTTOM: #cccccc 1px dotted; BORDER-right: #cccccc 1px dotted; +} +P.copyright { + TEXT-ALIGN: center +} +TT { + FONT-SIZE: 90%; COLOR: #000000; FONT-FAMILY: "Courier New", Courier, monospace +} +DL { + MARGIN-BOTTOM: 6px; MARGIN-LEFT: 8px +} +DT { + MARGIN-BOTTOM: 6px; MARGIN-LEFT: 8px +} +DD { + MARGIN-BOTTOM: 6px; MARGIN-LEFT: 8px +} +PRE { + BORDER: #cccccc 1px solid; PADDING: 5px 15px 5px 25px; FONT-SIZE: 11px; BACKGROUND-COLOR: #f5f5f5; +} +HR { + BORDER-TOP-WIDTH: 0px; PADDING-RIGHT: 0px; PADDING-LEFT: 0px; BORDER-LEFT-WIDTH: 0px; BORDER-BOTTOM-WIDTH: 0px; PADDING-BOTTOM: 0px; WIDTH: 100%; COLOR: #cccccc; PADDING-TOP: 0px; HEIGHT: 1px; BACKGROUND-COLOR: #cccccc; BORDER-RIGHT-WIDTH: 0px +} +.variablelist { + PADDING-BOTTOM: 10px; MARGIN: 0px; PADDING-TOP: 10px +} +.itemizedlist { + FONT-SIZE: 12px; PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-TOP: 0px;TEXT-ALIGN: justify +} +.term { + FONT-WEIGHT: bold +} +PRE.JAVA { + LINE-HEIGHT: 0px +} +PRE.XML { + LINE-HEIGHT: 0px +} +PRE.JSP { + LINE-HEIGHT: 0px +} +PRE.XHTML { + LINE-HEIGHT: 0px +} +.java_type { + COLOR: #008cca +} +.java_keyword { + FONT-WEIGHT: bold; COLOR: rgb(0,0,0) +} +.java_javadoc_comment { + COLOR: rgb(147,147,147); FONT-STYLE: italic; BACKGROUND-COLOR: rgb(247,247,247) +} +.java_comment { + COLOR: rgb(147,147,147); BACKGROUND-COLOR: rgb(247,247,247) +} +.java_operator { + COLOR: #003399 +} +.java_plain { + COLOR: rgb(0,0,0) +} +.java_literal { + COLOR: #ff6600 +} +PRE CODE { + FONT-SIZE: 12px; COLOR: rgb(0,0,0); FONT-FAMILY: monospace; WHITE-SPACE: nowrap +} +.java_javadoc_tag { + FONT-WEIGHT: bold; COLOR: rgb(147,147,147); FONT-STYLE: italic; BACKGROUND-COLOR: rgb(247,247,247) +} +.java_separator { + COLOR: #008cca +} +.xml_plain { + COLOR: rgb(0,0,0) +} +.xml_tag_name { + COLOR: #008cca +} +.xml_comment { + COLOR: rgb(147,147,147); BACKGROUND-COLOR: rgb(247,247,247) +} +.xml_tag_symbols { + COLOR: #008cca +} +.xml_rife_tag { + COLOR: rgb(0,0,0); BACKGROUND-COLOR: rgb(228,230,160) +} +.xml_attribute_value { + COLOR: #ff6600 +} +.xml_attribute_name { + FONT-WEIGHT: bold; COLOR: rgb(0,0,0) +} +.xml_char_data { + COLOR: rgb(0,0,0) +} +.xml_rife_name { + COLOR: #008cca; BACKGROUND-COLOR: rgb(228,230,160) +} +.xml_processing_instruction { + FONT-WEIGHT: bold; COLOR: rgb(0,0,0); FONT-STYLE: italic +} +TD.java { + VERTICAL-ALIGN: top; LINE-HEIGHT: 10px +} +TD.java-ln { + VERTICAL-ALIGN: top; LINE-HEIGHT: 10px +} +TT.java { + MARGIN-BOTTOM: 0em; LINE-HEIGHT: 10px +} +TT.java-ln { + MARGIN-BOTTOM: 0em; LINE-HEIGHT: 10px +} +PRE.java { + MARGIN-BOTTOM: 0em; LINE-HEIGHT: 10px +} +PRE.java-ln { + MARGIN-BOTTOM: 0em; LINE-HEIGHT: 10px +} +TD.java-ln { + LINE-HEIGHT: 10px; TEXT-ALIGN: right +} +TT.java-ln { + COLOR: #888888; LINE-HEIGHT: 10px +} +PRE.java-ln { + COLOR: #888888; LINE-HEIGHT: 10px +} +SPAN.java0 { + FONT-SIZE: 8pt; COLOR: #ffffff; LINE-HEIGHT: 10px +} +SPAN.java1 { + FONT-SIZE: 8pt; COLOR: #808080 +} +SPAN.java2 { + FONT-SIZE: 8pt; COLOR: #3f7f5f; LINE-HEIGHT: 10px +} +SPAN.java3 { + FONT-SIZE: 8pt; COLOR: #3f7f5f; LINE-HEIGHT: 10px +} +SPAN.java4 { + FONT-WEIGHT: bold; FONT-SIZE: 8pt; COLOR: #ff6600; LINE-HEIGHT: 10px +} +SPAN.java5 { + FONT-SIZE: 8pt; COLOR: #2a00ff; LINE-HEIGHT: 10px +} +SPAN.java6 { + FONT-SIZE: 8pt; COLOR: #990000; LINE-HEIGHT: 10px +} +SPAN.java7 { + FONT-SIZE: 8pt; COLOR: #990000; LINE-HEIGHT: 10px +} +SPAN.java8 { + FONT-SIZE: 8pt; COLOR: #000000; LINE-HEIGHT: 10px +} +SPAN.java9 { + FONT-WEIGHT: bold; FONT-SIZE: 8pt; COLOR: #ff6600; LINE-HEIGHT: 10px +} +SPAN.java10 { + FONT-SIZE: 8pt; COLOR: #000000; LINE-HEIGHT: 10px +} +SPAN.java11 { + FONT-SIZE: 8pt; COLOR: #7f9fbf; LINE-HEIGHT: 10px +} +SPAN.java12 { + FONT-SIZE: 8pt; COLOR: #7f7f9f; LINE-HEIGHT: 10px +} +SPAN.java13 { + FONT-SIZE: 8pt; COLOR: #3f3fbf; LINE-HEIGHT: 10px +} +SPAN.java14 { + FONT-SIZE: 8pt; COLOR: #3f5fbf; LINE-HEIGHT: 10px +} +SPAN.java15 { + FONT-SIZE: 8pt; COLOR: #ff6100; LINE-HEIGHT: 10px +} +SPAN.java16 { + FONT-SIZE: 8pt; COLOR: #646464; LINE-HEIGHT: 10px +} + +.expand_collapse_toc { + clear:both; + float:left; + font-family:monospace; + width:20px; + color: #2A7BD4; + cursor: pointer; +} + + Added: trunk/jbpm/docs/build/reference/en/html/css/images/bg_table.gif =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/css/images/bg_table.gif ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/css/images/ico_important.gif =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/css/images/ico_important.gif ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/css/images/ico_note.gif =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/css/images/ico_note.gif ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/defaltImage.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/defaltImage.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_1.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_2.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_3.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_4.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_4.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_5.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_5.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_6.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_6.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_7.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_7.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_8.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_8.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_9.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/Quick_Howto_Guide/quick_howto_guide_9.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/defaltImage.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/defaltImage.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_1.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_1a.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_1a.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_1b.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_1b.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_2.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_2a.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_2a.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_2b.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_2b.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_3.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_4.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_4.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_5.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/Test_Drive_Proc/test_driv_proc_5.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/defaltImage.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/defaltImage.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_1.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_10.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_10.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_2.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_3.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_4.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_4.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_5.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_5.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_6.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_6.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_7.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_7.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_8.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_8.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/default.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/default.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour1.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour10.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour10.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour11.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour11.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour12.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour12.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour13.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour13.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour14.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour14.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour15.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour15.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour2.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour2_b.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour2_b.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour3.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour4.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour4.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour5.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour5.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour6.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour6.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour7.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour7.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour8.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour8.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour9.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/guided_tour_jboss_jbpmgpd/guided_tour9.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/runtime_installation/runtime_installation1.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/runtime_installation/runtime_installation1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views1.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views10.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views10.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views2.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views3.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views4.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views4.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views5.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views5.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views6.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views6.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views7.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views7.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views8.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views8.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views9.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html/images/the_views/the_views9.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html/index.html =================================================================== --- trunk/jbpm/docs/build/reference/en/html/index.html (rev 0) +++ trunk/jbpm/docs/build/reference/en/html/index.html 2007-12-28 11:34:08 UTC (rev 5465) @@ -0,0 +1,5 @@ +<html><head> + <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> + <title>jBPM Tools Reference Guide</title><link rel="stylesheet" href="css/html.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"><link rel="start" href="index.html" title="jBPM Tools Reference Guide"><link rel="next" href="TargetAudience.html" title="Chapter 1. Introduction"><script xmlns="http://www.w3.org/TR/xhtml1/transitional" type="text/javascript" src="script/toggle.js"></script></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">jBPM Tools Reference Guide</th></tr><tr><td width="20%" align="left"> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="TargetAudience.html">Next</a></td></tr></table><hr></div><div class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="d0e1"></a>jBPM Tools Reference! Guide</h1></div><div><p class="releaseinfo"> +</p><p>Version: 3.1.1</p><p class="releaseinfo"> +</p></div><div><p class="copyright">Copyright © 2007 Red Hat</p></div></div><hr></div><div class="toc"><dl><dt xmlns="http://www.w3.org/TR/xhtml1/transitional"><span onclick="toc.expand(this)" class="expand_collapse_toc" style="">+</span><span onclick="toc.collapse(this)" class="expand_collapse_toc" style="display:none;">-</span><span xmlns="" class="chapter"><a href="TargetAudience.html">1. Introduction</a></span></dt><dd xmlns="http://www.w3.org/TR/xhtml1/transitional" style="display:none;"><dl><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="TargetAudience.html#Preface">1.1. Preface</a></span></dt><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="TargetAudience.html#feature_list">1.2. Feature list</a></span></dt></dl></dd><dt xmlns="http://www.w3.org/TR/xhtml1/transitional"><span class="expand_collapse_toc" style="visibility:hidd! en;">  </span><span xmlns="" class="chapter"><a href="jboss_jbpm_runtime_installation.html">2. JBoss jBPM Runtime Installation</a></span></dt><dt xmlns="http://www.w3.org/TR/xhtml1/transitional"><span onclick="toc.expand(this)" class="expand_collapse_toc" style="">+</span><span onclick="toc.collapse(this)" class="expand_collapse_toc" style="display:none;">-</span><span xmlns="" class="chapter"><a href="GuidedTourJBossjBPMGPD.html">3. A Guided Tour of JBoss jBPM GPD</a></span></dt><dd xmlns="http://www.w3.org/TR/xhtml1/transitional" style="display:none;"><dl><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="GuidedTourJBossjBPMGPD.html#CreatingjBPMProject">3.1. Creating a jBPM Project</a></span></dt><dt><span onclick="toc.expand(this)" class="expand_collapse_toc" style="">+</span><span onclick="toc.collapse(this)" class="expand_collapse_toc" style="display:none;">-</span><span xmlns="" class="section"><! a href="GuidedTourJBossjBPMGPD.html#creating_an_empty_process_definiti on">3.2. Creating an Empty Process Definition</a></span></dt><dd style="display:none;"><dl><dt><span onclick="toc.expand(this)" class="expand_collapse_toc" style="">+</span><span onclick="toc.collapse(this)" class="expand_collapse_toc" style="display:none;">-</span><span xmlns="" class="section"><a href="GuidedTourJBossjBPMGPD.html#minimal_process_definition">3.2.1. A Minimal Process Definition</a></span></dt><dd style="display:none;"><dl><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="GuidedTourJBossjBPMGPD.html#adding_the_nodes">3.2.1.1. Adding the Nodes</a></span></dt><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="GuidedTourJBossjBPMGPD.html#adding_transitions">3.2.1.2. Adding Transitions</a></span></dt></dl></dd></dl></dd></dl></dd><dt xmlns="http://www.w3.org/TR/xhtml1/transitional"><span onclick="toc.expand(this)" class="expand_! collapse_toc" style="">+</span><span onclick="toc.collapse(this)" class="expand_collapse_toc" style="display:none;">-</span><span xmlns="" class="chapter"><a href="the_views.html">4. The views</a></span></dt><dd xmlns="http://www.w3.org/TR/xhtml1/transitional" style="display:none;"><dl><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="the_views.html#the_outline_view">4.1. The Outline View</a></span></dt><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="the_views.html#the_overview">4.2. The Overview</a></span></dt><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="the_views.html#the_properties_view">4.3. The Properties View</a></span></dt><dt><span onclick="toc.expand(this)" class="expand_collapse_toc" style="">+</span><span onclick="toc.collapse(this)" class="expand_colla! pse_toc" style="display:none;">-</span><span xmlns="" class="section"> <a href="the_views.html#jbpm_gpd_editor">4.4. The jBPM Graphical Process Designer editor.</a></span></dt><dd style="display:none;"><dl><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="the_views.html#the_diagram_mode">4.4.1. The Diagram mode</a></span></dt><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="the_views.html#source_mode">4.4.2. The Source Mode</a></span></dt><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="the_views.html#design_mode">4.4.3. The Design Mode</a></span></dt><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="the_views.html#deployment_mode">4.4.4. The Deployment Mode</a></span></dt></dl></dd></dl></dd><dt xmlns="http://www.w3.org/TR/xhtml1/transitional"><span class="expand_collaps! e_toc" style="visibility:hidden;">  </span><span xmlns="" class="chapter"><a href="Test_Drive_Proc_Development.html">5. Test Driven Process Development</a></span></dt><dt xmlns="http://www.w3.org/TR/xhtml1/transitional"><span onclick="toc.expand(this)" class="expand_collapse_toc" style="">+</span><span onclick="toc.collapse(this)" class="expand_collapse_toc" style="display:none;">-</span><span xmlns="" class="chapter"><a href="The_JBoss_jBPM_Int_Mech.html">6. Actions : The JBoss jBPM Integration Mechanism</a></span></dt><dd xmlns="http://www.w3.org/TR/xhtml1/transitional" style="display:none;"><dl><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="The_JBoss_jBPM_Int_Mech.html#d0e931">6.1. Creating a Hello World Action</a></span></dt><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="The_JBoss_jBPM_Int_Mech.html#d0e1045">6.2. Integratin! g the Hello World Action</a></span></dt><dt><span class="expand_collap se_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="The_JBoss_jBPM_Int_Mech.html#d0e1147">6.3. Integration Points</a></span></dt></dl></dd><dt xmlns="http://www.w3.org/TR/xhtml1/transitional"><span onclick="toc.expand(this)" class="expand_collapse_toc" style="">+</span><span onclick="toc.collapse(this)" class="expand_collapse_toc" style="display:none;">-</span><span xmlns="" class="chapter"><a href="Quick_Howto_Guide.html">7. Quick Howto Guide</a></span></dt><dd xmlns="http://www.w3.org/TR/xhtml1/transitional" style="display:none;"><dl><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="Quick_Howto_Guide.html#change_core_jbpm_inst">7.1. Change the Default Core jBPM Installation</a></span></dt><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="Quick_Howto_Guide.html#d0e1206">7.2. Configuring Task Nodes</a>! </span></dt></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="TargetAudience.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"> </td><td width="20%" align="center"> </td><td width="40%" align="right" valign="top"> Chapter 1. Introduction</td></tr></table></div></body></html> \ No newline at end of file Added: trunk/jbpm/docs/build/reference/en/html/jboss_jbpm_runtime_installation.html =================================================================== --- trunk/jbpm/docs/build/reference/en/html/jboss_jbpm_runtime_installation.html (rev 0) +++ trunk/jbpm/docs/build/reference/en/html/jboss_jbpm_runtime_installation.html 2007-12-28 11:34:08 UTC (rev 5465) @@ -0,0 +1,16 @@ +<html><head> + <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> + <title>Chapter 2. JBoss jBPM Runtime Installation</title><link rel="stylesheet" href="css/html.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"><meta name="keywords" content="jBPM, designer, process, JBoss Developer Studio, jBPM runtime"><link rel="start" href="index.html" title="jBPM Tools Reference Guide"><link rel="up" href="index.html" title="jBPM Tools Reference Guide"><link rel="prev" href="TargetAudience.html" title="Chapter 1. Introduction"><link rel="next" href="GuidedTourJBossjBPMGPD.html" title="Chapter 3. A Guided Tour of JBoss jBPM GPD"><script xmlns="http://www.w3.org/TR/xhtml1/transitional" type="text/javascript" src="script/toggle.js"></script></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 2. JBoss jBPM Runtime Installation</t! h></tr><tr><td width="20%" align="left"><a accesskey="p" href="TargetAudience.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="GuidedTourJBossjBPMGPD.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="jboss_jbpm_runtime_installation"></a>Chapter 2. JBoss jBPM Runtime Installation</h2></div></div></div><p>The main purpose of this chapter is to let you know how to launch the <span class="property">JBoss + jBPM</span> (business process management).</p><p>The jBPM plugin (jBPM Designer) is already included in the <span class="property">JBoss Tools</span>. To make it work, you should only download the jBPM runtime (jbpm-jpdl-3.2.2 + currently) from <a class="ulink" href="http://labs.jboss.com/jbossjbpm/downloads/" target="_top">here</a> and specify + the directory where you extracted the runtime either when you create a jBPM project or by using + the jBPM preference pages.</p><p>Navigate to <span class="emphasis"><em> + <span class="property">Window > Preferences > JBoss jBPM > Runtime Locations</span> + </em></span>. Here you can add, edit and remove JBoss jBPM installation locations. Click <span class="emphasis"><em> + <span class="property">Add</span> + </em></span> button. In the diallog that appeared enter a name for a newly added jBPM runtime and + point to the correct location of this package on your harddrive. Click <span class="emphasis"><em> + <span class="property">OK</span> + </em></span> then click <span class="emphasis"><em> + <span class="property">OK</span> + </em></span> again.</p><div class="figure"><a name="d0e195"></a><div class="figure-contents"><div class="mediaobject"><img src="images/runtime_installation/runtime_installation1.png" alt="Adding jBPM Location"></div></div><p class="title"><b>Figure 2.1. Adding jBPM Location</b></p></div><br class="figure-break"><p>Now, when you have a runtime installed, we are going to demonstrate some powerful features of the jBPM.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="TargetAudience.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="GuidedTourJBossjBPMGPD.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 1. Introduction </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter&n! bsp;3. A Guided Tour of JBoss jBPM GPD</td></tr></table></div></body></html> \ No newline at end of file Added: trunk/jbpm/docs/build/reference/en/html/script/toggle.js =================================================================== --- trunk/jbpm/docs/build/reference/en/html/script/toggle.js (rev 0) +++ trunk/jbpm/docs/build/reference/en/html/script/toggle.js 2007-12-28 11:34:08 UTC (rev 5465) @@ -0,0 +1,43 @@ +function dbToggle(node, expandText, collapseText) { + var dt = node.parentNode; + if (dt.nodeName.toLowerCase() == 'dt') { + var dd = dt.nextSibling; + + if (dd && dd.nodeName.toLowerCase() == 'dd') { + + if (dd.style && dd.style.display == 'none') { + dd.style.display = ''; + node.innerHTML = collapseText; + } else { + dd.style.display = 'none'; + node.innerHTML = expandText; + } + + } + + } + +} + +var toc = { + expand: function(node) { + toc.show(toc.findDD(node)) + toc.hide(node); + toc.show(node.nextSibling); + }, + collapse : function(node) { + toc.hide(toc.findDD(node)) + toc.hide(node); + toc.show(node.previousSibling); + }, + findDD : function(node) { + return node.parentNode.nextSibling; + }, + + hide: function(node) { + node.style.display = "none"; + }, + show: function(node) { + node.style.display = ""; + } +}; \ No newline at end of file Added: trunk/jbpm/docs/build/reference/en/html/the_views.html =================================================================== --- trunk/jbpm/docs/build/reference/en/html/the_views.html (rev 0) +++ trunk/jbpm/docs/build/reference/en/html/the_views.html 2007-12-28 11:34:08 UTC (rev 5465) @@ -0,0 +1,56 @@ +<html><head> + <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> + <title>Chapter 4. The views</title><link rel="stylesheet" href="css/html.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"><meta name="keywords" content="jBPM"><link rel="start" href="index.html" title="jBPM Tools Reference Guide"><link rel="up" href="index.html" title="jBPM Tools Reference Guide"><link rel="prev" href="GuidedTourJBossjBPMGPD.html" title="Chapter 3. A Guided Tour of JBoss jBPM GPD"><link rel="next" href="Test_Drive_Proc_Development.html" title="Chapter 5. Test Driven Process Development"><script xmlns="http://www.w3.org/TR/xhtml1/transitional" type="text/javascript" src="script/toggle.js"></script></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 4. The views</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Guided! TourJBossjBPMGPD.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="Test_Drive_Proc_Development.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="the_views"></a>Chapter 4. The views</h2></div></div></div><p>Here, it will be explained how to work with views and editors provided by JBDS.</p><p>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 + currant-active file are immediately displayed in them. Let’s get acquainted more closely + with those that the jPDL perspective provides. </p><div class="figure"><a name="d0e536"></a><div class="figure-contents"><div class="mediaobject"><img src="images/the_views/the_views.png" alt="The jPDL Perspective Views and Editors"></div></div><p class="title"><b>Figure 4.1. The jPDL Perspective Views and Editors</b></p></div><br class="figure-break"><p>As you can see in the picture above, the jPDL perspective contains a complete set of + functionality that's necessary for working on the jBPM project.</p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="the_outline_view"></a>4.1. The Outline View</h2></div></div></div><p>To have a way to quickly see an outline of the process use the Outline view that is + presented as the classical tree. If it is not visible select <span class="emphasis"><em> + <span class="property">Window > Show view > Outline</span> + </em></span>.</p><div class="figure"><a name="d0e556"></a><div class="figure-contents"><div class="mediaobject"><img src="images/the_views/the_views1.png" alt="The Overview View"></div></div><p class="title"><b>Figure 4.2. The Overview View</b></p></div><br class="figure-break"></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="the_overview"></a>4.2. The Overview</h2></div></div></div><p>The main advantage of this view is that it gives visual representation of the whole + currant-developing process. Besides, the Overview comes as a scrollable thumbnail which + enables a better navigation of the process structure if it's too large.</p><div class="figure"><a name="d0e568"></a><div class="figure-contents"><div class="mediaobject"><img src="images/the_views/the_views2.png" alt="The Overview"></div></div><p class="title"><b>Figure 4.3. The Overview</b></p></div><br class="figure-break"></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="the_properties_view"></a>4.3. The Properties View</h2></div></div></div><p> Here, we dwell on the JBDS <span class="property">Properties view</span>.</p><p>Notice if it's not visible you can access it by navigating <span class="emphasis"><em> + <span class="property">Window > Show view > Properties</span> + </em></span>.</p><p>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.</p><div class="figure"><a name="d0e593"></a><div class="figure-contents"><div class="mediaobject"><img src="images/the_views/the_views3.png" alt="The Properties View of selected Transition"></div></div><p class="title"><b>Figure 4.4. The Properties View of selected Transition</b></p></div><br class="figure-break"><p>For example, on the picture above the Properties view displays all the properties for + a selected transition. Its name has been changed to <span class="emphasis"><em> + <span class="property">to_auction</span> + </em></span>. 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 <span class="emphasis"><em> + <span class="property">to_end</span> + </em></span>.</p><p>If no one item is selected, the view represents the properties of the whole process + definition. </p><div class="figure"><a name="d0e615"></a><div class="figure-contents"><div class="mediaobject"><img src="images/the_views/the_views4.png" alt="The Properties View of Process Definition"></div></div><p class="title"><b>Figure 4.5. The Properties View of Process Definition</b></p></div><br class="figure-break"><p>In this case, it contains six tabs. The first one is the <span class="emphasis"><em> + <span class="property">General</span></em></span>. It allows to specify + a process name and add necessary description. To illustrate let's change the process + definition name to <span class="emphasis"><em> + <span class="property">jbay</span> + </em></span></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="jbpm_gpd_editor"></a>4.4. The jBPM Graphical Process Designer editor.</h2></div></div></div><p>The jBPM GPD editor 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.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="the_diagram_mode"></a>4.4.1. The Diagram mode</h3></div></div></div><p> 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. </p><div class="figure"><a name="d0e644"></a><div class="figure-contents"><div class="mediaobject"><img src="images/the_views/the_views5.png" alt="The Diagram mode"></div></div><p class="title"><b>Figure 4.6. The Diagram mode</b></p></div><br class="figure-break"><p>Besides, some properties can be directly edited in the Diagram mode of the + graphical editor. One example of this is the <span class="emphasis"><em> + <span class="property">name</span> + </em></span> 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 <span class="emphasis"><em> + <span class="property">auction</span> + </em></span>.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="source_mode"></a>4.4.2. The Source Mode</h3></div></div></div><p>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.</p><div class="figure"><a name="d0e670"></a><div class="figure-contents"><div class="mediaobject"><img src="images/the_views/the_views6.png" alt="The Source Mode"></div></div><p class="title"><b>Figure 4.7. The Source Mode</b></p></div><br class="figure-break"><p>The Source mode 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.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="design_mode"></a>4.4.3. The Design Mode</h3></div></div></div><p>One more way to edit your file is to use <span class="property">Design mode</span>. You can + see it in the next picture:</p><div class="figure"><a name="d0e687"></a><div class="figure-contents"><div class="mediaobject"><img src="images/the_views/the_views7.png" alt="The Design Mode"></div></div><p class="title"><b>Figure 4.8. The Design Mode</b></p></div><br class="figure-break"><p>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.</p><p>For instance, let’s add a comment on the second transition. For that, you should + bring up the context menu for it and choose <span class="emphasis"><em> + <span class="property">Add Before > Comment</span> + </em></span>.</p><div class="figure"><a name="d0e703"></a><div class="figure-contents"><div class="mediaobject"><img src="images/the_views/the_views8.png" alt="Adding a Comment"></div></div><p class="title"><b>Figure 4.9. Adding a Comment</b></p></div><br class="figure-break"><p>Then, we can put the text <span class="emphasis"><em>This + transition leads to the end state</em></span> in the right column as its value.</p><div class="figure"><a name="d0e714"></a><div class="figure-contents"><div class="mediaobject"><img src="images/the_views/the_views9.png" alt="Comment is added"></div></div><p class="title"><b>Figure 4.10. Comment is added</b></p></div><br class="figure-break"></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="deployment_mode"></a>4.4.4. The Deployment Mode</h3></div></div></div><p>Finally, to adjust the deployment settings of the project you should switch on to + the tab that opens the Deployment mode. On the picture below the Deployment mode is + performed with default settings. Here, you can easily modify them or, if the + settings won't match your needs, to reset defaults. </p><div class="figure"><a name="d0e726"></a><div class="figure-contents"><div class="mediaobject"><img src="images/the_views/the_views10.png" alt="The Deployment Mode"></div></div><p class="title"><b>Figure 4.11. The Deployment Mode</b></p></div><br class="figure-break"><p>The button <span class="emphasis"><em> + <span class="property">Test Connections</span> + </em></span> is necessary to make sure whether all your settings are valid before + deploying the process.</p></div></div><p>Now that we've seen how to work with jPDL perspective, let's pass on to the project testing.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="GuidedTourJBossjBPMGPD.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="Test_Drive_Proc_Development.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 3. A Guided Tour of JBoss jBPM GPD </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 5. Test Driven Process Development</td></tr></table></div></body></html> \ No newline at end of file Added: trunk/jbpm/docs/build/reference/en/html_single/css/html.css =================================================================== --- trunk/jbpm/docs/build/reference/en/html_single/css/html.css (rev 0) +++ trunk/jbpm/docs/build/reference/en/html_single/css/html.css 2007-12-28 11:34:08 UTC (rev 5465) @@ -0,0 +1,346 @@ +* { + LINE-HEIGHT: 20px; FONT-FAMILY: verdana, helvetica, sans-serif +} +DIV.navheader TABLE, DIV.navheader TABLE td, DIV.navfooter TABLE, DIV.navfooter TABLE td{ + BORDER-RIGHT: 0px; BORDER-TOP: 0px; MARGIN: 0px; BORDER-LEFT: 0px; BORDER-BOTTOM: 0px; FONT-SIZE: 11px; padding : 0px; +} +A { + COLOR: #2a7bd4; FONT-FAMILY: verdana, helvetica, sans-serif +} +A:hover { + COLOR: #003399; FONT-FAMILY: verdana, helvetica, sans-serif +} +A:visited { + COLOR: #888888; FONT-FAMILY: verdana, helvetica, sans-serif +} +P { + FONT-SIZE: 12px; COLOR: #000000; margin : 5px 0px 5px 0px; +} +OL { + FONT-SIZE: 12px; COLOR: #000000; margin-top : 5px; margin-bottom : 5px; +} +UL { + FONT-SIZE: 12px; COLOR: #000000; margin-top : 5px; margin-bottom : 5px; +} +LI { + FONT-SIZE: 12px; COLOR: #000000; margin-top : 5px; margin-bottom : 5px; +} +DL { + FONT-SIZE: 12px; COLOR: #000000; margin-top : 5px; margin-bottom : 5px; +} +DT { + FONT-SIZE: 12px; COLOR: #000000; margin-top : 5px; margin-bottom : 5px; +} +DD { + FONT-SIZE: 12px; COLOR: #000000; margin-top : 5px; margin-bottom : 5px; +} +BLOCKQUOTE { + FONT-SIZE: 12px; COLOR: #000000 +} +TD { + COLOR: #000000 +} +TH { + COLOR: #000000 +} +SPAN { + COLOR: #000000 +} +SPAN.property { + COLOR: #008cca; +} +SPAN.italic { + FONT-STYLE: italic; +} + +BLOCKQUOTE { + MARGIN-RIGHT: 0px +} + +P.title { + MARGIN-BOTTOM: 5px; + MARGIN-top: 20px; +} + +div.book div.chapter .title { + text-align: left; +} + + +div.book .title { + text-align: center; +} + +.mediaobject{ + padding : 5px 10px 5px 35px; +} +H1 { + MARGIN: 0px; FONT-SIZE: 22px; COLOR: #ff6600; PADDING: 45px 0px 10px 0px; +} +H2 { + MARGIN: 0px; FONT-SIZE: 18px; COLOR: #2a7bd4; PADDING: 25px 0px 10px 0px; +} +H3 { + MARGIN: 0px; FONT-SIZE: 15px; COLOR: #000000; PADDING: 20px 0px 10px 0px; +} +H4 { + MARGIN: 0px; FONT-SIZE: 12px; COLOR: #000000; PADDING: 15px 0px 10px 0px; +} +H5 { + MARGIN: 0px; FONT-SIZE: 12px; COLOR: #000000; PADDING: 15px 0px 10px 0px; +} +H6 { + MARGIN: 0px; FONT-SIZE: 11px; COLOR: #000000; PADDING: 5px 0px 0px 0px; +} + +div.book div.section div.mediaobject{ +text-align:left; +} + + +div.book div.mediaobject{ +text-align:left; +} + +div.mediaobject, div.mediaobject img *{ +text-align:left; + +} + +DIV.note{ + BORDER: #CECECE 1px solid; PADDING: 3px 10px 10px 50px; line-height : 14px; MARGIN: 10px 0px 10px 0px; FONT-SIZE: 11px; WIDTH: 500px; BACKGROUND-COLOR: #FFFDD3; + background-image : url('Images/ico_note.gif'); background-repeat : no-repeat; background-position :top left; +} + +DIV.note *{ + line-height : 14px; +} + +.note P { + MARGIN-TOP: 0px; MARGIN-BOTTOM: 1em; PADDING-BOTTOM: 0px; PADDING-TOP: 0px +} +.important P { + MARGIN-TOP: 0px; MARGIN-BOTTOM: 1em; PADDING-BOTTOM: 0px; PADDING-TOP: 0px +} +DIV.important { + BORDER: #CECECE 1px solid; PADDING: 3px 10px 10px 50px; line-height : 14px; MARGIN: 10px 0px 10px 0px; FONT-SIZE: 11px; WIDTH: 500px; BACKGROUND-COLOR: #CFE3FF; + background-image : url('Images/ico_important.gif'); background-repeat : no-repeat; background-position :top left; +} + +DIV.important *{ + line-height : 14px; +} + +.important pre.XML { +PADDING: 1px 1px 1px 10px; + +} + + +TABLE { + BORDER: #cccccc 1px solid; FONT-SIZE: 11px; BORDER-COLLAPSE: collapse; border-spacing: 0; empty-cells: hide; margin-bottom : 10px; +} + +table *{ + line-height : 14px; +} + + +.table TH { + WHITE-SPACE: nowrap; BACKGROUND-COLOR: #EEF5FF; TEXT-ALIGN: center; BORDER-BOTTOM: #CAE1FF 2px solid; PADDING: 2px 8px 2px 8px; + background-image : url('Images/bg_table.gif'); background-repeat : repeat-x; background-position :top left; +} +TD { + PADDING: 4px 8px 4px 8px; BORDER-BOTTOM: #cccccc 1px dotted; BORDER-right: #cccccc 1px dotted; +} +P.copyright { + TEXT-ALIGN: center +} +TT { + FONT-SIZE: 90%; COLOR: #000000; FONT-FAMILY: "Courier New", Courier, monospace +} +DL { + MARGIN-BOTTOM: 6px; MARGIN-LEFT: 8px +} +DT { + MARGIN-BOTTOM: 6px; MARGIN-LEFT: 8px +} +DD { + MARGIN-BOTTOM: 6px; MARGIN-LEFT: 8px +} +PRE { + BORDER: #cccccc 1px solid; PADDING: 5px 15px 5px 25px; FONT-SIZE: 11px; BACKGROUND-COLOR: #f5f5f5; +} +HR { + BORDER-TOP-WIDTH: 0px; PADDING-RIGHT: 0px; PADDING-LEFT: 0px; BORDER-LEFT-WIDTH: 0px; BORDER-BOTTOM-WIDTH: 0px; PADDING-BOTTOM: 0px; WIDTH: 100%; COLOR: #cccccc; PADDING-TOP: 0px; HEIGHT: 1px; BACKGROUND-COLOR: #cccccc; BORDER-RIGHT-WIDTH: 0px +} +.variablelist { + PADDING-BOTTOM: 10px; MARGIN: 0px; PADDING-TOP: 10px +} +.itemizedlist { + FONT-SIZE: 12px; PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-TOP: 0px;TEXT-ALIGN: justify +} +.term { + FONT-WEIGHT: bold +} +PRE.JAVA { + LINE-HEIGHT: 0px +} +PRE.XML { + LINE-HEIGHT: 0px +} +PRE.JSP { + LINE-HEIGHT: 0px +} +PRE.XHTML { + LINE-HEIGHT: 0px +} +.java_type { + COLOR: #008cca +} +.java_keyword { + FONT-WEIGHT: bold; COLOR: rgb(0,0,0) +} +.java_javadoc_comment { + COLOR: rgb(147,147,147); FONT-STYLE: italic; BACKGROUND-COLOR: rgb(247,247,247) +} +.java_comment { + COLOR: rgb(147,147,147); BACKGROUND-COLOR: rgb(247,247,247) +} +.java_operator { + COLOR: #003399 +} +.java_plain { + COLOR: rgb(0,0,0) +} +.java_literal { + COLOR: #ff6600 +} +PRE CODE { + FONT-SIZE: 12px; COLOR: rgb(0,0,0); FONT-FAMILY: monospace; WHITE-SPACE: nowrap +} +.java_javadoc_tag { + FONT-WEIGHT: bold; COLOR: rgb(147,147,147); FONT-STYLE: italic; BACKGROUND-COLOR: rgb(247,247,247) +} +.java_separator { + COLOR: #008cca +} +.xml_plain { + COLOR: rgb(0,0,0) +} +.xml_tag_name { + COLOR: #008cca +} +.xml_comment { + COLOR: rgb(147,147,147); BACKGROUND-COLOR: rgb(247,247,247) +} +.xml_tag_symbols { + COLOR: #008cca +} +.xml_rife_tag { + COLOR: rgb(0,0,0); BACKGROUND-COLOR: rgb(228,230,160) +} +.xml_attribute_value { + COLOR: #ff6600 +} +.xml_attribute_name { + FONT-WEIGHT: bold; COLOR: rgb(0,0,0) +} +.xml_char_data { + COLOR: rgb(0,0,0) +} +.xml_rife_name { + COLOR: #008cca; BACKGROUND-COLOR: rgb(228,230,160) +} +.xml_processing_instruction { + FONT-WEIGHT: bold; COLOR: rgb(0,0,0); FONT-STYLE: italic +} +TD.java { + VERTICAL-ALIGN: top; LINE-HEIGHT: 10px +} +TD.java-ln { + VERTICAL-ALIGN: top; LINE-HEIGHT: 10px +} +TT.java { + MARGIN-BOTTOM: 0em; LINE-HEIGHT: 10px +} +TT.java-ln { + MARGIN-BOTTOM: 0em; LINE-HEIGHT: 10px +} +PRE.java { + MARGIN-BOTTOM: 0em; LINE-HEIGHT: 10px +} +PRE.java-ln { + MARGIN-BOTTOM: 0em; LINE-HEIGHT: 10px +} +TD.java-ln { + LINE-HEIGHT: 10px; TEXT-ALIGN: right +} +TT.java-ln { + COLOR: #888888; LINE-HEIGHT: 10px +} +PRE.java-ln { + COLOR: #888888; LINE-HEIGHT: 10px +} +SPAN.java0 { + FONT-SIZE: 8pt; COLOR: #ffffff; LINE-HEIGHT: 10px +} +SPAN.java1 { + FONT-SIZE: 8pt; COLOR: #808080 +} +SPAN.java2 { + FONT-SIZE: 8pt; COLOR: #3f7f5f; LINE-HEIGHT: 10px +} +SPAN.java3 { + FONT-SIZE: 8pt; COLOR: #3f7f5f; LINE-HEIGHT: 10px +} +SPAN.java4 { + FONT-WEIGHT: bold; FONT-SIZE: 8pt; COLOR: #ff6600; LINE-HEIGHT: 10px +} +SPAN.java5 { + FONT-SIZE: 8pt; COLOR: #2a00ff; LINE-HEIGHT: 10px +} +SPAN.java6 { + FONT-SIZE: 8pt; COLOR: #990000; LINE-HEIGHT: 10px +} +SPAN.java7 { + FONT-SIZE: 8pt; COLOR: #990000; LINE-HEIGHT: 10px +} +SPAN.java8 { + FONT-SIZE: 8pt; COLOR: #000000; LINE-HEIGHT: 10px +} +SPAN.java9 { + FONT-WEIGHT: bold; FONT-SIZE: 8pt; COLOR: #ff6600; LINE-HEIGHT: 10px +} +SPAN.java10 { + FONT-SIZE: 8pt; COLOR: #000000; LINE-HEIGHT: 10px +} +SPAN.java11 { + FONT-SIZE: 8pt; COLOR: #7f9fbf; LINE-HEIGHT: 10px +} +SPAN.java12 { + FONT-SIZE: 8pt; COLOR: #7f7f9f; LINE-HEIGHT: 10px +} +SPAN.java13 { + FONT-SIZE: 8pt; COLOR: #3f3fbf; LINE-HEIGHT: 10px +} +SPAN.java14 { + FONT-SIZE: 8pt; COLOR: #3f5fbf; LINE-HEIGHT: 10px +} +SPAN.java15 { + FONT-SIZE: 8pt; COLOR: #ff6100; LINE-HEIGHT: 10px +} +SPAN.java16 { + FONT-SIZE: 8pt; COLOR: #646464; LINE-HEIGHT: 10px +} + +.expand_collapse_toc { + clear:both; + float:left; + font-family:monospace; + width:20px; + color: #2A7BD4; + cursor: pointer; +} + + Added: trunk/jbpm/docs/build/reference/en/html_single/css/images/bg_table.gif =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/css/images/bg_table.gif ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/css/images/ico_important.gif =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/css/images/ico_important.gif ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/css/images/ico_note.gif =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/css/images/ico_note.gif ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/defaltImage.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/defaltImage.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_1.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_2.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_3.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_4.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_4.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_5.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_5.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_6.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_6.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_7.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_7.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_8.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_8.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_9.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/Quick_Howto_Guide/quick_howto_guide_9.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/defaltImage.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/defaltImage.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_1.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_1a.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_1a.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_1b.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_1b.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_2.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_2a.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_2a.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_2b.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_2b.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_3.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_4.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_4.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_5.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/Test_Drive_Proc/test_driv_proc_5.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/defaltImage.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/defaltImage.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_1.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_10.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_10.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_2.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_3.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_4.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_4.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_5.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_5.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_6.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_6.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_7.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_7.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_8.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_8.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/default.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/default.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour1.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour10.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour10.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour11.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour11.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour12.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour12.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour13.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour13.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour14.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour14.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour15.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour15.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour2.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour2_b.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour2_b.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour3.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour4.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour4.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour5.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour5.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour6.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour6.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour7.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour7.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour8.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour8.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour9.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/guided_tour_jboss_jbpmgpd/guided_tour9.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/runtime_installation/runtime_installation1.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/runtime_installation/runtime_installation1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views1.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views10.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views10.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views2.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views3.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views4.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views4.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views5.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views5.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views6.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views6.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views7.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views7.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views8.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views8.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views9.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/html_single/images/the_views/the_views9.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/build/reference/en/html_single/index.html =================================================================== --- trunk/jbpm/docs/build/reference/en/html_single/index.html (rev 0) +++ trunk/jbpm/docs/build/reference/en/html_single/index.html 2007-12-28 11:34:08 UTC (rev 5465) @@ -0,0 +1,338 @@ +<html><head> + <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> + <title>jBPM Tools Reference Guide</title><link rel="stylesheet" href="css/html.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"><script xmlns="http://www.w3.org/TR/xhtml1/transitional" type="text/javascript" src="script/toggle.js"></script></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="d0e1"></a>jBPM Tools Reference Guide</h1></div><div><p class="releaseinfo"> +</p><p>Version: 3.1.1</p><p class="releaseinfo"> +</p></div><div><p class="copyright">Copyright © 2007 Red Hat</p></div></div><hr></div><div class="toc"><dl><dt xmlns="http://www.w3.org/TR/xhtml1/transitional"><span onclick="toc.expand(this)" class="expand_collapse_toc" style="">+</span><span onclick="toc.collapse(this)" class="expand_collapse_toc" style="display:none;">-</span><span xmlns="" class="chapter"><a href="#Introduction">1. Introduction</a></span></dt><dd xmlns="http://www.w3.org/TR/xhtml1/transitional" style="display:none;"><dl><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="#Preface">1.1. Preface</a></span></dt><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="#feature_list">1.2. Feature list</a></span></dt></dl></dd><dt xmlns="http://www.w3.org/TR/xhtml1/transitional"><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="cha! pter"><a href="#jboss_jbpm_runtime_installation">2. JBoss jBPM Runtime Installation</a></span></dt><dt xmlns="http://www.w3.org/TR/xhtml1/transitional"><span onclick="toc.expand(this)" class="expand_collapse_toc" style="">+</span><span onclick="toc.collapse(this)" class="expand_collapse_toc" style="display:none;">-</span><span xmlns="" class="chapter"><a href="#GuidedTourJBossjBPMGPD">3. A Guided Tour of JBoss jBPM GPD</a></span></dt><dd xmlns="http://www.w3.org/TR/xhtml1/transitional" style="display:none;"><dl><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="#CreatingjBPMProject">3.1. Creating a jBPM Project</a></span></dt><dt><span onclick="toc.expand(this)" class="expand_collapse_toc" style="">+</span><span onclick="toc.collapse(this)" class="expand_collapse_toc" style="display:none;">-</span><span xmlns="" class="section"><a href="#creating_an_empty_process_definition">3.2. Creating an Empty Process D! efinition</a></span></dt><dd style="display:none;"><dl><dt><span oncli ck="toc.expand(this)" class="expand_collapse_toc" style="">+</span><span onclick="toc.collapse(this)" class="expand_collapse_toc" style="display:none;">-</span><span xmlns="" class="section"><a href="#minimal_process_definition">3.2.1. A Minimal Process Definition</a></span></dt><dd style="display:none;"><dl><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="#adding_the_nodes">3.2.1.1. Adding the Nodes</a></span></dt><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="#adding_transitions">3.2.1.2. Adding Transitions</a></span></dt></dl></dd></dl></dd></dl></dd><dt xmlns="http://www.w3.org/TR/xhtml1/transitional"><span onclick="toc.expand(this)" class="expand_collapse_toc" style="">+</span><span onclick="toc.collapse(this)" class="expand_collapse_toc" style="display:none;">-</span><span xmlns="" class="chapter"><a href="#the_views">4. The view! s</a></span></dt><dd xmlns="http://www.w3.org/TR/xhtml1/transitional" style="display:none;"><dl><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="#the_outline_view">4.1. The Outline View</a></span></dt><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="#the_overview">4.2. The Overview</a></span></dt><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="#the_properties_view">4.3. The Properties View</a></span></dt><dt><span onclick="toc.expand(this)" class="expand_collapse_toc" style="">+</span><span onclick="toc.collapse(this)" class="expand_collapse_toc" style="display:none;">-</span><span xmlns="" class="section"><a href="#jbpm_gpd_editor">4.4. The jBPM Graphical Process Designer editor.</a></span></dt><dd style="display:none;"><dl><dt><span class="expand_collapse_toc" styl! e="visibility:hidden;">  </span><span xmlns="" class="section"><a href="#the_diagram_mode">4.4.1. The Diagram mode</a></span></dt><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="#source_mode">4.4.2. The Source Mode</a></span></dt><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="#design_mode">4.4.3. The Design Mode</a></span></dt><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="#deployment_mode">4.4.4. The Deployment Mode</a></span></dt></dl></dd></dl></dd><dt xmlns="http://www.w3.org/TR/xhtml1/transitional"><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="chapter"><a href="#Test_Drive_Proc_Development">5. Test Driven Process Development</a></span></dt><dt xmlns="http://www.w3.org/TR/xhtml1/transitional"><span onclick="toc.expand(this)" class="expand_collapse_toc" style="">+</span><spa! n onclick="toc.collapse(this)" class="expand_collapse_toc" style="display:none;">-</span><span xmlns="" class="chapter"><a href="#The_JBoss_jBPM_Int_Mech">6. Actions : The JBoss jBPM Integration Mechanism</a></span></dt><dd xmlns="http://www.w3.org/TR/xhtml1/transitional" style="display:none;"><dl><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="#d0e931">6.1. Creating a Hello World Action</a></span></dt><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="#d0e1045">6.2. Integrating the Hello World Action</a></span></dt><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="#d0e1147">6.3. Integration Points</a></span></dt></dl></dd><dt xmlns="http://www.w3.org/TR/xhtml1/transitional"><span onclick="toc.expand(this)" class="expand_collapse_toc" style="">+</span><span onclick="to! c.collapse(this)" class="expand_collapse_toc" style="display:none;">-< /span><span xmlns="" class="chapter"><a href="#Quick_Howto_Guide">7. Quick Howto Guide</a></span></dt><dd xmlns="http://www.w3.org/TR/xhtml1/transitional" style="display:none;"><dl><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="#change_core_jbpm_inst">7.1. Change the Default Core jBPM Installation</a></span></dt><dt><span class="expand_collapse_toc" style="visibility:hidden;">  </span><span xmlns="" class="section"><a href="#d0e1206">7.2. Configuring Task Nodes</a></span></dt></dl></dd></dl></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Introduction"></a>Chapter 1. Introduction</h2></div></div></div><p>All developers and process analysts who are beginning to use JBoss jBPM should read this + Getting Started guide. It will give them a jumpstart showing how to create a process definition.</p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="Preface"></a>1.1. Preface</h2></div></div></div><p>This document introduces the use of the JBoss jBPM Graphical Process Designer (GPD) to + create workflow processes. It will help first time users with the following tasks :</p><div class="itemizedlist"><ul type="disc"><li><p>Install the JBoss jBPM GPD Eclipse plugin available from the JBoss jBPM download + area</p></li><li><p>Set up a Java project in Eclipse and prepare it to do test driven process + development</p></li><li><p>Using the creation wizard to create an empty process definition</p></li><li><p>Use the designer palette to draw the first processdefinition</p></li><li><p>Show how the xml processdefinition can be inspected as an xml file</p></li><li><p>Set up a Java project in Eclipse and prepare it to do test driven process + development</p></li><li><p>Write an example process test case</p></li></ul></div><p>If you have questions, please feel free to contact Koen Aers (koen.aers(a)jboss.com) or Tom Baeyens (tom.baeyens(a)jboss.com) for more + information.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="feature_list"></a>1.2. Feature list</h2></div></div></div><p> JBoss jBPM is a workflow that enables creating and automatization business processes. Look + at the list of features below to understand its main functionality.</p><div class="table"><a name="d0e69"></a><p class="title"><b>Table 1.1. Key Functionality for JBoss jBPM</b></p><div class="table-contents"><table summary="Key Functionality for JBoss jBPM" border="1"><colgroup><col><col></colgroup><thead><tr><th>Feature</th><th>Benefit</th></tr></thead><tbody><tr><td> + <a class="link" href="#minimal_process_definition" title="3.2.1. A Minimal Process Definition">jBDL support</a> + </td><td>Enables managing workflow processes as well as human tasks and interactions between + them. jBDL combines the best both Java and declarative process techniques.</td></tr><tr><td> + <a class="link" href="#GuidedTourJBossjBPMGPD" title="Chapter 3. A Guided Tour of JBoss jBPM GPD">Support of Graphical Process Designer (GPD)</a> + </td><td>Is used for simplifying declarative process development and visualizations of all + actions.</td></tr><tr><td> + <a class="link" href="#CreatingjBPMProject" title="3.1. Creating a jBPM Project">Project Creation wizard</a> + </td><td>Allows to create a new jBPM template project that already includes all advanced + artifacts and core jBPM libraries.</td></tr><tr><td> + <a class="link" href="#minimal_process_definition" title="3.2.1. A Minimal Process Definition">Rich palette of pre-build process nodes</a> + </td><td>Provides process-building functionality and gives opportunity even non-programmers to + develop processes.</td></tr><tr><td> + <a class="link" href="#source_mode" title="4.4.2. The Source Mode">Support of XML code view</a> + </td><td>Shows the corresponding XML that's generated automatically in the Source view of the process + definition editor when developing the process.</td></tr><tr><td> + <a class="link" href="#the_properties_view" title="4.3. The Properties View">Properties view</a> + </td><td>Facilitates configuring and editing of all nodes properties.</td></tr><tr><td>Interaction with all of the J2EE based integration technologies including Web Services, + Java Messaging, J2EE Connectors, JBDC, EJBs.</td><td>Enables implementation, provides better functionality and flexibility.</td></tr><tr><td>Integration with jBoss Seam</td><td>Allows to write applications with complex workflows and provides easier interactions + between them.</td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="jboss_jbpm_runtime_installation"></a>Chapter 2. JBoss jBPM Runtime Installation</h2></div></div></div><p>The main purpose of this chapter is to let you know how to launch the <span class="property">JBoss + jBPM</span> (business process management).</p><p>The jBPM plugin (jBPM Designer) is already included in the <span class="property">JBoss Tools</span>. To make it work, you should only download the jBPM runtime (jbpm-jpdl-3.2.2 + currently) from <a class="ulink" href="http://labs.jboss.com/jbossjbpm/downloads/" target="_top">here</a> and specify + the directory where you extracted the runtime either when you create a jBPM project or by using + the jBPM preference pages.</p><p>Navigate to <span class="emphasis"><em> + <span class="property">Window > Preferences > JBoss jBPM > Runtime Locations</span> + </em></span>. Here you can add, edit and remove JBoss jBPM installation locations. Click <span class="emphasis"><em> + <span class="property">Add</span> + </em></span> button. In the diallog that appeared enter a name for a newly added jBPM runtime and + point to the correct location of this package on your harddrive. Click <span class="emphasis"><em> + <span class="property">OK</span> + </em></span> then click <span class="emphasis"><em> + <span class="property">OK</span> + </em></span> again.</p><div class="figure"><a name="d0e195"></a><div class="figure-contents"><div class="mediaobject"><img src="images/runtime_installation/runtime_installation1.png" alt="Adding jBPM Location"></div></div><p class="title"><b>Figure 2.1. Adding jBPM Location</b></p></div><br class="figure-break"><p>Now, when you have a runtime installed, we are going to demonstrate some powerful features of the jBPM.</p></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="GuidedTourJBossjBPMGPD"></a>Chapter 3. A Guided Tour of JBoss jBPM GPD</h2></div></div></div><p>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.</p><p>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 advanced artifacts that + we will ignore for this section. In the future we will elaborate this wizard and offer the + possibility to create an empty jBPM project as well as projects based on templates taken + from the jBPM tutorial.</p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="CreatingjBPMProject"></a>3.1. Creating a jBPM Project</h2></div></div></div><p>This section will show you how to use the Creation wizard for creating a new jBPM + project with already included source folders.</p><p>At first you should select <span class="emphasis"><em> + <span class="property">File >New Project...</span> + </em></span> and then <span class="emphasis"><em> + <span class="property">JBoss jBPM > Process Project</span> + </em></span> in the New Project dialog:</p><div class="figure"><a name="d0e243"></a><div class="figure-contents"><div class="mediaobject"><img src="images/guided_tour_jboss_jbpmgpd/guided_tour1.png" alt="New Project Dialog"></div></div><p class="title"><b>Figure 3.1. New Project Dialog</b></p></div><br class="figure-break"><p> Clicking <span class="emphasis"><em> + <span class="property">Next</span> + </em></span> brings us to the wizard page where it's necessary to specify the + name and location for the project. We choose, for example, <span class="emphasis"><em> + <span class="property">HellojBPM</span> + </em></span> as the name and accept the default location. </p><div class="figure"><a name="d0e263"></a><div class="figure-contents"><div class="mediaobject"><img src="images/guided_tour_jboss_jbpmgpd/guided_tour2.png" alt="Process Name and Location"></div></div><p class="title"><b>Figure 3.2. Process Name and Location</b></p></div><br class="figure-break"><p>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 <span class="emphasis"><em> + <span class="property">Use default location</span> + </em></span> and click <span class="emphasis"><em> + <span class="property">Browse...</span></em></span> button to set needed location or simply type it.</p><p>On the next screen you'll be prompted to select the core jBPM location that we have defined in the previous chapter.</p><div class="figure"><a name="d0e284"></a><div class="figure-contents"><div class="mediaobject"><img src="images/guided_tour_jboss_jbpmgpd/guided_tour2_b.png" alt="Process Name and Location"></div></div><p class="title"><b>Figure 3.3. Process Name and Location</b></p></div><br class="figure-break"><p>Clicking on <span class="emphasis"><em> + <span class="property">Finish</span> + </em></span> results in the project being generated. The wizard creates four source + folders: one for the processes (<span class="emphasis"><em> + <span class="property">src/main/jpdl</span> + </em></span>), one for the java sources (<span class="emphasis"><em> + <span class="property">src/main/java</span> + </em></span>), one for the unit tests (<span class="emphasis"><em> + <span class="property">src/test/java</span> + </em></span>) and one for the resources such as the jbpm.properties and the + hibernate.properties files (<span class="emphasis"><em> + <span class="property">src/main/config</span> + </em></span>). In addition a classpath container with all the core jBPM libraries is + added to the project</p><div class="figure"><a name="d0e322"></a><div class="figure-contents"><div class="mediaobject"><img src="images/guided_tour_jboss_jbpmgpd/guided_tour3.png" alt="Layout of the Process Project"></div></div><p class="title"><b>Figure 3.4. Layout of the Process Project</b></p></div><br class="figure-break"><p>Looking inside the different source folders will reveal a number of 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 definition.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="creating_an_empty_process_definition"></a>3.2. Creating an Empty Process Definition</h2></div></div></div><p>Now when the project is set up, we can use a Creation wizard to create an empty + process definition. Bring up the <span class="emphasis"><em> + <span class="property">New</span> + </em></span> wizard by clicking the <span class="emphasis"><em> + <span class="property">File > New > Other...</span> + </em></span> menu item. The wizard opens on the <span class="emphasis"><em> + <span class="property">Select Wizard</span> + </em></span> page.</p><div class="figure"><a name="d0e354"></a><div class="figure-contents"><div class="mediaobject"><img src="images/guided_tour_jboss_jbpmgpd/guided_tour4.png" alt="The Select Wizard Page"></div></div><p class="title"><b>Figure 3.5. The Select Wizard Page</b></p></div><br class="figure-break"><p>Selecting the <span class="emphasis"><em> + <span class="property">JBoss jBPM</span> + </em></span> category, then the <span class="emphasis"><em> + <span class="property">Process Definition</span> + </em></span> item and clicking on the <span class="emphasis"><em> + <span class="property">Next</span> + </em></span> button brings us to the <span class="emphasis"><em> + <span class="property">Create Process Definition</span> + </em></span> page.</p><div class="figure"><a name="d0e386"></a><div class="figure-contents"><div class="mediaobject"><img src="images/guided_tour_jboss_jbpmgpd/guided_tour5.png" alt="The Create New Process Definion Page"></div></div><p class="title"><b>Figure 3.6. The Create New Process Definion Page</b></p></div><br class="figure-break"><p>We choose <span class="emphasis"><em> + <span class="property">hello</span> + </em></span> as the name of the process archive file. Click on the <span class="emphasis"><em> + <span class="property">Finish</span> + </em></span> button to end the wizard and open the process definition editor.</p><div class="figure"><a name="d0e406"></a><div class="figure-contents"><div class="mediaobject"><img src="images/guided_tour_jboss_jbpmgpd/guided_tour6.png" alt="The Process Definition Editor"></div></div><p class="title"><b>Figure 3.7. The Process Definition Editor</b></p></div><br class="figure-break"><p>You can see in the Package Explorer that creating a process definition involves + creating a folder with the name of the process definition and populating this folder + with two .xml files : <span class="emphasis"><em> + <span class="property">gpd.xml</span> + </em></span> and <span class="emphasis"><em> + <span class="property">processdefinition.xml</span> + </em></span>.</p><p>The <span class="emphasis"><em> + <span class="property">gpd.xml</span> + </em></span> contains the graphical information used by the process + definition editor. The <span class="emphasis"><em> + <span class="property">processdefinition.xml</span> + </em></span> file contains the actual process definition info without the graphical + rendering info. At present, the GPD assumes that these two files are siblings. More + sophisticated configuration will be supported later.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="minimal_process_definition"></a>3.2.1. A Minimal Process Definition</h3></div></div></div><p>Now we are ready to create a very simple process definition consisting of a begin + state, an intermediate state and an end state.</p><p>To make the configuration of actions much easier it's better to use the + jPDL perspective. It provides the tabbed Properties Editor which allows to configure + all the relevant properties of the current selected item. </p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="adding_the_nodes"></a>3.2.1.1. Adding the Nodes</h4></div></div></div><p>At first select respectively <span class="emphasis"><em> + <span class="property">Start</span> + </em></span>, <span class="emphasis"><em> + <span class="property">State</span> + </em></span> and <span class="emphasis"><em> + <span class="property">End</span> + </em></span> on the tools palette and click on the canvas to add these nodes to + the process definition. The result should look similar to this:</p><div class="figure"><a name="d0e472"></a><div class="figure-contents"><div class="mediaobject"><img src="images/guided_tour_jboss_jbpmgpd/guided_tour7.png" alt="A Simple Process With Three Nodes"></div></div><p class="title"><b>Figure 3.8. A Simple Process With Three Nodes</b></p></div><br class="figure-break"></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="adding_transitions"></a>3.2.1.2. Adding Transitions</h4></div></div></div><p>Then, we will connect the nodes with transitions. To do that select the <span class="emphasis"><em> + <span class="property">Transition</span> + </em></span> tool in the tools palette and click on the <span class="emphasis"><em> + <span class="property">Start</span> + </em></span> node, then move to the <span class="emphasis"><em> + <span class="property">State</span> + </em></span> node and click again to see the transition being drawn. Perform the + same steps to create a transition from the <span class="emphasis"><em> + <span class="property">State</span> + </em></span> node to the <span class="emphasis"><em> + <span class="property">End</span> + </em></span> node. The result will look like:</p><div class="figure"><a name="d0e514"></a><div class="figure-contents"><div class="mediaobject"><img src="images/guided_tour_jboss_jbpmgpd/guided_tour8.png" alt="A Simple Process With Transitions"></div></div><p class="title"><b>Figure 3.9. A Simple Process With Transitions</b></p></div><br class="figure-break"></div></div><p>Now, when you've got background knowledge of simple project creation, let's move to more advanced tools.</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="the_views"></a>Chapter 4. The views</h2></div></div></div><p>Here, it will be explained how to work with views and editors provided by JBDS.</p><p>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 + currant-active file are immediately displayed in them. Let’s get acquainted more closely + with those that the jPDL perspective provides. </p><div class="figure"><a name="d0e536"></a><div class="figure-contents"><div class="mediaobject"><img src="images/the_views/the_views.png" alt="The jPDL Perspective Views and Editors"></div></div><p class="title"><b>Figure 4.1. The jPDL Perspective Views and Editors</b></p></div><br class="figure-break"><p>As you can see in the picture above, the jPDL perspective contains a complete set of + functionality that's necessary for working on the jBPM project.</p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="the_outline_view"></a>4.1. The Outline View</h2></div></div></div><p>To have a way to quickly see an outline of the process use the Outline view that is + presented as the classical tree. If it is not visible select <span class="emphasis"><em> + <span class="property">Window > Show view > Outline</span> + </em></span>.</p><div class="figure"><a name="d0e556"></a><div class="figure-contents"><div class="mediaobject"><img src="images/the_views/the_views1.png" alt="The Overview View"></div></div><p class="title"><b>Figure 4.2. The Overview View</b></p></div><br class="figure-break"></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="the_overview"></a>4.2. The Overview</h2></div></div></div><p>The main advantage of this view is that it gives visual representation of the whole + currant-developing process. Besides, the Overview comes as a scrollable thumbnail which + enables a better navigation of the process structure if it's too large.</p><div class="figure"><a name="d0e568"></a><div class="figure-contents"><div class="mediaobject"><img src="images/the_views/the_views2.png" alt="The Overview"></div></div><p class="title"><b>Figure 4.3. The Overview</b></p></div><br class="figure-break"></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="the_properties_view"></a>4.3. The Properties View</h2></div></div></div><p> Here, we dwell on the JBDS <span class="property">Properties view</span>.</p><p>Notice if it's not visible you can access it by navigating <span class="emphasis"><em> + <span class="property">Window > Show view > Properties</span> + </em></span>.</p><p>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.</p><div class="figure"><a name="d0e593"></a><div class="figure-contents"><div class="mediaobject"><img src="images/the_views/the_views3.png" alt="The Properties View of selected Transition"></div></div><p class="title"><b>Figure 4.4. The Properties View of selected Transition</b></p></div><br class="figure-break"><p>For example, on the picture above the Properties view displays all the properties for + a selected transition. Its name has been changed to <span class="emphasis"><em> + <span class="property">to_auction</span> + </em></span>. 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 <span class="emphasis"><em> + <span class="property">to_end</span> + </em></span>.</p><p>If no one item is selected, the view represents the properties of the whole process + definition. </p><div class="figure"><a name="d0e615"></a><div class="figure-contents"><div class="mediaobject"><img src="images/the_views/the_views4.png" alt="The Properties View of Process Definition"></div></div><p class="title"><b>Figure 4.5. The Properties View of Process Definition</b></p></div><br class="figure-break"><p>In this case, it contains six tabs. The first one is the <span class="emphasis"><em> + <span class="property">General</span></em></span>. It allows to specify + a process name and add necessary description. To illustrate let's change the process + definition name to <span class="emphasis"><em> + <span class="property">jbay</span> + </em></span></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="jbpm_gpd_editor"></a>4.4. The jBPM Graphical Process Designer editor.</h2></div></div></div><p>The jBPM GPD editor 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.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="the_diagram_mode"></a>4.4.1. The Diagram mode</h3></div></div></div><p> 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. </p><div class="figure"><a name="d0e644"></a><div class="figure-contents"><div class="mediaobject"><img src="images/the_views/the_views5.png" alt="The Diagram mode"></div></div><p class="title"><b>Figure 4.6. The Diagram mode</b></p></div><br class="figure-break"><p>Besides, some properties can be directly edited in the Diagram mode of the + graphical editor. One example of this is the <span class="emphasis"><em> + <span class="property">name</span> + </em></span> 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 <span class="emphasis"><em> + <span class="property">auction</span> + </em></span>.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="source_mode"></a>4.4.2. The Source Mode</h3></div></div></div><p>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.</p><div class="figure"><a name="d0e670"></a><div class="figure-contents"><div class="mediaobject"><img src="images/the_views/the_views6.png" alt="The Source Mode"></div></div><p class="title"><b>Figure 4.7. The Source Mode</b></p></div><br class="figure-break"><p>The Source mode 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.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="design_mode"></a>4.4.3. The Design Mode</h3></div></div></div><p>One more way to edit your file is to use <span class="property">Design mode</span>. You can + see it in the next picture:</p><div class="figure"><a name="d0e687"></a><div class="figure-contents"><div class="mediaobject"><img src="images/the_views/the_views7.png" alt="The Design Mode"></div></div><p class="title"><b>Figure 4.8. The Design Mode</b></p></div><br class="figure-break"><p>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.</p><p>For instance, let’s add a comment on the second transition. For that, you should + bring up the context menu for it and choose <span class="emphasis"><em> + <span class="property">Add Before > Comment</span> + </em></span>.</p><div class="figure"><a name="d0e703"></a><div class="figure-contents"><div class="mediaobject"><img src="images/the_views/the_views8.png" alt="Adding a Comment"></div></div><p class="title"><b>Figure 4.9. Adding a Comment</b></p></div><br class="figure-break"><p>Then, we can put the text <span class="emphasis"><em>This + transition leads to the end state</em></span> in the right column as its value.</p><div class="figure"><a name="d0e714"></a><div class="figure-contents"><div class="mediaobject"><img src="images/the_views/the_views9.png" alt="Comment is added"></div></div><p class="title"><b>Figure 4.10. Comment is added</b></p></div><br class="figure-break"></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="deployment_mode"></a>4.4.4. The Deployment Mode</h3></div></div></div><p>Finally, to adjust the deployment settings of the project you should switch on to + the tab that opens the Deployment mode. On the picture below the Deployment mode is + performed with default settings. Here, you can easily modify them or, if the + settings won't match your needs, to reset defaults. </p><div class="figure"><a name="d0e726"></a><div class="figure-contents"><div class="mediaobject"><img src="images/the_views/the_views10.png" alt="The Deployment Mode"></div></div><p class="title"><b>Figure 4.11. The Deployment Mode</b></p></div><br class="figure-break"><p>The button <span class="emphasis"><em> + <span class="property">Test Connections</span> + </em></span> is necessary to make sure whether all your settings are valid before + deploying the process.</p></div></div><p>Now that we've seen how to work with jPDL perspective, let's pass on to the project testing.</p></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Test_Drive_Proc_Development"></a>Chapter 5. Test Driven Process Development</h2></div></div></div><p> One of the most important advantages of JBoss jBPM's lightweight approach to BPM + and workflow management is that developers can easily leverage their usual programming + skills and techniques. One of these well-known techniques is Unit Testing and Test Driven + Development. </p><p>In this chapter we will show how developers, making use of the JBoss jBPM GPD, can use a + technique we have baptized <span class="property">Test Driven Process Development</span> to create + process definitions and test their correctness. </p><p> When creating the <span class="emphasis"><em> + <span class="property">HellojBPM</span> + </em></span> project the Project Creation wizard has already put in place all the library + requirements we need to start writing the jBPM unit tests. They are contained in the jBPM + Library container and the most important of them is the <span class="emphasis"><em> + <span class="property">.jar</span> + </em></span> file containing the core jBPM classes. While working on the project you could + find them all in the Package Explorer.</p><div class="figure"><a name="d0e777"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Test_Drive_Proc/test_driv_proc.png" alt="The jBPM Libraries"></div></div><p class="title"><b>Figure 5.1. The jBPM Libraries</b></p></div><br class="figure-break"><p>It must be noted that it is possible to change the location of the core jBPM installation + by changing the preference settings. More on this <a class="link" href="#change_core_jbpm_inst" title="7.1. Change the Default Core jBPM Installation">see + later</a> in this book.</p><p> With that extra knowledge on the project settings, you can create your first test. To do + this, we create the <span class="emphasis"><em> + <span class="property">com.jbay</span> + </em></span> package in the <span class="emphasis"><em> + <span class="property">test/java</span> + </em></span> source folder. Then we bring up the context menu on this package and select <span class="emphasis"><em> + <span class="property">New > Other...</span> + </em></span></p><div class="figure"><a name="d0e807"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Test_Drive_Proc/test_driv_proc_1a.png" alt="Call the JUnit Test Case Creation wizard"></div></div><p class="title"><b>Figure 5.2. Call the JUnit Test Case Creation wizard</b></p></div><br class="figure-break"><p> And then <span class="emphasis"><em> + <span class="property">Java > JUnit > JUnit Test Case</span> + </em></span> to call the specialized JUnite Test case creation wizard.</p><div class="figure"><a name="d0e821"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Test_Drive_Proc/test_driv_proc_1b.png" alt="Call the JUnit Test Case Creation wizard"></div></div><p class="title"><b>Figure 5.3. Call the JUnit Test Case Creation wizard</b></p></div><br class="figure-break"><p>The wizard looks as follows:</p><div class="figure"><a name="d0e829"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Test_Drive_Proc/test_driv_proc_2a.png" alt="Create Test Dialog"></div></div><p class="title"><b>Figure 5.4. Create Test Dialog</b></p></div><br class="figure-break"><p>By default JUnite 3 version of testing framework is selected. Of course, you can choose + new advanced JUnit 4 version. In this case you'll be prompted to add new JUnit + Library to your build path. To add it automatically just click on the appropriate link.</p><div class="figure"><a name="d0e837"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Test_Drive_Proc/test_driv_proc_2b.png" alt="A First Test Scenario"></div></div><p class="title"><b>Figure 5.5. A First Test Scenario</b></p></div><br class="figure-break"><p>Then, we call the test class <span class="emphasis"><em> + <span class="property">HelloTest</span> + </em></span> and press <span class="emphasis"><em> + <span class="property">Finish</span> + </em></span> button to complete.</p><p> Next, we should write a simple test scenario as shown on the next figure. Let's + study the code of this test case. </p><div class="figure"><a name="hello_test"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Test_Drive_Proc/test_driv_proc_3.png" alt="A First Test Scenario"></div></div><p class="title"><b>Figure 5.6. A First Test Scenario</b></p></div><br class="figure-break"><p>In the first line of the method, a jBPM process archive object is created. We use a + constructor accepting the filename of the archive. In our case it is the <span class="emphasis"><em> + <span class="property">hello</span> + </em></span> file we created earlier and which lives in the <span class="emphasis"><em> + <span class="property">src/main/jpdl</span> + </em></span> folder of our project. After asserting that this object is really created, we + extract a process definition object from it. This 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 <span class="emphasis"><em> + <span class="property">auction</span> + </em></span> state. Finally another signal will end the process. </p><p> After writing this test we can check whether it works as expected by running it .</p><div class="figure"><a name="d0e887"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Test_Drive_Proc/test_driv_proc_4.png" alt="Running the Process Test"></div></div><p class="title"><b>Figure 5.7. Running the Process Test</b></p></div><br class="figure-break"><p>All went well as we have a green light:</p><div class="figure"><a name="d0e895"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Test_Drive_Proc/test_driv_proc_5.png" alt="Successful Test Run"></div></div><p class="title"><b>Figure 5.8. Successful Test Run</b></p></div><br class="figure-break"><p> 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 <a class="ulink" href="http://docs.jboss.com/jbpm/v3/userguide/" target="_top">JBoss jBPM User Guide</a> and to + study the API reference. Moreover some more examples will be given later in this book.</p></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="The_JBoss_jBPM_Int_Mech"></a>Chapter 6. Actions : The JBoss jBPM Integration Mechanism</h2></div></div></div><p> In this chapter we will show how to do software integration with <span class="property">JBoss + jBPM</span>. The standard mechanism to implement this is to wrap the functionality you + want to integrate in a class that implements the <span class="emphasis"><em> + <span class="property">ActionHandler</span> + </em></span> interface. In order to demonstrate it let's specify Hello World action for our + process.</p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e931"></a>6.1. Creating a Hello World Action</h2></div></div></div><p>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 <span class="emphasis"><em> + <span class="property">ActionHandler</span> + </em></span> 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. </p><p> To make things a little bit more concrete, let's create a new class called <span class="emphasis"><em> + <span class="property">HelloActionHandler</span> + </em></span>. For that firstly we'll create a new package <span class="emphasis"><em> + <span class="property">com.jbay.action</span> + </em></span> in the <span class="emphasis"><em> + <span class="property">src/java/main</span> + </em></span> folder of our project. Then, we should call New Class Creation wizard as + usual by right-clicking and navigating <span class="emphasis"><em> + <span class="property">New > Class</span> + </em></span>. </p><div class="figure"><a name="d0e968"></a><div class="figure-contents"><div class="mediaobject"><img src="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_1.png" alt="Creating HelloActionHendler Class"></div></div><p class="title"><b>Figure 6.1. Creating HelloActionHendler Class</b></p></div><br class="figure-break"><p>Notice that two first gaps have been filled automatically. Here, instead of <span class="emphasis"><em> + <span class="property">Package</span> + </em></span> option <span class="emphasis"><em> + <span class="property">Enclose type</span> + </em></span> option can be selected where a type in which to enclose a new class should + be specified.</p><p>In our case, we leave everything as it is, just type <span class="emphasis"><em> + <span class="property">HelloActionHandler</span> + </em></span> as a name of new class and add <span class="emphasis"><em> + <span class="property">org.jbpm.graph.ActionHendler</span> + </em></span> interface as it's shown in the picture above.</p><p>Thus, our <span class="emphasis"><em> + <span class="property">HelloActionHandler</span> + </em></span> implements the <span class="emphasis"><em> + <span class="property">ActionHandler</span> + </em></span> interface including the <span class="emphasis"><em> + <span class="property">execute</span> + </em></span> method as shown in the next figure. Here, we add a variable named <span class="emphasis"><em> + <span class="property">greeting</span> + </em></span> to the collection of process variables and put a message in it : + <span class="emphasis"><em>"Hello from ActionHandler"</em></span>. </p><div class="figure"><a name="d0e1031"></a><div class="figure-contents"><div class="mediaobject"><img src="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_2.png" alt="A Simple Hello Action"></div></div><p class="title"><b>Figure 6.2. A Simple Hello Action</b></p></div><br class="figure-break"><p>Now, as we have <span class="emphasis"><em> + <span class="property">HelloActionHandler</span> + </em></span> class defined, let's explore how we can handle it.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e1045"></a>6.2. Integrating the Hello World Action</h2></div></div></div><p>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.</p><p> As good Testcity citizens we will first create a Unit Test that proves the behaviour + we want to achieve by adding the <span class="emphasis"><em> + <span class="property">ActionHandler</span> + </em></span> to the process. So we implement another test.</p><p>At first, let's return to the + code we already saw <a class="link" href="#hello_test" title="Figure 5.6. A First Test Scenario">in the previous chapter</a> and add new test method <span class="emphasis"><em> + <span class="property">testActionHendler</span></em></span> to it. </p><div class="figure"><a name="d0e1068"></a><div class="figure-contents"><div class="mediaobject"><img src="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_3.png" alt="Create the Hello Action Test"></div></div><p class="title"><b>Figure 6.3. Create the Hello Action Test</b></p></div><br class="figure-break"><p>We assert + that no variable called <span class="emphasis"><em> + <span class="property">greeting</span> + </em></span> 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 <span class="emphasis"><em> + <span class="property">greeting</span> + </em></span> variable should exist and contain the string "Hello from + ActionHandler". That's what we assert in the last lines of the test + method.</p><p> 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. </p><div class="figure"><a name="d0e1090"></a><div class="figure-contents"><div class="mediaobject"><img src="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_4.png" alt="Test Results Before Integration"></div></div><p class="title"><b>Figure 6.4. Test Results Before Integration</b></p></div><br class="figure-break"><p> 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.</p><div class="figure"><a name="d0e1098"></a><div class="figure-contents"><div class="mediaobject"><img src="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_5.png" alt="Adding an Action to a Transition"></div></div><p class="title"><b>Figure 6.5. Adding an Action to a Transition</b></p></div><br class="figure-break"><p>After adding the action a tabbed view with three pages will appear.</p><div class="figure"><a name="d0e1106"></a><div class="figure-contents"><div class="mediaobject"><img src="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_6.png" alt="Configuration Dialog for an Action"></div></div><p class="title"><b>Figure 6.6. Configuration Dialog for an Action</b></p></div><br class="figure-break"><p>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. </p><div class="figure"><a name="d0e1114"></a><div class="figure-contents"><div class="mediaobject"><img src="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_7.png" alt="The Details page of an Action Configuration Dialog"></div></div><p class="title"><b>Figure 6.7. The Details page of an Action Configuration Dialog</b></p></div><br class="figure-break"><p>Clicking on the <span class="emphasis"><em> + <span class="property">Search...</span> + </em></span> button brings us to a Choose Class dialog.</p><div class="figure"><a name="d0e1128"></a><div class="figure-contents"><div class="mediaobject"><img src="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_8.png" alt="The Choose Action Handler Dialog"></div></div><p class="title"><b>Figure 6.8. The Choose Action Handler Dialog</b></p></div><br class="figure-break"><p> We choose our previously created 'HelloActionHandler' class and + push the <span class="property">OK</span> button. After the selection of the action handler for + the action, we can run the test and observe it gives us a green light.</p><div class="figure"><a name="d0e1139"></a><div class="figure-contents"><div class="mediaobject"><img src="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_10.png" alt="Test Results"></div></div><p class="title"><b>Figure 6.9. Test Results</b></p></div><br class="figure-break"><p>Tere we are. The above objective has been achieved.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e1147"></a>6.3.  Integration Points</h2></div></div></div><p> The different integration points in a process definition are thoroughly documented in + the <a class="ulink" href="http://docs.jboss.com/jbpm/v3/userguide/" target="_top">JBoss jBPM User Guide</a>. 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. </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Quick_Howto_Guide"></a>Chapter 7. Quick Howto Guide</h2></div></div></div><p>This chapter contains additional information related to the <span class="property">JBoss + jBPM</span>.</p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="change_core_jbpm_inst"></a>7.1. Change the Default Core jBPM Installation</h2></div></div></div><p> You can change the default <span class="property">jBPM</span> installation by means of the + Eclipse preference mechanism. Open the Preferences dialog by selecting <span class="emphasis"><em> + <span class="property">Window > Preferences</span> + </em></span> and select the <span class="emphasis"><em> + <span class="property">JBoss jBPM > Runtime Location</span> + </em></span> category. Using this page you can add multiple <span class="property">jBPM</span> + 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 <span class="property">jBPM</span> + installation that's being referenced by a project however will cause the + classpath to contain errors. </p><div class="figure"><a name="d0e1200"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Quick_Howto_Guide/quick_howto_guide_1.png" alt="The jBPM Preferences Page"></div></div><p class="title"><b>Figure 7.1. The jBPM Preferences Page</b></p></div><br class="figure-break"></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e1206"></a>7.2. Configuring Task Nodes</h2></div></div></div><p>Here, we'll examine how you can configure the Task nodes in jBPM jPDL GPD.</p><p> 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 + Properties view for selected Task node includes several tabs. </p><div class="figure"><a name="d0e1213"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Quick_Howto_Guide/quick_howto_guide_2.png" alt="The Properties View of the selected Task Node"></div></div><p class="title"><b>Figure 7.2. The Properties View of the selected Task Node</b></p></div><br class="figure-break"><p>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.</p><div class="figure"><a name="d0e1221"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Quick_Howto_Guide/quick_howto_guide_3.png" alt="Adding a Task to the Task Node"></div></div><p class="title"><b>Figure 7.3. Adding a Task to the Task Node</b></p></div><br class="figure-break"><p>Every added Task has its own configuration possibilities. You can access them through + the Properties view as well.</p><div class="figure"><a name="d0e1229"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Quick_Howto_Guide/quick_howto_guide_4.png" alt="The Task properties"></div></div><p class="title"><b>Figure 7.4. The Task properties</b></p></div><br class="figure-break"><p>On the <span class="property">General</span> page is a place where you can specify the name of + a Task and its description. For instance, let it be <span class="emphasis"><em> + <span class="property">approve oder</span> + </em></span> with appropriate description that you can see in the figure below.</p><div class="figure"><a name="d0e1246"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Quick_Howto_Guide/quick_howto_guide_5.png" alt="The Task General Page"></div></div><p class="title"><b>Figure 7.5. The Task General Page</b></p></div><br class="figure-break"><p>Now, look at <span class="property">Details page</span>. 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 blocking attribute indicates that the process will not be + able to continue if this task is still unaccomplished. The <span class="emphasis"><em> + <span class="property">Generate Form...</span> + </em></span> button is for creating a simple task form that can be rendered by the jBPM + console.</p><div class="figure"><a name="d0e1263"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Quick_Howto_Guide/quick_howto_guide_6.png" alt="The Task Details Page"></div></div><p class="title"><b>Figure 7.6. The Task Details Page</b></p></div><br class="figure-break"><p>For our example, we specify the due date as 2 business days, choose the high priority + and also check the signalling and notifying 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 + <span class="property">Assignment</span> page.</p><div class="figure"><a name="d0e1274"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Quick_Howto_Guide/quick_howto_guide_7.png" alt="The Task Assignment Page"></div></div><p class="title"><b>Figure 7.7. The Task Assignment Page</b></p></div><br class="figure-break"><p>On the Reminder page you can specify whether the assignee will be reminded of the task + that awaits him.</p><div class="figure"><a name="d0e1282"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Quick_Howto_Guide/quick_howto_guide_8.png" alt="The Task Reminder Page"></div></div><p class="title"><b>Figure 7.8. The Task Reminder Page</b></p></div><br class="figure-break"><p>In our case, the assignee will be reminded by email after two business hours and continue + to get reminding every business hour after that.</p><p>In the next figure you can see our configuring generated into XML.</p><div class="figure"><a name="d0e1292"></a><div class="figure-contents"><div class="mediaobject"><img src="images/Quick_Howto_Guide/quick_howto_guide_9.png" alt="The Task Reminder Page"></div></div><p class="title"><b>Figure 7.9. The Task Reminder Page</b></p></div><br class="figure-break"></div></div></div></body></html> \ No newline at end of file Added: trunk/jbpm/docs/build/reference/en/html_single/script/toggle.js =================================================================== --- trunk/jbpm/docs/build/reference/en/html_single/script/toggle.js (rev 0) +++ trunk/jbpm/docs/build/reference/en/html_single/script/toggle.js 2007-12-28 11:34:08 UTC (rev 5465) @@ -0,0 +1,43 @@ +function dbToggle(node, expandText, collapseText) { + var dt = node.parentNode; + if (dt.nodeName.toLowerCase() == 'dt') { + var dd = dt.nextSibling; + + if (dd && dd.nodeName.toLowerCase() == 'dd') { + + if (dd.style && dd.style.display == 'none') { + dd.style.display = ''; + node.innerHTML = collapseText; + } else { + dd.style.display = 'none'; + node.innerHTML = expandText; + } + + } + + } + +} + +var toc = { + expand: function(node) { + toc.show(toc.findDD(node)) + toc.hide(node); + toc.show(node.nextSibling); + }, + collapse : function(node) { + toc.hide(toc.findDD(node)) + toc.hide(node); + toc.show(node.previousSibling); + }, + findDD : function(node) { + return node.parentNode.nextSibling; + }, + + hide: function(node) { + node.style.display = "none"; + }, + show: function(node) { + node.style.display = ""; + } +}; \ No newline at end of file Added: trunk/jbpm/docs/build/reference/en/pdf/jBPM_Tools_Ref.pdf =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/build/reference/en/pdf/jBPM_Tools_Ref.pdf ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Modified: trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_2.png =================================================================== (Binary files differ) Added: trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_3.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_4.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_4.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_5.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_5.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_6.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_6.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_7.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_7.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_8.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_8.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_9.png =================================================================== (Binary files differ) Property changes on: trunk/jbpm/docs/reference/en/images/Quick_Howto_Guide/quick_howto_guide_9.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Modified: trunk/jbpm/docs/reference/en/modules/Quick_Howto_Guide.xml =================================================================== --- trunk/jbpm/docs/reference/en/modules/Quick_Howto_Guide.xml 2007-12-28 09:38:35 UTC (rev 5464) +++ trunk/jbpm/docs/reference/en/modules/Quick_Howto_Guide.xml 2007-12-28 11:34:08 UTC (rev 5465) @@ -12,8 +12,9 @@ </chapterinfo> <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> @@ -45,13 +46,15 @@ <section> <title>Configuring Task Nodes</title> - <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 - <property>Properties</property> entry that opens a configuration dialog. </para> + <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 + Properties view for selected Task node includes several tabs. </para> + <figure> - <title> The Task Configuration Dialog</title> - + <title>The Properties View of the selected Task Node</title> <mediaobject> <imageobject> <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_2.png" @@ -59,6 +62,112 @@ </imageobject> </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> + + <figure> + <title>Adding a Task to the Task Node</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_3.png" + scalefit="1"/> + </imageobject> + </mediaobject> + </figure> + + <para>Every added Task has its own configuration possibilities. You can access them through + the Properties view as well.</para> + + <figure> + <title>The Task properties</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_4.png" + scalefit="1"/> + </imageobject> + </mediaobject> + </figure> + + <para>The <property>General</property> page 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> + <mediaobject> + <imageobject> + <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_5.png" + scalefit="1"/> + </imageobject> + </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> + + <figure> + <title>The Task Details Page</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_6.png" + scalefit="1"/> + </imageobject> + </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</property> page.</para> + + <figure> + <title>The Task Assignment Page</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_7.png" + scalefit="1"/> + </imageobject> + </mediaobject> + </figure> + + <para>On the Reminder page you can specify whether the assignee will be reminded of the task + that awaits him.</para> + + <figure> + <title>The Task Reminder Page</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_8.png" + scalefit="1"/> + </imageobject> + </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 the next figure you can see our configuring generated into XML.</para> + <figure> + <title>The Task Reminder Page</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_9.png" + scalefit="1"/> + </imageobject> + </mediaobject> + </figure> + </section> </chapter> Modified: trunk/jbpm/docs/reference/en/modules/Test_Drive_Proc.xml =================================================================== --- trunk/jbpm/docs/reference/en/modules/Test_Drive_Proc.xml 2007-12-28 09:38:35 UTC (rev 5464) +++ trunk/jbpm/docs/reference/en/modules/Test_Drive_Proc.xml 2007-12-28 11:34:08 UTC (rev 5465) @@ -89,7 +89,8 @@ <para>By default JUnite 3 version of testing framework is selected. Of course, you can choose new advanced JUnit 4 version. In this case you'll be prompted to add new JUnit - Library to your build path. To add it automatically just click on the appropriate link.</para> + 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> <figure> <title>A First Test Scenario</title> 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-12-28 09:38:35 UTC (rev 5464) +++ trunk/jbpm/docs/reference/en/modules/The_JBoss_jBPM_Int_Mech.xml 2007-12-28 11:34:08 UTC (rev 5465) @@ -73,7 +73,7 @@ <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 puts a message in it : + </emphasis> to the collection of process variables and put a message in it : <emphasis>"Hello from ActionHandler"</emphasis>. </para> <figure> Modified: trunk/jbpm/docs/reference/en/modules/jboss_jbpm_runtime_installation.xml =================================================================== --- trunk/jbpm/docs/reference/en/modules/jboss_jbpm_runtime_installation.xml 2007-12-28 09:38:35 UTC (rev 5464) +++ trunk/jbpm/docs/reference/en/modules/jboss_jbpm_runtime_installation.xml 2007-12-28 11:34:08 UTC (rev 5465) @@ -13,8 +13,7 @@ <title>JBoss jBPM Runtime Installation</title> <para>The main purpose of this chapter is to let you know how to launch the <property>JBoss jBPM</property> (business process management).</para> - <para>The jBPM plugin (jBPM Designer) is already included in the <property>JBoss Developer - Studio</property>. To make it work, you should only download the jBPM runtime (jbpm-jpdl-3.2.2 + <para>The jBPM plugin (jBPM Designer) is already included in the <property>JBoss Tools</property>. To make it work, you should only download the jBPM runtime (jbpm-jpdl-3.2.2 currently) from <ulink url="http://labs.jboss.com/jbossjbpm/downloads/">here</ulink> and specify the directory where you extracted the runtime either when you create a jBPM project or by using the jBPM preference pages.</para>

16 years, 12 months

1
0
0 / 0

JBoss Tools SVN: r5464 - trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor.

by jbosstools-commits＠lists.jboss.org

Author: mareshkau Date: 2007-12-28 04:38:35 -0500 (Fri, 28 Dec 2007) New Revision: 5464 Modified: trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/VpeSourceDomBuilder.java Log: http://jira.jboss.com/jira/browse/JBIDE-1569 Modified: trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/VpeSourceDomBuilder.java =================================================================== --- trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/VpeSourceDomBuilder.java 2007-12-27 16:33:45 UTC (rev 5463) +++ trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/VpeSourceDomBuilder.java 2007-12-28 09:38:35 UTC (rev 5464) @@ -315,7 +315,7 @@ //Added by Max Areshkau in scope of bug JBIDE-1209 } else if (sourceParent.getNodeType()==Node.TEXT_NODE) { - setSelection(sourceParent, 1, 0); + setSelection(sourceParent, offset, length); } } }

16 years, 12 months

1
0
0 / 0

JBoss Tools SVN: r5463 - trunk/jsf/tests/org.jboss.tools.jsf.test/src/org/jboss/tools/jsf/test.

by jbosstools-commits＠lists.jboss.org

Author: sdzmitrovich Date: 2007-12-27 11:33:45 -0500 (Thu, 27 Dec 2007) New Revision: 5463 Modified: trunk/jsf/tests/org.jboss.tools.jsf.test/src/org/jboss/tools/jsf/test/JSFImportTest.java Log: http://jira.jboss.com/jira/browse/JBIDE-1563 Modified: trunk/jsf/tests/org.jboss.tools.jsf.test/src/org/jboss/tools/jsf/test/JSFImportTest.java =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.test/src/org/jboss/tools/jsf/test/JSFImportTest.java 2007-12-27 16:27:57 UTC (rev 5462) +++ trunk/jsf/tests/org.jboss.tools.jsf.test/src/org/jboss/tools/jsf/test/JSFImportTest.java 2007-12-27 16:33:45 UTC (rev 5463) @@ -36,7 +36,7 @@ context.setWebXmlLocation(webxml.getAbsolutePath()); context.setProjectName(projectLocation.getName()); context.setApplicationName(projectLocation.getName()); - context.setLinkingToProjectOutsideWorkspace(false); + //context.setLinkingToProjectOutsideWorkspace(false); JSFProjectAdoptOperation operation = new JSFProjectAdoptOperation(context);

16 years, 12 months

1
0
0 / 0

JBoss Tools SVN: r5462 - in trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test: META-INF and 9 other directories.

by jbosstools-commits＠lists.jboss.org

Author: sdzmitrovich Date: 2007-12-27 11:27:57 -0500 (Thu, 27 Dec 2007) New Revision: 5462 Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/.classpath trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/.project trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/META-INF/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/META-INF/MANIFEST.MF trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/build.properties trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/jsfTest.jar trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/ImportJsfComponents.java trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfComponentTest.java trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfTestPlugin.java Log: http://jira.jboss.com/jira/browse/JBIDE-1563 Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/.classpath =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/.classpath (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/.classpath 2007-12-27 16:27:57 UTC (rev 5462) @@ -0,0 +1,7 @@ +<?xml version="1.0" encoding="UTF-8"?> +<classpath> + <classpathentry kind="src" path="src"/> + <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/> + <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/> + <classpathentry kind="output" path="bin"/> +</classpath> Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/.project =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/.project (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/.project 2007-12-27 16:27:57 UTC (rev 5462) @@ -0,0 +1,28 @@ +<?xml version="1.0" encoding="UTF-8"?> +<projectDescription> + <name>org.jboss.tools.jsf.vpe.jsf.test</name> + <comment></comment> + <projects> + </projects> + <buildSpec> + <buildCommand> + <name>org.eclipse.jdt.core.javabuilder</name> + <arguments> + </arguments> + </buildCommand> + <buildCommand> + <name>org.eclipse.pde.ManifestBuilder</name> + <arguments> + </arguments> + </buildCommand> + <buildCommand> + <name>org.eclipse.pde.SchemaBuilder</name> + <arguments> + </arguments> + </buildCommand> + </buildSpec> + <natures> + <nature>org.eclipse.pde.PluginNature</nature> + <nature>org.eclipse.jdt.core.javanature</nature> + </natures> +</projectDescription> Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/META-INF/MANIFEST.MF =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/META-INF/MANIFEST.MF (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/META-INF/MANIFEST.MF 2007-12-27 16:27:57 UTC (rev 5462) @@ -0,0 +1,15 @@ +Manifest-Version: 1.0 +Bundle-ManifestVersion: 2 +Bundle-Name: Jsf Test Plug-in +Bundle-SymbolicName: org.jboss.tools.jsf.vpe.jsf.test +Bundle-Version: 1.0.0 +Bundle-Activator: org.jboss.tools.jsf.vpe.jsf.test.JsfTestPlugin +Require-Bundle: org.eclipse.ui, + org.eclipse.core.runtime, + org.jboss.tools.vpe, + org.junit, + org.eclipse.core.resources, + org.eclipse.ui.ide, + org.jboss.tools.common +Eclipse-LazyStart: true +Bundle-ClassPath: jsf-test.jar Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/build.properties =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/build.properties (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/build.properties 2007-12-27 16:27:57 UTC (rev 5462) @@ -0,0 +1,10 @@ +bin.includes = META-INF/,\ + jsf-test.jar,\ + resources/ +jars.compile.order = jsf-test.jar +source.jsf-test.jar = src/ +output.jsf-test.jar = bin/ +src.includes = META-INF/,\ + build.properties,\ + resources/,\ + src/ Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/jsfTest.jar =================================================================== (Binary files differ) Property changes on: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/jsfTest.jar ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/ImportJsfComponents.java =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/ImportJsfComponents.java (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/ImportJsfComponents.java 2007-12-27 16:27:57 UTC (rev 5462) @@ -0,0 +1,105 @@ +/******************************************************************************* + * Copyright (c) 2007 Exadel, Inc. and Red Hat, Inc. + * Distributed under license by Red Hat, Inc. All rights reserved. + * This program is made available under the terms of the + * Eclipse Public License v1.0 which accompanies this distribution, + * and is available at http://www.eclipse.org/legal/epl-v10.html + * + * Contributors: + * Exadel, Inc. and Red Hat, Inc. - initial API and implementation + ******************************************************************************/ +package org.jboss.tools.jsf.vpe.jsf.test; + +import java.io.IOException; +import java.lang.reflect.InvocationTargetException; +import java.util.zip.ZipFile; + +import org.eclipse.core.resources.IProject; +import org.eclipse.core.resources.IResource; +import org.eclipse.core.resources.ResourcesPlugin; +import org.eclipse.core.runtime.CoreException; +import org.eclipse.core.runtime.IPath; +import org.eclipse.core.runtime.NullProgressMonitor; +import org.eclipse.ui.PlatformUI; +import org.eclipse.ui.dialogs.IOverwriteQuery; +import org.eclipse.ui.internal.wizards.datatransfer.ZipLeveledStructureProvider; +import org.eclipse.ui.wizards.datatransfer.ImportOperation; + +/** + * Class for importing project from jar file + * + * @author dsakharov@exadel.com,amakhtadui(a)exadel.com + * + */ +public class ImportJsfComponents { + private static final String PROJECT_NAME = "JsfTest"; // $NON-NLS-1$ + private static final String COMPONENTS_PATH = "WebContent/pages"; // $NON-NLS-1$ + + @SuppressWarnings("restriction") + static void importJsfPages(String path) { + IProject project = ResourcesPlugin.getWorkspace().getRoot().getProject(PROJECT_NAME); + ZipLeveledStructureProvider zipStructureProvider; + try { + zipStructureProvider = + new ZipLeveledStructureProvider(new ZipFile(path)); + + IOverwriteQuery overwrite = new IOverwriteQuery() { + public String queryOverwrite(String pathString) { + return ALL; + } + }; + + ImportOperation importOp = new ImportOperation( + project.getFullPath(), + zipStructureProvider.getRoot(), + zipStructureProvider, + overwrite); + + importOp.setContext(PlatformUI.getWorkbench().getActiveWorkbenchWindow().getShell()); + + importOp.run(new NullProgressMonitor()); + } catch (InvocationTargetException ite) { + JsfTestPlugin.getPluginLog().logError(ite.getCause()); + } catch (InterruptedException ie) { + JsfTestPlugin.getPluginLog().logError(ie); + } catch (IOException e) { + JsfTestPlugin.getPluginLog().logError(e); + } + } + + /** + * + * @return + * @throws CoreException + */ + static IPath getComponentPath(String componentPage) throws CoreException { + IProject project = ResourcesPlugin.getWorkspace().getRoot().getProject(PROJECT_NAME); + if (project != null) { + IResource resource = project.getFolder(COMPONENTS_PATH).findMember(componentPage); + if (resource != null) { + return resource.getFullPath(); + } +// IResource[] resources = folder.members(); +// if (resources != null && resources.length > 0) { +// result = new ArrayList<IPath>(resources.length); +// for (IResource res : resources) { +// result.add(res.getFullPath()); +// } +// } + } + + return null; + } + + /** + * + * @throws CoreException + */ + static void removeProject() throws CoreException { + IProject project = ResourcesPlugin.getWorkspace().getRoot().getProject(PROJECT_NAME); + if (project != null) { + project.delete(IResource.ALWAYS_DELETE_PROJECT_CONTENT, + new NullProgressMonitor()); + } + } +} Property changes on: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/ImportJsfComponents.java ___________________________________________________________________ Name: svn:executable + * Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java 2007-12-27 16:27:57 UTC (rev 5462) @@ -0,0 +1,34 @@ +/******************************************************************************* + * Copyright (c) 2007 Exadel, Inc. and Red Hat, Inc. + * Distributed under license by Red Hat, Inc. All rights reserved. + * This program is made available under the terms of the + * Eclipse Public License v1.0 which accompanies this distribution, + * and is available at http://www.eclipse.org/legal/epl-v10.html + * + * Contributors: + * Exadel, Inc. and Red Hat, Inc. - initial API and implementation + ******************************************************************************/ +package org.jboss.tools.jsf.vpe.jsf.test; + +import junit.framework.Test; +import junit.framework.TestSuite; + +/** + * Class for testing all RichFaces components + * + * @author sdzmitrovich + * + */ + +public class JsfAllTests { + + public static Test suite() { + TestSuite suite = new TestSuite("Tests for Vpe Jsf components"); // $NON-NLS-1$ + // $JUnit-BEGIN$ + suite.addTestSuite(JsfComponentTest.class); + // $JUnit-END$ + return suite; + + } + +} Property changes on: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java ___________________________________________________________________ Name: svn:executable + * Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfComponentTest.java =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfComponentTest.java (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfComponentTest.java 2007-12-27 16:27:57 UTC (rev 5462) @@ -0,0 +1,261 @@ +/******************************************************************************* + * Copyright (c) 2007 Exadel, Inc. and Red Hat, Inc. + * Distributed under license by Red Hat, Inc. All rights reserved. + * This program is made available under the terms of the + * Eclipse Public License v1.0 which accompanies this distribution, + * and is available at http://www.eclipse.org/legal/epl-v10.html + * + * Contributors: + * Exadel, Inc. and Red Hat, Inc. - initial API and implementation + ******************************************************************************/ +package org.jboss.tools.jsf.vpe.jsf.test; + +import junit.framework.TestCase; + +import org.eclipse.core.resources.IFile; +import org.eclipse.core.resources.ResourcesPlugin; +import org.eclipse.core.runtime.ILogListener; +import org.eclipse.core.runtime.IPath; +import org.eclipse.core.runtime.IStatus; +import org.eclipse.core.runtime.Platform; +import org.eclipse.core.runtime.jobs.Job; +import org.eclipse.swt.widgets.Display; +import org.eclipse.ui.IEditorInput; +import org.eclipse.ui.PartInitException; +import org.eclipse.ui.PlatformUI; +import org.eclipse.ui.part.FileEditorInput; + +/** + * Class for testing all jsf components + * + * @author sdzmitrovich + * + */ +public class JsfComponentTest extends TestCase implements ILogListener { + + private final static String EDITOR_ID = "org.jboss.tools.jst.jsp.jspeditor.JSPTextEditor"; // $NON-NLS-1$ + private final static String TEST_PROJECT_JAR_PATH = "/jsfTest.jar"; // $NON-NLS-1$ + + // check warning log + private final static boolean checkWarning = false; + private Throwable exception; + + public JsfComponentTest(String name) { + super(name); + } + + /** + * Perform pre-test initialization. + * + * @throws Exception + * + * @see TestCase#setUp() + */ + protected void setUp() throws Exception { + super.setUp(); + + // TODO: Use TestSetup to create and remove project once for all tests + // not for every one + if (ResourcesPlugin.getWorkspace().getRoot().findMember("JsfTest") == null) { + + ImportJsfComponents.importJsfPages(JsfTestPlugin + .getPluginResourcePath() + + TEST_PROJECT_JAR_PATH); + + waitForJobs(); + waitForJobs(); + delay(5000); + } + Platform.addLogListener(this); + } + + /** + * Perform post-test cleanup. + * + * @throws Exception + * + * @see TestCase#tearDown() + */ + protected void tearDown() throws Exception { + super.tearDown(); + // ImportRichFacesComponents.removeProject(); + // waitForJobs(); + Platform.removeLogListener(this); + } + + /** + * Process UI input but do not return for the specified time interval. + * + * @param waitTimeMillis + * the number of milliseconds + */ + private void delay(long waitTimeMillis) { + Display display = Display.getCurrent(); + if (display != null) { + long endTimeMillis = System.currentTimeMillis() + waitTimeMillis; + while (System.currentTimeMillis() < endTimeMillis) { + if (!display.readAndDispatch()) + display.sleep(); + } + display.update(); + } + // Otherwise, perform a simple sleep. + else { + try { + Thread.sleep(waitTimeMillis); + } catch (InterruptedException e) { + // Ignored. + } + } + } + + /** + * Wait until all background tasks are complete. + */ + public void waitForJobs() { + while (Job.getJobManager().currentJob() != null) + delay(5000); + } + + // public void testAllComponentsOnSinglePage() throws PartInitException, + // Throwable { + // performTestForRichFacesComponent("richFacesTest.xhtml"); // $NON-NLS-1$ + // } + + public void testCommandButton() throws PartInitException, Throwable { + performTestForJsfComponent("commandButton.jsp"); // $NON-NLS-1$ + } + + public void testCommandLink() throws PartInitException, Throwable { + performTestForJsfComponent("commandLink.jsp"); // $NON-NLS-1$ + } + + public void testDataTable() throws PartInitException, Throwable { + performTestForJsfComponent("dataTable.jsp"); // $NON-NLS-1$ + } + + public void testForm() throws PartInitException, Throwable { + performTestForJsfComponent("form.jsp"); // $NON-NLS-1$ + } + + public void testGraphicImage() throws PartInitException, Throwable { + performTestForJsfComponent("graphicImage.jsp"); // $NON-NLS-1$ + } + + public void testInputHidden() throws PartInitException, Throwable { + performTestForJsfComponent("inputHidden.jsp"); // $NON-NLS-1$ + } + + public void testInputSecret() throws PartInitException, Throwable { + performTestForJsfComponent("inputSecret.jsp"); // $NON-NLS-1$ + } + + public void testInputText() throws PartInitException, Throwable { + performTestForJsfComponent("inputText.jsp"); // $NON-NLS-1$ + } + + public void testInputTextArea() throws PartInitException, Throwable { + performTestForJsfComponent("inputTextArea.jsp"); // $NON-NLS-1$ + } + + public void testMessage() throws PartInitException, Throwable { + performTestForJsfComponent("message.jsp"); // $NON-NLS-1$ + } + + public void testMessages() throws PartInitException, Throwable { + performTestForJsfComponent("messages.jsp"); // $NON-NLS-1$ + } + + public void testOutputFormat() throws PartInitException, Throwable { + performTestForJsfComponent("outputFormat.jsp"); // $NON-NLS-1$ + } + + public void testOutputLabel() throws PartInitException, Throwable { + performTestForJsfComponent("outputLabel.jsp"); // $NON-NLS-1$ + } + + public void testOutputLink() throws PartInitException, Throwable { + performTestForJsfComponent("outputLink.jsp"); // $NON-NLS-1$ + } + + public void testOutputText() throws PartInitException, Throwable { + performTestForJsfComponent("outputText.jsp"); // $NON-NLS-1$ + } + + public void testPanelGrid() throws PartInitException, Throwable { + performTestForJsfComponent("panelGrid.jsp"); // $NON-NLS-1$ + } + + public void testPanelGroup() throws PartInitException, Throwable { + performTestForJsfComponent("panelGroup.jsp"); // $NON-NLS-1$ + } + + public void testSelectBooleanCheckbox() throws PartInitException, Throwable { + performTestForJsfComponent("selectBooleanCheckbox.jsp"); // $NON-NLS-1$ + } + + public void testSelectManyCheckbox() throws PartInitException, Throwable { + performTestForJsfComponent("selectManyCheckbox.jsp"); // $NON-NLS-1$ + } + + public void testSelectManyListbox() throws PartInitException, Throwable { + performTestForJsfComponent("selectManyListbox.jsp"); // $NON-NLS-1$ + } + + public void testSelectManyMenu() throws PartInitException, Throwable { + performTestForJsfComponent("selectManyMenu.jsp"); // $NON-NLS-1$ + } + + public void testSelectOneListbox() throws PartInitException, Throwable { + performTestForJsfComponent("selectOneListbox.jsp"); // $NON-NLS-1$ + } + + public void testSelectOneMenu() throws PartInitException, Throwable { + performTestForJsfComponent("selectOneMenu.jsp"); // $NON-NLS-1$ + } + + public void testSelectOneRadio() throws PartInitException, Throwable { + performTestForJsfComponent("selectOneRadio.jsp"); // $NON-NLS-1$ + } + + private void performTestForJsfComponent(String componentPage) + throws PartInitException, Throwable { + waitForJobs(); + + exception = null; + IPath componentPath = ImportJsfComponents + .getComponentPath(componentPage); + + IFile file = ResourcesPlugin.getWorkspace().getRoot().getFile( + componentPath); + IEditorInput input = new FileEditorInput(file); + + PlatformUI.getWorkbench().getActiveWorkbenchWindow().getActivePage() + .openEditor(input, EDITOR_ID, true); + + waitForJobs(); + delay(3000); + PlatformUI.getWorkbench().getActiveWorkbenchWindow().getActivePage() + .closeAllEditors(true); + + if (exception != null) { + throw exception; + } + } + + public void logging(IStatus status, String plugin) { + switch (status.getSeverity()) { + case IStatus.ERROR: + exception = status.getException(); + break; + case IStatus.WARNING: + if (checkWarning) + exception = status.getException(); + break; + default: + break; + } + + } + +} Property changes on: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfComponentTest.java ___________________________________________________________________ Name: svn:executable + * Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfTestPlugin.java =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfTestPlugin.java (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfTestPlugin.java 2007-12-27 16:27:57 UTC (rev 5462) @@ -0,0 +1,74 @@ +package org.jboss.tools.jsf.vpe.jsf.test; + +import java.net.URL; + +import org.eclipse.core.runtime.FileLocator; +import org.eclipse.core.runtime.Platform; +import org.jboss.tools.common.log.BaseUIPlugin; +import org.jboss.tools.common.log.IPluginLog; +import org.osgi.framework.Bundle; +import org.osgi.framework.BundleContext; + +/** + * The activator class controls the plug-in life cycle + */ +public class JsfTestPlugin extends BaseUIPlugin { + + // The plug-in ID + public static final String PLUGIN_ID = "org.jboss.tools.jsf.vpe.jsf.test"; + + // The shared instance + private static JsfTestPlugin plugin; + + /** + * The constructor + */ + public JsfTestPlugin() { + } + + /* + * (non-Javadoc) + * + * @see org.eclipse.core.runtime.Plugins#start(org.osgi.framework.BundleContext) + */ + public void start(BundleContext context) throws Exception { + super.start(context); + plugin = this; + } + + /* + * (non-Javadoc) + * + * @see org.eclipse.core.runtime.Plugin#stop(org.osgi.framework.BundleContext) + */ + public void stop(BundleContext context) throws Exception { + plugin = null; + super.stop(context); + } + + /** + * Returns the shared instance + * + * @return the shared instance + */ + public static JsfTestPlugin getDefault() { + return plugin; + } + + public static IPluginLog getPluginLog() { + return getDefault(); + } + + public static String getPluginResourcePath() { + Bundle bundle = Platform.getBundle(PLUGIN_ID); + URL url = null; + try { + url = bundle == null ? null : FileLocator.resolve(bundle + .getEntry("/resources")); // $NON-NLS-1$ + } catch (Exception e) { + url = bundle.getEntry("/resources"); // $NON-NLS-1$ + } + return (url == null) ? null : url.getPath(); + } + +}

16 years, 12 months

1
0
0 / 0

JBoss Tools SVN: r5461 - trunk/jsf/tests.

by jbosstools-commits＠lists.jboss.org

Author: sdzmitrovich Date: 2007-12-27 11:27:11 -0500 (Thu, 27 Dec 2007) New Revision: 5461 Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/ Log: http://jira.jboss.com/jira/browse/JBIDE-1563

16 years, 12 months

1
0
0 / 0

JBoss Tools SVN: r5460 - trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/validation.

by jbosstools-commits＠lists.jboss.org

Author: akazakov Date: 2007-12-27 11:19:40 -0500 (Thu, 27 Dec 2007) New Revision: 5460 Modified: trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/validation/SeamCoreValidator.java Log: http://jira.jboss.com/jira/browse/JBIDE-1572 Fixed. JUnit test for this feature is already exists. Modified: trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/validation/SeamCoreValidator.java =================================================================== --- trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/validation/SeamCoreValidator.java 2007-12-27 14:41:20 UTC (rev 5459) +++ trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/validation/SeamCoreValidator.java 2007-12-27 16:19:40 UTC (rev 5460) @@ -281,32 +281,30 @@ boolean unknownVariable = true; boolean firstDuplicateVariableWasMarked = false; for (ISeamContextVariable variable : variables) { - if((factoryScope == variable.getScope() || factoryScope.getPriority()>variable.getScope().getPriority())) { - if(variable instanceof ISeamFactory || variable instanceof ISeamComponent || variable instanceof IRole) { - if(variable!=factory && !markedDuplicateFactoryNames.contains(factoryName)) { - // Duplicate factory name. Mark it. - // Save link to factory resource. - ISeamTextSourceReference location = null; - if(!firstDuplicateVariableWasMarked) { - firstDuplicateVariableWasMarked = true; - // mark original factory - validationContext.addLinkedCoreResource(factoryName, factory.getSourcePath()); - location = coreHelper.getLocationOfName(factory); - this.addError(DUPLICATE_VARIABLE_NAME_MESSAGE_ID, SeamPreferences.DUPLICATE_VARIABLE_NAME, new String[]{factoryName}, location, factory.getResource()); - } - // Mark duplicate variable. - if(!coreHelper.isJar(variable.getSourcePath())) { - IResource resource = coreHelper.getComponentResourceWithName(variable); - validationContext.addLinkedCoreResource(factoryName, resource.getFullPath()); - location = coreHelper.getLocationOfName(variable); - this.addError(DUPLICATE_VARIABLE_NAME_MESSAGE_ID, SeamPreferences.DUPLICATE_VARIABLE_NAME, new String[]{factoryName}, location, resource); - } -// markedDuplicateFactoryNames.add(factoryName); + if(variable instanceof ISeamFactory || variable instanceof ISeamComponent || variable instanceof IRole) { + if(variable!=factory && !markedDuplicateFactoryNames.contains(factoryName) && + (factoryScope == variable.getScope() || factoryScope.getPriority()>variable.getScope().getPriority())) { + // Duplicate factory name. Mark it. + // Save link to factory resource. + ISeamTextSourceReference location = null; + if(!firstDuplicateVariableWasMarked) { + firstDuplicateVariableWasMarked = true; + // mark original factory + validationContext.addLinkedCoreResource(factoryName, factory.getSourcePath()); + location = coreHelper.getLocationOfName(factory); + this.addError(DUPLICATE_VARIABLE_NAME_MESSAGE_ID, SeamPreferences.DUPLICATE_VARIABLE_NAME, new String[]{factoryName}, location, factory.getResource()); } - } else { - // We have that variable name - unknownVariable = false; + // Mark duplicate variable. + if(!coreHelper.isJar(variable.getSourcePath())) { + IResource resource = coreHelper.getComponentResourceWithName(variable); + validationContext.addLinkedCoreResource(factoryName, resource.getFullPath()); + location = coreHelper.getLocationOfName(variable); + this.addError(DUPLICATE_VARIABLE_NAME_MESSAGE_ID, SeamPreferences.DUPLICATE_VARIABLE_NAME, new String[]{factoryName}, location, resource); + } } + } else { + // We know that variable name + unknownVariable = false; } } if(firstDuplicateVariableWasMarked) {

16 years, 12 months

1
0
0 / 0

JBoss Tools SVN: r5459 - in trunk/as/docs/reference/en: images/runtimes_servers and 1 other directories.

by jbosstools-commits＠lists.jboss.org

Author: afedosik Date: 2007-12-27 09:41:20 -0500 (Thu, 27 Dec 2007) New Revision: 5459 Modified: trunk/as/docs/reference/en/images/perspective/perspective_3.png trunk/as/docs/reference/en/images/runtimes_servers/runtimes_servers_2.png trunk/as/docs/reference/en/modules/perspective.xml trunk/as/docs/reference/en/modules/runtimes_servers.xml Log: http://jira.jboss.com/jira/browse/JBDS-199 guide update according to remarks Modified: trunk/as/docs/reference/en/images/perspective/perspective_3.png =================================================================== (Binary files differ) Modified: trunk/as/docs/reference/en/images/runtimes_servers/runtimes_servers_2.png =================================================================== (Binary files differ) Modified: trunk/as/docs/reference/en/modules/perspective.xml =================================================================== --- trunk/as/docs/reference/en/modules/perspective.xml 2007-12-27 12:50:12 UTC (rev 5458) +++ trunk/as/docs/reference/en/modules/perspective.xml 2007-12-27 14:41:20 UTC (rev 5459) @@ -268,10 +268,60 @@ </imageobject> </mediaobject> </figure> - <para>The context menu on the items in the view is extendable, but there are several that come standard. The first is the <property>Build Archive</property> action, enabled - only on top-level archives, which initiates a full build on that archive. Editing and deleting nodes are also standard actions, with deletion not needing - an explanation. The edit action brings up the wizard associated with that particular node type and allows the details to be changed. The final action - contribution here is the ability to publish to a declared server.</para> + <para>The context menu on the items in the view is extendable, but there are several that come standard.</para> + + <table> + <title>Context Menu on the Item</title> + <tgroup cols="2"> + <colspec colnum="1" colwidth="1*"/> + <colspec colnum="2" colwidth="3*"/> + + + <thead> + <row> + <entry align="center"> + <para>Name</para> + </entry> + + <entry align="center"> + <para>Description</para> + </entry> + </row> + </thead> + + <tbody> + + <row> + <entry><para>Build Archive (Full)</para></entry> + + <entry><para>The action enabled only on top-level archives, which initiates a full build on that archive</para></entry> + </row> + + <row> + <entry><para>Edit Archive</para></entry> + + <entry><para>Standard action that brings up the wizard associated with that particular node type and allows the details to be changed</para></entry> + </row> + + <row> + <entry><para>Delete Archive</para></entry> + + <entry><para>Deleting node is standard action with deletion not needing an explanation</para></entry> + </row> + + <row> + <entry><para>Publish To Server</para></entry> + + <entry><para>The action means the ability to publish to a declared server</para></entry> + </row> + + </tbody> + </tgroup> + </table> + + + + </section> <section id="PublishToServer"> <title>Publish to Server</title> Modified: trunk/as/docs/reference/en/modules/runtimes_servers.xml =================================================================== --- trunk/as/docs/reference/en/modules/runtimes_servers.xml 2007-12-27 12:50:12 UTC (rev 5458) +++ trunk/as/docs/reference/en/modules/runtimes_servers.xml 2007-12-27 14:41:20 UTC (rev 5459) @@ -33,7 +33,7 @@ <listitem><para>For JBoss server at least, it provides information necessary for the starting and stopping of the server, it tells which jars to run and which configuration to use.</para></listitem> </itemizedlist> - <section><title>Installing a new Runtime</title> + <section id="InstNewRuntime"><title>Installing a new Runtime</title> <para>You can install runtimes into eclipse from the <emphasis><property>Window > Preferences... </property></emphasis> menu, and then select <emphasis><property>Server > Installed Runtimes</property></emphasis> from the categories available.</para> <figure> @@ -88,7 +88,7 @@ <section> <title>WTP Servers</title> - <para>WTP servers are eclipse-representations of a backing server installation. They are used to start or stop servers, deploy to servers, or debug code that will run on the server. They keep track of what modules (jars, wars, etc) + <para>WTP servers are eclipse-representations of a backing server installation. They are used to start or stop servers, deploy to servers, or debug code that will run on the server. They keep track of the modules (jars, wars, etc) you deploy to the server and also allow you to undeploy those modules. </para> <para>Servers can be started or stopped with different command-line arguments. They are often backed by a runtime object representing that server's location.</para> <section> @@ -108,8 +108,7 @@ <para>Because there may be many runtimes of each type declared, the wizard allows you to select which runtime you want your server to be backed by. The combo box below the view lets you select which declared runtime to use. For example, if there were already multiple JBoss 4.2 runtimes declared, the combo box would list all of the 4.2 runtimes available. </para> <para>If none of the runtimes declared are one you want to use, for example if you declared a default and a minimal runtime before but now want your server - to be backed by the ALL configuration, then you can click on the <emphasis><property>Installed Runtimes... </property></emphasis> button to bring up the preference page - shown at the beginning of this chapter. </para> + to be backed by the ALL configuration, then you can click on the <emphasis><property>Installed Runtimes... </property></emphasis> button to bring up the preference page shown at the beginning of this chapter.</para> <figure> <title>Installed Server Runtime Environments</title> <mediaobject>

16 years, 12 months

1
0
0 / 0

JBoss Tools SVN: r5458 - in trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core: validation and 1 other directory.

by jbosstools-commits＠lists.jboss.org

Author: akazakov Date: 2007-12-27 07:50:12 -0500 (Thu, 27 Dec 2007) New Revision: 5458 Modified: trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/AbstractContextVariable.java trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/Role.java trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/validation/SeamCoreValidator.java Log: http://jira.jboss.com/jira/browse/JBIDE-1570 Fixed. JUnit for this issue already exists. Modified: trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/AbstractContextVariable.java =================================================================== --- trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/AbstractContextVariable.java 2007-12-27 01:20:37 UTC (rev 5457) +++ trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/AbstractContextVariable.java 2007-12-27 12:50:12 UTC (rev 5458) @@ -27,6 +27,9 @@ protected String scope; public ScopeType getScope() { + if(scopeType == null) { + return ScopeType.UNSPECIFIED; + } return scopeType; } @@ -66,7 +69,7 @@ scope = f.scope; scopeType = f.scopeType; } - + return changes; } @@ -79,5 +82,4 @@ AbstractContextVariable c = (AbstractContextVariable)super.clone(); return c; } - -} +} \ No newline at end of file Modified: trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/Role.java =================================================================== --- trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/Role.java 2007-12-27 01:20:37 UTC (rev 5457) +++ trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/Role.java 2007-12-27 12:50:12 UTC (rev 5458) @@ -12,11 +12,40 @@ package org.jboss.tools.seam.internal.core; import org.jboss.tools.seam.core.IRole; +import org.jboss.tools.seam.core.ISeamContextVariable; +import org.jboss.tools.seam.core.ISeamElement; +import org.jboss.tools.seam.core.ISeamJavaComponentDeclaration; +import org.jboss.tools.seam.core.ScopeType; public class Role extends SeamJavaContextVariable implements IRole { + /* + * (non-Javadoc) + * @see org.jboss.tools.seam.internal.core.SeamJavaContextVariable#clone() + */ + @Override public Role clone() throws CloneNotSupportedException { return (Role)super.clone(); } -} + /* + * (non-Javadoc) + * @see org.jboss.tools.seam.internal.core.AbstractContextVariable#getScope() + */ + @Override + public ScopeType getScope() { + ScopeType returnScopeType = scopeType; + if(returnScopeType == null) { + ISeamElement parent = getParent(); + if(parent instanceof ISeamContextVariable) { + returnScopeType = ((ISeamContextVariable)parent).getScope(); + } else if(parent instanceof ISeamJavaComponentDeclaration) { + returnScopeType = ((ISeamJavaComponentDeclaration)parent).getScope(); + } + if(returnScopeType == null) { + returnScopeType = ScopeType.UNSPECIFIED; + } + } + return returnScopeType; + } +} \ No newline at end of file Modified: trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/validation/SeamCoreValidator.java =================================================================== --- trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/validation/SeamCoreValidator.java 2007-12-27 01:20:37 UTC (rev 5457) +++ trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/validation/SeamCoreValidator.java 2007-12-27 12:50:12 UTC (rev 5458) @@ -285,7 +285,7 @@ if(variable instanceof ISeamFactory || variable instanceof ISeamComponent || variable instanceof IRole) { if(variable!=factory && !markedDuplicateFactoryNames.contains(factoryName)) { // Duplicate factory name. Mark it. - // save link to factory resource + // Save link to factory resource. ISeamTextSourceReference location = null; if(!firstDuplicateVariableWasMarked) { firstDuplicateVariableWasMarked = true; @@ -294,14 +294,14 @@ location = coreHelper.getLocationOfName(factory); this.addError(DUPLICATE_VARIABLE_NAME_MESSAGE_ID, SeamPreferences.DUPLICATE_VARIABLE_NAME, new String[]{factoryName}, location, factory.getResource()); } - // mark duplicate variable + // Mark duplicate variable. if(!coreHelper.isJar(variable.getSourcePath())) { IResource resource = coreHelper.getComponentResourceWithName(variable); validationContext.addLinkedCoreResource(factoryName, resource.getFullPath()); location = coreHelper.getLocationOfName(variable); this.addError(DUPLICATE_VARIABLE_NAME_MESSAGE_ID, SeamPreferences.DUPLICATE_VARIABLE_NAME, new String[]{factoryName}, location, resource); } - markedDuplicateFactoryNames.add(factoryName); +// markedDuplicateFactoryNames.add(factoryName); } } else { // We have that variable name @@ -309,6 +309,9 @@ } } } + if(firstDuplicateVariableWasMarked) { + markedDuplicateFactoryNames.add(factoryName); + } if(unknownVariable && validateUnknownName) { // mark unknown factory name // save link to factory resource

16 years, 12 months

1
0
0 / 0

JBoss Tools SVN: r5457 - trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui.

by jbosstools-commits＠lists.jboss.org

Author: dgolovin Date: 2007-12-26 20:20:37 -0500 (Wed, 26 Dec 2007) New Revision: 5457 Modified: trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/messages.properties Log: http://jira.jboss.org/jira/browse/JBIDE-1543 Modified: trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/messages.properties =================================================================== --- trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/messages.properties 2007-12-26 18:05:16 UTC (rev 5456) +++ trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/messages.properties 2007-12-27 01:20:37 UTC (rev 5457) @@ -146,7 +146,7 @@ VALIDATOR_FACTORY_PRJ_NOT_SELECTED=Project is not selected VALIDATOR_FACTORY_IS_NOT_A_SEAM_WEB_PROJECT=' is not a Seam Web Project VALIDATOR_FACTORY_CONNECTION_PROFILE_IS_NOT_SELECTED=Connection profile is not selected -VALIDATOR_FACTORY_DRIVER_CLASS_PROPERTY_IS_EMPTY_FOR_SELECTED=Driver Class proberty is empty for selected ' +VALIDATOR_FACTORY_DRIVER_CLASS_PROPERTY_IS_EMPTY_FOR_SELECTED=Driver Class property is empty for selected ' VALIDATOR_FACTORY_SEAM_RT_SOURCE_TEMPLATES_DIR_DOES_NOT_EXIST=Seam Runtime ''{0}'' source templates directory doesn't exist for selected Seam Web Project VALIDATOR_FACTORY_CONNECTION_PROFILE=' connection profile VALIDATOR_FACTORY_SEAM_RUNTIME_IS_NOT_SELECTED=Seam Runtime is not selected

16 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbosstools-commits December 2007