September 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1771) Fix JobExecutorDbTest on postgresql

by Thomas Diesler (JIRA)

Fix JobExecutorDbTest on postgresql ----------------------------------- Key: JBPM-1771 URL: https://jira.jboss.org/jira/browse/JBPM-1771 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jBPM 3.3.1 GA expected:<[10X, 10Y, 10Z, 10a, 10b, 10c, 10d, 10e, 11X, 11Y, 11Z, 11a, 11b, 11c, 11d, 11e, 12X, 12Y, 12Z, 12a, 12b, 12c, 12d, 12e, 13X, 13Y, 13Z, 13a, 13b, 13c, 13d, 13e, 14X, 14Y, 14Z, 14a, 14b, 14c, 14d, 14e, 15X, 15Y, 15Z, 15a, 15b, 15c, 15d, 15e, 16X, 16Y, 16Z, 16a, 16b, 16c, 16d, 16e, 17X, 17Y, 17Z, 17a, 17b, 17c, 17d, 17e, 18X, 18Y, 18Z, 18a, 18b, 18c, 18d, 18e, 19X, 19Y, 19Z, 19a, 19b, 19c, 19d, 19e, 1X, 1Y, 1Z, 1a, 1b, 1c, 1d, 1e, 20X, 20Y, 20Z, 20a, 20b, 20c, 20d, 20e, 2X, 2Y, 2Z, 2a, 2b, 2c, 2d, 2e, 3X, 3Y, 3Z, 3a, 3b, 3c, 3d, 3e, 4X, 4Y, 4Z, 4a, 4b, 4c, 4d, 4e, 5X, 5Y, 5Z, 5a, 5b, 5c, 5d, 5e, 6X, 6Y, 6Z, 6a, 6b, 6c, 6d, 6e, 7X, 7Y, 7Z, 7a, 7b, 7c, 7d, 7e, 8X, 8Y, 8Z, 8a, 8b, 8c, 8d, 8e, 9X, 9Y, 9Z, 9a, 9b, 9c, 9d, 9e]> but was:<[100X, 100Y, 100Z, 100a, 100b, 100c, 100d, 100e, 108X, 108Y, 108Z, 108a, 108b, 108c, 108d, 108e, 116X, 116Y, 116Z, 116a, 116b, 116c, 116d, 116e, 124X, 124Y, 124Z, 124a, 124b, 124c, 124d, 124e, 132X, 132Y, 132Z, 132a, 132b, 132c, 132d, 132e, 140X, 140Y, 140Z, 140a, 140b, 140c, 140d, 140e, 148X, 148Y, 148Z, 148a, 148b, 148c, 148d, 148e, 156X, 156Y, 156Z, 156a, 156b, 156c, 156d, 156e, 164X, 164Y, 164Z, 164a, 164b, 164c, 164d, 164e, 172X, 172Y, 172Z, 172a, 172b, 172c, 172d, 172e, 180X, 180Y, 180Z, 180a, 180b, 180c, 180d, 180e, 188X, 188Y, 188Z, 188a, 188b, 188c, 188d, 188e, 36X, 36Y, 36Z, 36a, 36b, 36c, 36d, 36e, 44X, 44Y, 44Z, 44a, 44b, 44c, 44d, 44e, 52X, 52Y, 52Z, 52a, 52b, 52c, 52d, 52e, 60X, 60Y, 60Z, 60a, 60b, 60c, 60d, 60e, 68X, 68Y, 68Z, 68a, 68b, 68c, 68d, 68e, 76X, 76Y, 76Z, 76a, 76b, 76c, 76d, 76e, 84X, 84Y, 84Z, 84a, 84b, 84c, 84d, 84e, 92X, 92Y, 92Z, 92a, 92b, 92c, 92d, 92e]> -- 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

16 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-1958) Security issue allows arbitrary java code to be deployed and executed

by Thomas Diesler (JIRA)

Security issue allows arbitrary java code to be deployed and executed --------------------------------------------------------------------- Key: JBPM-1958 URL: https://jira.jboss.org/jira/browse/JBPM-1958 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Console Reporter: Thomas Diesler Assignee: Koen Aers Priority: Critical Fix For: jBPM 3.3.2 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

16 years, 3 months

3
14
0 / 0

[JBoss JIRA] Created: (JBPM-1178) Script conditions in transitions are evaluated as expressions by the decision node

by Romain Lamarche (JIRA)

