November 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1812) Fix tests that don't cleanup the database

by Thomas Diesler (JIRA)

Fix tests that don't cleanup the database ----------------------------------------- Key: JBPM-1812 URL: https://jira.jboss.org/jira/browse/JBPM-1812 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Core Engine Reporter: Thomas Diesler Fix For: jBPM 3.3.1 GA if ((count == null) || (count != 0)) { hasLeftOvers = true; //System.err.println("FIXME: " + getClass().getName() + "." + getName() + " left " + count + " records in " + tableName); } -- 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

2
12
0 / 0

[JBoss JIRA] Created: (JBPM-1796) Add process variable view

by Heiko Braun (JIRA)

Add process variable view ------------------------- Key: JBPM-1796 URL: https://jira.jboss.org/jira/browse/JBPM-1796 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: GWT Console 1.0.0 CR1 -- 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

1
5
0 / 0

[JBoss JIRA] Created: (JBPM-1836) View process variables

by Heiko Braun (JIRA)

View process variables ---------------------- Key: JBPM-1836 URL: https://jira.jboss.org/jira/browse/JBPM-1836 Project: JBoss jBPM Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: GWT Console 1.0.0 CR1 -- 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

1
3
0 / 0

[JBoss JIRA] Created: (JBPM-1459) getDefaultTransition

by Tom Baeyens (JIRA)

getDefaultTransition -------------------- Key: JBPM-1459 URL: https://jira.jboss.org/jira/browse/JBPM-1459 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens shouldn't that be called Node.getDefaultOutgoingTransition() ? ...given that the rest of the transition methods all have incoming or outgoing. WDYT ? -- 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

2
6
0 / 0

[JBoss JIRA] Created: (JBPM-1236) fix for undescriptive NullPointerException when jbpm4jsf-config.xml is missing

by Gergely Nagy (JIRA)

fix for undescriptive NullPointerException when jbpm4jsf-config.xml is missing ------------------------------------------------------------------------------ Key: JBPM-1236 URL: http://jira.jboss.com/jira/browse/JBPM-1236 Project: JBoss jBPM Issue Type: Patch Security Level: Public (Everyone can see) Components: Web Interface Reporter: Gergely Nagy An undescriptive error page is shown when jbpm4jsf-config.xml is missing: simple error 500 page with no indication to the cause of the error. I could only track this down by debugging jbpm4jsf, and it took me a while to figure this out. The attached patch includes a check for null, and a descriptive error message. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBPM-1892) Define a meaningful TaskService to be implemented by BPM engines

by Thomas Diesler (JIRA)

Define a meaningful TaskService to be implemented by BPM engines ---------------------------------------------------------------- Key: JBPM-1892 URL: https://jira.jboss.org/jira/browse/JBPM-1892 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Console, Task Reporter: Thomas Diesler Assignee: Heiko Braun Fix For: GWT Console 1.0.0 GA -- 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

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-1185) Node, State and ProcessState don't support Conditions on Transitions

by Britt Miner (JIRA)

