February 2010 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2764) extend API to make it possible to determine the type of an active activity

by Sebastian Schneider (JIRA)

extend API to make it possible to determine the type of an active activity -------------------------------------------------------------------------- Key: JBPM-2764 URL: https://jira.jboss.org/jira/browse/JBPM-2764 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0, jBPM 4.1, jBPM 4.2, jBPM 4.3 Environment: not relevant Reporter: Sebastian Schneider Fix For: jBPM 4.x The API should be extended in that way that you can easily determine the type of an active activity. To achieve this getActiveActivities() could be extended to also return the type of an activity additionally to its name and description. Or there could be a method taking an activity's name and returning its type. -- 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

14 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-2658) Process variables of type hibernate-long-id/hibernate-string-id don't work

by Derek Cornelius (JIRA)

Process variables of type hibernate-long-id/hibernate-string-id don't work -------------------------------------------------------------------------- Key: JBPM-2658 URL: https://jira.jboss.org/jira/browse/JBPM-2658 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.2 Reporter: Derek Cornelius This is the same problem as JBPM-2474. The problem is in HibernateIdMatcher. if (sessionFactory!=null) { ClassMetadata classMetadata = sessionFactory.getClassMetadata(value.getClass()); matches = ( (classMetadata!=null) && (classMetadata.getIdentifierType().getClass()==getIdType()) ); } value.getClass() is returning the Javassist proxy class that is not found. It needs to check for "value.getClass().getSuperClass()" if value instance of HibernateProxy. -- 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

14 years, 2 months

5
4
0 / 0

[JBoss JIRA] Created: (JBPM-1992) Logging is missing if JobExecutorThread marks TX as rollbackonly because of max

by Roman Heinz (JIRA)

Logging is missing if JobExecutorThread marks TX as rollbackonly because of max ------------------------------------------------------------------------------- Key: JBPM-1992 URL: https://jira.jboss.org/jira/browse/JBPM-1992 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.3.1 GA Reporter: Roman Heinz If the execution of an action/script/... takes longer than the time configured org.jbpm.job.executor.JobExecutor.maxLockTime, the current TX is marked as rollback-only without any logging. In JobExecutorThread: // if this job is locked too long long totalLockTimeInMillis = System.currentTimeMillis() - job.getLockTime().getTime(); if (totalLockTimeInMillis>maxLockTime) { jbpmContext.setRollbackOnly(); } Logging is missing to inform about the jbpmContext.setRollbackOnly() together with the reason. -- 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

14 years, 3 months

4
5
0 / 0

[JBoss JIRA] Created: (JBPM-2398) expose full history details through the history api

by Tom Baeyens (JIRA)

expose full history details through the history api --------------------------------------------------- Key: JBPM-2398 URL: https://jira.jboss.org/jira/browse/JBPM-2398 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 expose the history that is in the database through the api -- 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

14 years, 3 months

5
25
0 / 0

[JBoss JIRA] Created: (JBPM-2769) Add FreeMarker support for mail templates

by Peter Horvath (JIRA)

Add FreeMarker support for mail templates ----------------------------------------- Key: JBPM-2769 URL: https://jira.jboss.org/jira/browse/JBPM-2769 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.x Reporter: Peter Horvath JBPM already uses FreeMarker to generate task forms. It would be great if FreeMarker could be used as a mail template engine as well. -- 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

14 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-2417) allow for programmatic way to specify authentication through service api

by Tom Baeyens (JIRA)

allow for programmatic way to specify authentication through service api ------------------------------------------------------------------------ Key: JBPM-2417 URL: https://jira.jboss.org/jira/browse/JBPM-2417 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 first target is our own console. our own console should pass the authentication information through the api. maybe this can be part of the more general: User provided transactional resources -- 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

14 years, 4 months

3
9
0 / 0

[JBoss JIRA] Created: (JBPM-2568) review history based on user feedback

by Tom Baeyens (JIRA)

review history based on user feedback ------------------------------------- Key: JBPM-2568 URL: https://jira.jboss.org/jira/browse/JBPM-2568 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.3 Ronald mentioned a lot of questions and activity around history. This issue is a reminder that we have to look into this topic in the 4.3 jira period (1st half of november) https://jira.jboss.org/jira/sr/jira.issueviews:searchrequest-printable/te... We should try to get an overview of what exactly the history related questions/issues are and find out how we can address them. Then translate that into concrete jira issues that can be prioritized. -- 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

14 years, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPM-2442) Review task history details and add new information where needed

by Joram Barrez (JIRA)

Review task history details and add new information where needed ---------------------------------------------------------------- Key: JBPM-2442 URL: https://jira.jboss.org/jira/browse/JBPM-2442 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Joram Barrez Priority: Minor Fix For: jBPM 4.x See forum reference (assignment history). Check if there are other events that need to be logged. -- 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

14 years, 4 months

4
7
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

14 years, 4 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

14 years, 4 months

2
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues February 2010