January 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1881) Release jBPM 4.0.0 Alpha1

by Thomas Diesler (JIRA)

Release jBPM 4.0.0 Alpha1 ------------------------- Key: JBPM-1881 URL: https://jira.jboss.org/jira/browse/JBPM-1881 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Core Engine 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

17 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1921) getGroupTaskList(List actorids) behaviour changed

by Daniel Bremer-Tonn (JIRA)

getGroupTaskList(List actorids) behaviour changed ------------------------------------------------- Key: JBPM-1921 URL: https://jira.jboss.org/jira/browse/JBPM-1921 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: API Affects Versions: jBPM 3.3.0 GA Reporter: Daniel Bremer-Tonn We migrated from jpdl v3.2.3 to v3.3 and did see some new behaviour for "JBPMContext.getGroupTaskList(List actorIds)". Behaviour in V3.2.3: Assigning a task to two pooledActorIds and calling JBPMContext.getGroupTaskList(List actorIds) with these two pooledActorIds will get you a list with one TaskInstance. In v3.3 you will get now a list with two items, which are two references to the same Taskinstance. While digging into the code I've found a change in the corresponding hibernate-query ("TaskMgmtSession.findPooledTaskInstancesByActorIds" in hibernate.queries.hbm.xml). The 3.2.3 version uses the "distinct" keyword, while the 3.3 one does not. Since this is some change in behaviour of the method JBPMContext.getGroupTaskList(List actorIds) either it should be fixed, or if intended should be documented somewhere. Best regards, Daniel Bremer-Tonn -- 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

17 years, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-1824) Investigate core test failures against Sybase

by Thomas Diesler (JIRA)

Investigate core test failures against Sybase --------------------------------------------- Key: JBPM-1824 URL: https://jira.jboss.org/jira/browse/JBPM-1824 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Productization Reporter: Thomas Diesler Fix For: jBPM 3.3.1 GA <exclude>org/jbpm/db/DeleteProcessInstanceDbTest.java</exclude> <exclude>org/jbpm/graph/exe/SubProcessPlusConcurrencyDbTest.java</exclude> <exclude>org/jbpm/jbpm1072/JBPM1072Test.java</exclude> <exclude>org/jbpm/jbpm1755/JBPM1755Test.java</exclude> <exclude>org/jbpm/jbpm983/JBPM983Test.java</exclude> <exclude>org/jbpm/job/executor/JobExecutorDbTest.java</exclude> <exclude>org/jbpm/optimisticlocking/LockingTest.java</exclude> <exclude>org/jbpm/scheduler/exe/UnsafeSessionUsageTest.java</exclude> <exclude>org/jbpm/seam/JobExecutorCustomizationTest.java</exclude> -- 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

17 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPM-1816) Sanitize tests that leak jBPM configurations (and connection pools)

by Alejandro Guizar (JIRA)

Sanitize tests that leak jBPM configurations (and connection pools) ------------------------------------------------------------------- Key: JBPM-1816 URL: https://jira.jboss.org/jira/browse/JBPM-1816 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Productization Reporter: Alejandro Guizar Assignee: Alejandro Guizar Fix For: jBPM 3.3.0 GA Tests that use a custom jBPM configuration leave it hanging around with a session factory and a pool of JDBC connections. The jBPM configuration must be explicitly closed so that those JDBC connections can be released. -- 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

17 years, 3 months

1
6
0 / 0

[JBoss JIRA] Closed: (JBPM-1446) display non GMT+0 time zones

by Alejandro Guizar (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1446?page=com.atlassian.jira.plug... ] Alejandro Guizar closed JBPM-1446. ---------------------------------- Closing issues that I resolved in already released versions. > display non GMT+0 time zones > ---------------------------- > > Key: JBPM-1446 > URL: https://jira.jboss.org/jira/browse/JBPM-1446 > Project: JBoss jBPM > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core Engine > Reporter: Jiri Pechanec > Assignee: Alejandro Guizar > Fix For: jBPM 3.3.0 GA > > Attachments: Screenshot.jpg, SolutionShot.png > > > I spotted it today so I am creating the link to project JIRA. It is really inconvenient for user to have UTC time displayed in browser. See JBPM-987 -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1429) Custom FunctionMapper implementation is not picked up in org.jbpm.mail.Mail