Node, State and ProcessState don't support Conditions on Transitions -------------------------------------------------------------------- Key: JBPM-1185 URL: http://jira.jboss.com/jira/browse/JBPM-1185 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Britt Miner Assigned To: Tom Baeyens Node, State, and ProcessState don't provide any preliminary check for conditions provided on transitions. No check is performed until the transition is signaled, at which point the process will barf if a condition is present on the default transition, and that condition evaluates to false. Regardless if a person "should" be using transition conditions in Node or State, the schema allows it, the documentation doesn't forbid it, and the current behavior of a Transition element in the jpdl is inconsistent. The fix to make everything consistent is fairly simple--only org.jbpm.graph.def.Node needs to really be altered (and a one-liner in ProcessState): In org.jbpm.graph.def.Node, add the following method: // BRITT-- public Transition calculateLeavingTransition(ExecutionContext executionContext) { Transition transition = null; boolean hasTransitioned = false; Iterator iter = leavingTransitions.iterator(); while (iter.hasNext()) { Transition candidate = (Transition) iter.next(); String conditionExpression = candidate.getCondition(); if (conditionExpression != null) { Object result = JbpmExpressionEvaluator.evaluate(conditionExpression, executionContext); if (Boolean.TRUE.equals(result)) { transition = candidate; } } else { transition = candidate; } } if (!hasTransitioned) { this.getDefaultLeavingTransition().removeConditionEnforcement(); log.warn("All transition conditions have evaluated to 'false'. Taking the default transition."); transition = this.getDefaultLeavingTransition(); } return transition; } // --BRITT ...and modify "leave(ExecutionContext executionContext)": // BRITT --replace the following line with the code below // to check conditions before selecting the transition to take... //leave(executionContext, getDefaultLeavingTransition()); //original line leave(executionContext, calculateLeavingTransition(executionContext)); // --BRITT For consistency, ProcessState should also have one line modified at the very end of it's "leave(ExecutionContext, Transition)" method: // BRITT-- rather than specify which transition, let the super class decide... //super.leave(executionContext, getDefaultLeavingTransition()); super.leave(executionContext, calculateLeavingTransition(executionContext)); // --BRITT -- 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, 9 months

5
11
0 / 0

[JBoss JIRA] Created: (JBPM-1471) Do not signal ENDED super process token when ending process instance

by Pavel Kadlec (JIRA)

Do not signal ENDED super process token when ending process instance -------------------------------------------------------------------- Key: JBPM-1471 URL: https://jira.jboss.org/jira/browse/JBPM-1471 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jPDL 3.2.3 Reporter: Pavel Kadlec The path of execution of the super process token should not continue when the token was ended. If it is not tested, the ended super process token is signalled and the path of execution continues. I think it should not. I suggest following fix to org.jbpm.graph.exe.ProcessInstance.end() method. There is one change in if statement bellow... /** * ends (=cancels) this process instance and all the tokens in it. */ public void end() { // end the main path of execution rootToken.end(); if (end==null) { // mark this process instance as ended end = Clock.getCurrentTime(); // fire the process-end event ExecutionContext executionContext = new ExecutionContext(rootToken); processDefinition.fireEvent(Event.EVENTTYPE_PROCESS_END, executionContext); // add the process instance end log rootToken.addLog(new ProcessInstanceEndLog()); // check if this process was started as a subprocess of a super process if (superProcessToken!=null && !superProcessToken.hasEnded()) { // THIS IS THE FIX, TEST IF SUPER PROCESS TOKEN HAS ENDED addCascadeProcessInstance(superProcessToken.getProcessInstance()); ExecutionContext superExecutionContext = new ExecutionContext(superProcessToken); superExecutionContext.setSubProcessInstance(this); superProcessToken.signal(superExecutionContext); } // make sure all the timers for this process instance are cancelled when the process end updates get saved in the database. // TODO route this directly through the jobSession. just like the suspend and resume. // NOTE Only timers should be deleted, messages-type of jobs should be kept. SchedulerService schedulerService = (SchedulerService) Services.getCurrentService(Services.SERVICENAME_SCHEDULER, false); if (schedulerService!=null) schedulerService.deleteTimersByProcessInstance(this); } } -- 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, 10 months

8
16
0 / 0

[JBoss JIRA] Created: (JBPM-1759) Cleanup excluded jPDL test

by Thomas Diesler (JIRA)

Cleanup excluded jPDL test -------------------------- Key: JBPM-1759 URL: https://jira.jboss.org/jira/browse/JBPM-1759 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jBPM 4.0.0 Alpha1 -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-1769) fix db isolation test

by Tom Baeyens (JIRA)

fix db isolation test --------------------- Key: JBPM-1769 URL: https://jira.jboss.org/jira/browse/JBPM-1769 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: PVM Reporter: Tom Baeyens Fix For: jBPM 4.0.0 Alpha2 test JobExecutorIsolationDbTest requires a DB that supports DB isolation read committed. fix the test and make sure that it is only run on DB's that support this isolation level. please make sure that this test is not included when selecting src directory src/test/java in eclipse and executing all tests. consider moving it to a different module. -- 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, 10 months

1
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues November 2008