September 2009 - jbpm-issues - Jboss List Archives

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

[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

14 years, 4 months

3
5
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

14 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-2434) Write jBPM4 article

by Joram Barrez (JIRA)

Write jBPM4 article ------------------- Key: JBPM-2434 URL: https://jira.jboss.org/jira/browse/JBPM-2434 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Joram Barrez Assignee: Joram Barrez Fix For: jBPM 4.1 Write a general article explaining what jBPM4 is, why and when you should use it. Also think about a valid use case that shows the value of using jBPM4. -- 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, 5 months

4
5
0 / 0

[JBoss JIRA] Created: (JBPM-1768) fix groovy expression support

by Tom Baeyens (JIRA)

fix groovy expression support ----------------------------- Key: JBPM-1768 URL: https://jira.jboss.org/jira/browse/JBPM-1768 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.0.0 Alpha2 Fix test GroovyExpressionTest It's a matter of getting the right dependencies defined in maven. -- 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, 5 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues September 2009