May 2010 - jbpm-issues - Jboss List Archives

[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, 10 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, 10 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, 10 months

3
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, 10 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, 10 months

4
10
0 / 0

[JBoss JIRA] Created: (JBPM-2706) Add subprocess with timers and wait state to test case suite

by Martin Porter (JIRA)

Add subprocess with timers and wait state to test case suite ------------------------------------------------------------ Key: JBPM-2706 URL: https://jira.jboss.org/jira/browse/JBPM-2706 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.x Reporter: Martin Porter Cleanup and add the attached test case for simple subprocess with custom java command exector and timeout loop for regression testing. -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2405) make task forms i18n-able

by Tom Baeyens (JIRA)

make task forms i18n-able ------------------------- Key: JBPM-2405 URL: https://jira.jboss.org/jira/browse/JBPM-2405 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Console, Runtime Engine Reporter: Tom Baeyens Fix For: jBPM 4.x gert, can you try and see where we need to update the engine in order to accomodate 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

13 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-2870) Auto-assign the autenticate user for a task

by Jaber C. Mourad (JIRA)

Auto-assign the autenticate user for a task ------------------------------------------- Key: JBPM-2870 URL: https://jira.jboss.org/browse/JBPM-2870 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.3 Environment: JBPM 4.3 with spring Reporter: Jaber C. Mourad I'm looking for something to assign automatically the current authenticate user when it is known by the ProcessEngine.setAuthenticatedUserId method. My usecase is very simple (but, AFAIK, no simple solution for this !) : when a user start a particular process, I need to assign or make it candidate to a particular task (the first one generally)... As it is that particular user who create the instance, it is assigned to complete that task... If it is possible to have an EL to describe the current autenticate user it would be very helpfull. for example : <task assignee="${context.authenticateUser}" candidate-users="${context.authenticateUser},bob" g="170,179,92,52" name="autoAssignTask"> <transition g="-81,-24" name="to theEnd" to="theEnd"/> </task> In that way it doesn't need to modify jpdl but it need to make the authenticate userId available. Regards -- 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, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-2773) TaskService: allow search for assigned candidate tasks

by Kai WeingÃ¤rtner (JIRA)

TaskService: allow search for assigned candidate tasks ------------------------------------------------------ Key: JBPM-2773 URL: https://jira.jboss.org/jira/browse/JBPM-2773 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.3 Environment: any Reporter: Kai WeingÃ¤rtner Fix For: jBPM 4.x I would like to be able to find all tasks a user is a candidate for, regardless of the task being assigned or not. Currently the TaskQuery.candidate - filter also sets the unassigned filter. Thus, already assigned candidate tasks can never be found. Possible use cases: - a task needs to be reassigned due to sickness of the assignee - user A needs to take user B's task, when a customer approaches user A about a task concerning him Solution: - don't add the unassigned filter in the candidate filter of TaskQuery but make them separate. To achieve the current result, one could set both filters explicitly. -- 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, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-2814) Trouble using a custom BusinessCalendar because of 'new BusinessCalendarImpl' in BusinessDayCalendarBinding

by Per Christian Henden (JIRA)

Trouble using a custom BusinessCalendar because of 'new BusinessCalendarImpl' in BusinessDayCalendarBinding ----------------------------------------------------------------------------------------------------------- Key: JBPM-2814 URL: https://jira.jboss.org/jira/browse/JBPM-2814 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Per Christian Henden Fix For: jBPM 4.x I've followed the howto on the JBPM webpages to replace BusinessCalendarImpl with my own implementation. My custom BusinessCalendar.add is called, that works, but in JBPM's BusinessDayCalendarBinding. java 'new BusinessCalendarImpl' is called and a BusinessCalendarImpl is used throughout the class. This choice results in a problem when setting the 'days' field based on parsing jbpm.business-calendar.cfg.xml. The field is written to the 'new BusinessCalendarImpl' and not to my custom BusinessCalendar. This means that in my custom BusinessCalendar implementation I have no access to that information ('days' is null). Other places in the JBPM code a processEngine.get(BusinessCalendar.class) is done to get an instance of the (custom) BusinessCalendar. -- 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, 10 months

3
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues May 2010