August 2010 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2924) Cannot retrieve information about a task within it's start event handler because task not initialised at the point the handler is invoked

by Ed Willis (JIRA)

Cannot retrieve information about a task within it's start event handler because task not initialised at the point the handler is invoked ----------------------------------------------------------------------------------------------------------------------------------------- Key: JBPM-2924 URL: https://jira.jboss.org/browse/JBPM-2924 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.4 Reporter: Ed Willis Re-opens https://jira.jboss.org/browse/JBPM-2644 which, in my opinion, was incorrectly closed. See last few comments on this Jira for more info. A common use-case (for us at least, and I suspect for many applications) is to perform some processing when a task starts in the start event handler. Currently, it is not possible to retrieve information about the task that has been started (in our case we need the participants) because it is not initialised when the start event fires. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
11
0 / 0

[JBoss JIRA] Created: (JBPM-2920) Choose N tasks out from M paths in fork nodes

by Jecoso Chou (JIRA)

Choose N tasks out from M paths in fork nodes ---------------------------------------------- Key: JBPM-2920 URL: https://jira.jboss.org/browse/JBPM-2920 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.4 Environment: JBOSS 5.1GA, JBPM 4.4, Reporter: Jecoso Chou Fix For: jBPM 4.5 For example: <fork name="fork1"> <transition name="to A" to="A"> </transition> <transition name="to B" to="B"> </transition> <transition name="to C" to="C"> </transition> <transition name="to D" to="D"> </transition> </fork> This issue means that when process to this fork, only some of this 4 transition can be chosen to go, for example ,the transition "to A" and "to A". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
9
0 / 0

[JBoss JIRA] Created: (JBPM-2911) Possible performance problem caused by autoSaveProcessInstances

by Alejandro Guizar (JIRA)

Possible performance problem caused by autoSaveProcessInstances --------------------------------------------------------------- Key: JBPM-2911 URL: https://jira.jboss.org/browse/JBPM-2911 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 3.2.5.SP5 Reporter: Alejandro Guizar Fix For: jBPM 3.2.10 autoSaveProcessInstances is a List type field of JbpmContext class, which contains the processInstance needed to persistent to database. List autoSaveProcessInstances = null; Due to the List type of autoSaveProcessInstances, the same processInstance can be repeatedly added to autoSaveProcessInstances by JbpmContext.addAutoSaveProcessInstance method. public void addAutoSaveProcessInstance(ProcessInstance processInstance) { if (autoSaveProcessInstances == null) autoSaveProcessInstances = new ArrayList(); autoSaveProcessInstances.add(processInstance); } When invoked by JbpmContext.close method, JbpmContext.autoSave will iterate each processInstance in the autoSaveProcessInstances to save, thus the processInstance be saved repeatedly. void autoSave() { if (autoSaveProcessInstances != null) { Iterator iter = autoSaveProcessInstances.iterator(); while (iter.hasNext()) { ProcessInstance processInstance = (ProcessInstance)iter.next(); save(processInstance); iter.remove(); } } } In a web app based on seam 2.2.0, jbpm 3.2.5.sp5, a jsf request will cause the same processInstance to be saved more than 2000 times. The suggestion is to change the type of autoSaveProcessInstances from List to Set. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPM-2473) description about coexistence of version and binding attribute for sub-process is wrong

by Toshiya Kobayashi (JIRA)

description about coexistence of version and binding attribute for sub-process is wrong ---------------------------------------------------------------------------------------- Key: JBPM-2473 URL: https://jira.jboss.org/jira/browse/JBPM-2473 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.5.SP5 Reporter: Toshiya Kobayashi Priority: Minor 21.4.28. sub-process When both version and binding="late" are given then jBPM will use the version as requested, but will not yet try to find the sub process when the parent process-state is deployed. http://docs.jboss.org/jbpm/v3.2/userguide/html_single/index.html#subproce... But actually, ProcessState.execute() ignores version attribute if binding="late". So fix the description to: When both version and binding="late" are given then jBPM will ignore the version attribute and use the latest version. -- 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

13 years, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (JBPM-2386) Update description of DeployProcessTask

by Toshiya Kobayashi (JIRA)

