August 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1379) Conditional Sequence Flow

by Thomas Diesler (JIRA)

Conditional Sequence Flow ------------------------- Key: JBPM-1379 URL: http://jira.jboss.com/jira/browse/JBPM-1379 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: API Reporter: Thomas Diesler -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-1334) Basic Node Sequence

by Thomas Diesler (JIRA)

Basic Node Sequence ------------------- Key: JBPM-1334 URL: http://jira.jboss.com/jira/browse/JBPM-1334 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: API Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: API 1.0.0.Alpha Support a basic node activity like this <process-definition> <start-state> <transition to='stateA' /> </start-state> <state name='stateA'> <event type='node-enter'> <action class='org.jboss.bpm.samples.activity.BasicActivity' /> </event> <transition to='end'/> </state> <end-state name='end' /> </process-definition> public class BasicActivity implements Activity { public void execute(Node node, Context ctx) { String name = node.getName(); ctx.addAttachment(String.class, "Activity on: " + name); } } /** * Test that the execution context variables set by the Activity * are visible to the client. */ public void testBasicActivity() throws Exception { // Create a ProcessDefinition through the ProcessDefinitionManager ProcessDefinitionManager pdm = ProcessDefinitionManager.locateProcessDefinitionManager(); ProcessDefinition pd = pdm.createProcessDefinition(jpdl); // Create an Execution through the ProcessDefinition Execution ex = pd.createExecution(); assertEquals(pd.getStartNode(), ex.getNode()); // Signal the execution ex.signal(); assertEquals(pd.findNode("stateA"), ex.getNode()); // Verify context variables String msg = ex.getContext().getAttachment(String.class); assertEquals("Activity on: stateA", msg); // Signal the execution ex.signal(); assertEquals(pd.findNode("end"), ex.getNode()); } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
9
0 / 0

[JBoss JIRA] Created: (JBPM-1333) Basic Activity

by Thomas Diesler (JIRA)

Basic Activity -------------- Key: JBPM-1333 URL: http://jira.jboss.com/jira/browse/JBPM-1333 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: API Reporter: Thomas Diesler Assigned To: Heiko Braun Fix For: API 1.0.0.Alpha Support prepareForShutdown and cancelShutdown on the ProcessEngine. /** * Try to create a Execution during shutdown */ public void testCreateExecution() throws Exception { // Create a ProcessDefinition through the ProcessDefinitionManager ProcessDefinitionManager pdm = ProcessDefinitionManager.locateProcessDefinitionManager(); ProcessDefinition pd = pdm.createProcessDefinition(jpdl); assertNotNull("Execution expected", pd.createExecution()); // Try to create a Execution during shutdown try { ProcessInstance pinst = pd.createProcessInstance(); engine.prepareForShutdown(); pinst.createExecution(); } catch (EngineShutdownException ex) { assertEquals("Cannot create new Execution while engine is shutting down", ex.getMessage()); } } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
9
0 / 0

[JBoss JIRA] Created: (JBPM-1689) Update '8.2. Database upgrades' section of JBPM Users Guide

by Taro Yasuma (JIRA)

Update '8.2. Database upgrades' section of JBPM Users Guide ----------------------------------------------------------- Key: JBPM-1689 URL: https://jira.jboss.org/jira/browse/JBPM-1689 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: jPDL 3.2.3 Reporter: Taro Yasuma '8.2. Database upgrades' section of JBPM Users Guide[1] is out-dated because it explains about using upgrade.scripts. But when you upgrade from jBPM v3.1.x to v3.2.x, you need to follow a section about upgrading database schema in JBPM_3.2.x_x.zip/jbpm-jpdl-3.2.x/release.notes.html instead of [1]. [1] http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.2.2/html-single/JBP... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (JBPM-1181) document 'end-complete-process' attribute on end-state

by Ronald van Kuijk (JIRA)

document 'end-complete-process' attribute on end-state ------------------------------------------------------ Key: JBPM-1181 URL: http://jira.jboss.com/jira/browse/JBPM-1181 Project: JBoss jBPM Issue Type: Task Reporter: Ronald van Kuijk Assigned To: Tom Baeyens Using an end-state in a leg of fork does not end the process. It ends the token (and parent tokens if it was the last active child). If one really wants to end the full process, the end-complete-process attribute should be used on the end-state. This is not documented anywhere, but it should. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

4
7
0 / 0

[JBoss JIRA] Created: (JBPM-1294) Integrate console tests in automated testrun

by Thomas Diesler (JIRA)

Integrate console tests in automated testrun -------------------------------------------- Key: JBPM-1294 URL: http://jira.jboss.com/jira/browse/JBPM-1294 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jBPM jPDL 3.2.4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