Script conditions in transitions are evaluated as expressions by the decision node ---------------------------------------------------------------------------------- Key: JBPM-1178 URL: http://jira.jboss.com/jira/browse/JBPM-1178 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Environment: Windows XP, JBoss AS 4.2.2GA, MS SQL EXPRESS 2005, Jdk5 Reporter: Romain Lamarche Assigned To: Tom Baeyens The decision node does not evaluate scripts in conditional transitions. Indeed, the execute method of node type decision does not check what type of condition it is. Listing of the wrong code : (file Decision.java lines 120-135 in Jbpm Jpdl 3.2.2) } else { // new mode based on conditions in the transition itself Iterator iter = leavingTransitions.iterator(); while (iter.hasNext() && (transition==null)) { 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; } } } } The problem is the "JbpmExpressionEvaluator". -- 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

16 years, 3 months

5
7
0 / 0

[JBoss JIRA] Created: (JBPM-2489) jBPM proccess loses access to process variables when timer is used inside forked process

by Jiri Pechanec (JIRA)

jBPM proccess loses access to process variables when timer is used inside forked process ---------------------------------------------------------------------------------------- Key: JBPM-2489 URL: https://jira.jboss.org/jira/browse/JBPM-2489 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Jiri Pechanec Priority: Blocker See platform issue SOA-1449 -- 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

16 years, 3 months

2
11
0 / 0

[JBoss JIRA] Created: (JBPM-1883) Provide an initial implementation of a AS4 deployer

by Thomas Diesler (JIRA)

Provide an initial implementation of a AS4 deployer --------------------------------------------------- Key: JBPM-1883 URL: https://jira.jboss.org/jira/browse/JBPM-1883 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Productization Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: jBPM 3.3.1 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

16 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-2172) integrate jboss identity component

by Tom Baeyens (JIRA)

integrate jboss identity component ---------------------------------- Key: JBPM-2172 URL: https://jira.jboss.org/jira/browse/JBPM-2172 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Jeff Yu Fix For: jBPM 4.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

16 years, 4 months

2
20
0 / 0

[JBoss JIRA] Created: (JBPM-2543) Enhance query API with operations needed for JOPR plugin

by Joram Barrez (JIRA)

Enhance query API with operations needed for JOPR plugin -------------------------------------------------------- Key: JBPM-2543 URL: https://jira.jboss.org/jira/browse/JBPM-2543 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0, jBPM 4.1 Reporter: Joram Barrez Assignee: Joram Barrez Priority: Minor Fix For: jBPM 4.3 The following operations where demanded by Jim Ma for his JOPR plugin work (and I agree that they are needed). 1. JobQuery : query by job id 2. query historyTasks by process definition id" . 3. The api to query the average process instance duration . I get this value by sum and divide the process duration . It will be faster if there is the same api as the get average activity duration. 4. The api to get the process deployment , process definition , process instances , task number . It can be retrieved by calling the collection size . It will be efficient to select count(*) from database . -- 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

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2536) Make Job retry logic configurable

by Peter Horvath (JIRA)

Make Job retry logic configurable ---------------------------------- Key: JBPM-2536 URL: https://jira.jboss.org/jira/browse/JBPM-2536 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Peter Horvath Currently retry count is hard-coded to JobImpl (org.jbpm.pvm.internal.job.JobImpl.retries) This number should be configurable / there should be an option to completely disable job retries. -- 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

16 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-2485) Accessing the parent/super execution from a subprocess execution

by Flavio Donzé (JIRA)

Accessing the parent/super execution from a subprocess execution ---------------------------------------------------------------- Key: JBPM-2485 URL: https://jira.jboss.org/jira/browse/JBPM-2485 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0 Reporter: Flavio Donzé See the forum reference for the description -- 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

16 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-2329) re-introduce timers in the userguide

by Tom Baeyens (JIRA)

re-introduce timers in the userguide ------------------------------------ Key: JBPM-2329 URL: https://jira.jboss.org/jira/browse/JBPM-2329 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.1 change jpdpl schema of the timers: from <on event="timeout"> <timer duedate="10 minutes"/> <event-listener class="org.jbpm.examples.timer.event.Escalate" /> </on> to <timer duedate="10 minutes" fire-event="timeout"> <event-listener class="org.jbpm.examples.timer.event.Escalate" /> </timer> and re-introduce the timers back in the userguide -- 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

16 years, 4 months

3
7
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues September 2009