Update description of DeployProcessTask --------------------------------------- Key: JBPM-2386 URL: https://jira.jboss.org/jira/browse/JBPM-2386 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.5.SP5 Reporter: Toshiya Kobayashi Chapter 21.1.1 of the User Guide states: ============ <target name="deploy.par"> <taskdef name="deploypar" classname="org.jbpm.ant.DeployProcessTask"> <classpath --make sure the jbpm-[version].jar is in this classpath--/> </taskdef> <deploypar par="build/myprocess.par" /> </target> To deploy more process archives at once, use the nested fileset elements. The file attribute itself is optional. Other attributes of the ant task are: * cfg: cfg is optional, the default value is 'hibernate.cfg.xml'. The hibernate configuration file that contains the jdbc connection properties to the database and the mapping files. * properties: properties is optional and overwrites *all* hibernate properties as found in the hibernate.cfg.xml * createschema: if set to true, the jbpm database schema is created before the processes get deployed. ============ http://docs.jboss.org/jbpm/v3.2/userguide/html_single/#theprocessarchive But this description is old now. They should be: ============= <target name="deploy.par"> <taskdef name="deploypar" classname="org.jbpm.ant.DeployProcessTask"> <classpath --ensure jbpm-[version].jar is in this classpath--/> </taskdef> <deploypar process="build/myprocess.par" /> </target> To deploy more process archives at once, use the nested fileset elements. The process attribute itself is optional. Other attributes of the ant task are: * jbpmcfg: Optional, the default value is jbpm.cfg.xml. The JBPM configuration file can specify the location of Hibernate configuration file ( the default value is hibernate.cfg.xml ) that contains the jdbc connection properties to the database and the mapping files. ============= -- 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

13 years, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (JBPM-2530) Add SLF4J support to allow plugging in any logging framework

by Peter Horvath (JIRA)

Add SLF4J support to allow plugging in any logging framework ------------------------------------------------------------ Key: JBPM-2530 URL: https://jira.jboss.org/jira/browse/JBPM-2530 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Peter Horvath Adding SLF4J logging support would make it possible to plug in any Logging framework to jBPM without any further code modification. Adding a wrapper for SLF4J org.slf4j.Logger and org.slf4j.LoggerFactory to org.jbpm.internal.log.Log class (similarly to the current Log4j implementation) would be trivial to implement and would provide an extremely powerful logging system to jBPM. -- 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

13 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-2917) Getting Http 500 when trying to create an request

by Raji Ramachandran (JIRA)

Getting Http 500 when trying to create an request ------------------------------------------------- Key: JBPM-2917 URL: https://jira.jboss.org/browse/JBPM-2917 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jBPM 4.4, jBPM 4.3 Environment: Redhat Linux 4 and JBOSS 5.1.0.GA Reporter: Raji Ramachandran I installed the default example that comes with the distribution. When I tried to create a Vacation Request Instance I get the following error --------- New Process Instance: VacationRequest-2 Not found The requested URL /gwt-console-server/rs/form/process/VacationRequest-2/render was not found on this server -------- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-2850) Column sorting broken in console tables

by M M (JIRA)

Column sorting broken in console tables --------------------------------------- Key: JBPM-2850 URL: https://jira.jboss.org/jira/browse/JBPM-2850 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Console Affects Versions: jBPM 4.0, jBPM 4.1, jBPM 4.2, jBPM 4.3 Reporter: M M Clicking on column headers in tables causes the contents of those tables to be sorted. However, sorting on columns that contain numbers appears to be broken. For example, given "1,3,5,8,10,11,13,20", it will sort as "1,10,11,13,20,3,5,8". Sorting of other (string) columns works fine. I would also recommend that tables containing data with logically-composite keys be sorted by multiple columns, with the column selected for sorting being the first key by which the rows are sorted. For example, "Process Definitions" could be sorted by Name, then by Version. That would make it easy to find the latest version of a given process definition. -- 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

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2805) Add access to event type in EventListener interface

by Mike Martin (JIRA)

Add access to event type in EventListener interface --------------------------------------------------- Key: JBPM-2805 URL: https://jira.jboss.org/jira/browse/JBPM-2805 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jBPM 4.x Reporter: Mike Martin Add the ability to determine the event type ("start" or "end") from within an EventListener implementation. There should also be the ability to easily determine the name of the process definition step where the event occurred. This makes it possible to write a single event listener that handles many different kinds of events. As far as design, it seems odd that the notify() method has a *Execution parameter, rather than an "event" parameter that contains all information about the event that occurred; the latter would be more in line with the way event listener interfaces are usually designed in Java. -- 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

13 years, 9 months

4
10
0 / 0

[JBoss JIRA] Created: (JBPM-2916) Employ JBoss Cache in the jBPM enterprise configuration

by Alejandro Guizar (JIRA)

Employ JBoss Cache in the jBPM enterprise configuration ------------------------------------------------------- Key: JBPM-2916 URL: https://jira.jboss.org/browse/JBPM-2916 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Alejandro Guizar Assignee: Alejandro Guizar Fix For: jBPM 3.2.10 A cluster-safe 2nd level cache provider should be used instead of the HashtableCashProvider -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 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 August 2010