by Martin Putz (JIRA)

Custom FunctionMapper implementation is not picked up in org.jbpm.mail.Mail --------------------------------------------------------------------------- Key: JBPM-1429 URL: https://jira.jboss.org/jira/browse/JBPM-1429 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jPDL 3.2.3 Reporter: Martin Putz Assignee: Alejandro Guizar Fix For: JBossBPM-3.3.0 I have created a custom implementation of the FunctionMapper, which provides a custom function I want to use in an email template. Now, after I add the reference to this FunctionMapper to jbpm.cfg.xml: <bean name="jbpm.function.mapper" class="org.jbpm.jpdl.el.impl.DateFormatFunctionMapper" singleton="true" /> it will get picked up, but unfortunately, the default Mail class does not use it because it always sets the FunctionMapper to null in the evaluate method (last parameter): String evaluate(String expression) { //... return (String) JbpmExpressionEvaluator.evaluate(expression, executionContext, variableResolver, null); this should be : return (String) JbpmExpressionEvaluator.evaluate(expression, executionContext, variableResolver, JbpmExpressionEvaluator.getUsedFunctionMapper()); -- 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

17 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1755) make field Join.parentLockMode persistent

by Alejandro Guizar (JIRA)

make field Join.parentLockMode persistent ----------------------------------------- Key: JBPM-1755 URL: https://jira.jboss.org/jira/browse/JBPM-1755 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: jPDL 3 Affects Versions: jBPM 3.3.0 CR1 Reporter: Alejandro Guizar Fix For: jBPM 3.3.0 GA The value of field Join.parentLockMode is read from the process definition but no database mapping was defined for 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

17 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPM-1248) examples do not have a javac source/target defined

by Alejandro Guizar (JIRA)

examples do not have a javac source/target defined -------------------------------------------------- Key: JBPM-1248 URL: http://jira.jboss.com/jira/browse/JBPM-1248 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jBPM jPDL 3.2.3 Reporter: Alejandro Guizar Fix For: jBPM jPDL 3.2.4 The javac tasks in example.base.build.xml have neither the source nor target attributes set. This causes the example classes to be compiled under whatever jdk version the compiler is using. In the case of the published 3.2.3 distro, the compiler used was jdk 6. Hence the examples can only be run under jre 6, otherwise an UnsupportedClassVersionError is thrown. -- 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

17 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPM-1802) Add sybase database option to installer

by Alejandro Guizar (JIRA)

Add sybase database option to installer --------------------------------------- Key: JBPM-1802 URL: https://jira.jboss.org/jira/browse/JBPM-1802 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Productization Reporter: Alejandro Guizar Assignee: Alejandro Guizar Fix For: jBPM 3.3.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

17 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-1376) Bug in JPDL 3.2.3 when using a configuration file not named 'jbpm.cfg.xml' (worked in 3.2.2)

by Joram Barrez (JIRA)

Bug in JPDL 3.2.3 when using a configuration file not named 'jbpm.cfg.xml' (worked in 3.2.2) -------------------------------------------------------------------------------------------- Key: JBPM-1376 URL: http://jira.jboss.com/jira/browse/JBPM-1376 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: jPDL 3 Affects Versions: jPDL 3.2.3 Environment: Windows XP, Eclipse 3.4, 0 JDK 1.6.0.05_b13 Reporter: Joram Barrez Priority: Critical Bug discovered when porting app from 3.2.2 to 3.2.3. Application uses a config file which is not named 'jbpm.cfg.xml'. See forum reference for more information and test class. Test class works for JPDL 3.2.2, but not for 3.2.3. Adding jbpm.cf.xml to the class path resolves the issue. However, by default jbpm should not fail to start and use the standard config which is in the distribution. -- 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

17 years, 3 months

2
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues January 2009