3
11
0 / 0

[JBoss JIRA] Created: (JBPM-1297) Integrate all tests in automated QA

by Thomas Diesler (JIRA)

Integrate all tests in automated QA ----------------------------------- Key: JBPM-1297 URL: http://jira.jboss.com/jira/browse/JBPM-1297 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: jPDL 3 Reporter: Thomas Diesler Fix For: jBPM jPDL 3.2.4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
9
0 / 0

[JBoss JIRA] Created: (JBPM-1205) Cleanup stale tests from the testsuite

by Thomas Diesler (JIRA)

Cleanup stale tests from the testsuite -------------------------------------- Key: JBPM-1205 URL: http://jira.jboss.com/jira/browse/JBPM-1205 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: jPDL 3 Reporter: Thomas Diesler I believe this is currently the list of tests that are not run as part of the testsuite  <exclude>org/jbpm/context/exe/VariableQueryDbTest.java</exclude> <exclude>org/jbpm/db/ContextSessionDbTest.java</exclude> <exclude>org/jbpm/DefaultConfigurationTest.java</exclude> <exclude>org/jbpm/graph/def/ExceptionHandlerDbTest.java</exclude> <exclude>org/jbpm/graph/def/TransitionDbTest.java</exclude> <exclude>org/jbpm/graph/exe/StateDbTest.java</exclude> <exclude>org/jbpm/graph/exe/SubProcessCancellationTest.java</exclude> <exclude>org/jbpm/graph/exe/SuperStateActionExecutionDbTest.java</exclude> <exclude>org/jbpm/graph/log/NodeLogTest.java</exclude> <exclude>org/jbpm/instantiation/UserCodeInterceptorTest.java</exclude> <exclude>org/jbpm/JbpmDefaultConfigTest.java</exclude> <exclude>org/jbpm/job/executor/ConcurrencyTest.java</exclude> <exclude>org/jbpm/job/executor/JobExecutorDbTest.java</exclude> <exclude>org/jbpm/job/executor/JobLoadJoinTest.java</exclude> <exclude>org/jbpm/job/executor/JobLoadSubProcessTest.java</exclude> <exclude>org/jbpm/jpdl/convert/ConversionTestCase.java</exclude> <exclude>org/jbpm/jpdl/xml/SchemaTest.java</exclude> <exclude>org/jbpm/logging/exe/LoggingConfigDbTest.java</exclude> <exclude>org/jbpm/logging/exe/LogLogTest.java</exclude> <exclude>org/jbpm/mail/RealServerMailTestCase.java</exclude> <exclude>org/jbpm/mock/JdbcProxyTest.java</exclude> <exclude>org/jbpm/perf/PerfWithoutDbTest.java</exclude> <exclude>org/jbpm/perf/StateUpdateTest.java</exclude> <exclude>org/jbpm/perf/TasklistEagerLoadingTest.java</exclude> <exclude>org/jbpm/perf/TaskWithVariablesTest.java</exclude> <exclude>org/jbpm/persistence/db/PersistenceConfigurationTest.java</exclude> <exclude>org/jbpm/scheduler/exe/UnsafeSessionUsageTest.java</exclude> <exclude>org/jbpm/seam/SeamPageFlowTest.java</exclude> To cleanup, do one of the following #1 enable the test #2 remove the test from SVN #3 disable the test with a FIXME #4 put the test in the exclude file void testFoo() { if(true) { System.out.println("FIXME: [JBPM-1234] some issue that needs fixing"); return; } } The union of tests in the exclude file and FIXME disabled tests are the errata for a given release. Do not silently disable/exclude a test. There must be a jira associated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
17
0 / 0

[JBoss JIRA] Created: (JBPM-1419) decide on use of BooleanArray

by Tom Baeyens (JIRA)

decide on use of BooleanArray ----------------------------- Key: JBPM-1419 URL: https://jira.jboss.org/jira/browse/JBPM-1419 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: PVM Reporter: Tom Baeyens are we going to combine multiple boolean fields into one column ? should BooleanArray (+test) be kept or should we remove it ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-1355) Add integration with supported target containers

by Thomas Diesler (JIRA)

Add integration with supported target containers ------------------------------------------------ Key: JBPM-1355 URL: http://jira.jboss.com/jira/browse/JBPM-1355 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: jPDL 3 Reporter: Thomas Diesler Fix For: jPDL 3.2.4 Generally, a new version of jBPM comes out approximately every eight weeks and integrates with the last three JBoss Application Server releases http://jbpm.dyndns.org/jbpmwiki/index.php?title=JBPM3-SupportedTargetCont... The container matrix needs to be covered by Hudson and thirdparty dependencies need to be aligned with the target container -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues August 2008