August 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2497) End always trigger deleteProcessInstance

by Hauke Rabe (JIRA)

End always trigger deleteProcessInstance ---------------------------------------- Key: JBPM-2497 URL: https://jira.jboss.org/jira/browse/JBPM-2497 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0 Reporter: Hauke Rabe Why should the process instance immediately be deleted on end? At least this should be configurable. -- 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, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-2498) improve exception message when execution not found

by Tom Baeyens (JIRA)

improve exception message when execution not found -------------------------------------------------- Key: JBPM-2498 URL: https://jira.jboss.org/jira/browse/JBPM-2498 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.1 java.lang.NullPointerException at org.jbpm.pvm.internal.cmd.GetExecutionVariablesCmd.execute(GetExecutionVariablesCmd.java:60) at org.jbpm.pvm.internal.cmd.GetExecutionVariablesCmd.execute(GetExecutionVariablesCmd.java:36) at org.jbpm.pvm.internal.svc.DefaultCommandService.execute(DefaultCommandService.java:42) at org.jbpm.pvm.internal.tx.StandardTransactionInterceptor.execute(StandardTransactionInterceptor.java:54) at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:54) at org.jbpm.pvm.internal.svc.RetryInterceptor.execute(RetryInterceptor.java:55) at org.jbpm.pvm.internal.svc.ExecutionServiceImpl.getVariable(ExecutionServiceImpl.java:130) -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-2445) JBPM4-Spring 1.2 integration problems

by manish hotwani (JIRA)

JBPM4-Spring 1.2 integration problems ------------------------------------- Key: JBPM-2445 URL: https://jira.jboss.org/jira/browse/JBPM-2445 Project: JBoss jBPM Issue Type: Patch Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0 Environment: Win XP, JBPM4, Tomcat 6, Spring 1.2.7 Reporter: manish hotwani Priority: Minor JPBM4 cannot be integrated with spring 1.2. I get the following exceptions when I try to deploy a process definition: java.lang.NoSuchMethodError: org.springframework.transaction.support.TransactionTemplate.(Lorg/springframework/transaction/PlatformTransactionManager;Lorg/springframework/transaction/TransactionDefinition;)V org.jbpm.pvm.internal.tx.SpringTransactionInterceptor.execute(SpringTransactionInterceptor.java:77) org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:54) org.jbpm.pvm.internal.svc.RetryInterceptor.execute(RetryInterceptor.java:55) org.jbpm.pvm.internal.repository.DeploymentImpl.deploy(DeploymentImpl.java:89). The cause of the error is that the constructor "public TransactionTemplate(PlatformTransactionManager transactionManager, TransactionDefinition transactionDefinition)" (which is used in SpringTransactionInterceptor) only exists in spring 2 (and onwards) and not in spring 1.2. -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Updated: (JBPM-165) process instance versioning

by Koen Aers (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-165?page=com.atlassian.jira.plugi... ] Koen Aers updated JBPM-165: --------------------------- Fix Version/s: jBPM 4.2 (was: jBPM 4.1) > process instance versioning > --------------------------- > > Key: JBPM-165 > URL: https://jira.jboss.org/jira/browse/JBPM-165 > Project: jBPM > Issue Type: Feature Request > Components: Runtime Engine > Reporter: Tom Baeyens > Assignee: Koen Aers > Fix For: jBPM 4.2 > > > i think jbpm could offer some degree of assistence in process instance versioning. > when a new version of a process is deployed, jbpm could do the following conversion for a process instance : > * input required: mapping of the nodes from the old to the new definition. > * cancel the old process instance > * create a new process instance and copy the runtime (exe) information such as tokens and process variables from the old process instance. > * then establish a special link between the 2 process instances to indicate that the new process instance is the continuation of the old process instance. > this way we can avoid the problematic conversion of logs, while still keeping them in the system. > NOTE: i believe that Bernd has got some code for this in jBPM 3. That could be used as a basis. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-2435) verify online presence of xsd's

by Tom Baeyens (JIRA)

verify online presence of xsd's ------------------------------- Key: JBPM-2435 URL: https://jira.jboss.org/jira/browse/JBPM-2435 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Koen Aers Fix For: jBPM 4.1 check the jbpm 3 version xsd's. it might be that we used some kind of forwards to link the jbpm.org location to the docs location where they are actually published. that should be double checked. check if jbpm 4 xsd is at the expected location. document all about xsd publication to the release guide wiki page. -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2476) creating new process instance from console fails to set process variables properly

by Marko Friedemann (JIRA)

creating new process instance from console fails to set process variables properly ---------------------------------------------------------------------------------- Key: JBPM-2476 URL: https://jira.jboss.org/jira/browse/JBPM-2476 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Console Affects Versions: jBPM 4.0 Environment: Jboss-5.1.0.GA on Windows XP Reporter: Marko Friedemann When creating a new ProcessInstance from the jbpm-console, the integration code fails to set process variables (eg. from form template for start activity) properly. The offending code is: ,-- ProcessManagementImpl.java, 265, 266 -- | | Execution exec = execService.startProcessInstanceById (definitionId); | execService.setVariables(exec.getId(), processVars); | `-------------------- Setting the variables after startProcessInstanceById() is pointless, as this starts and runs the instance. Easily fixed by supplying the variables to startProcessInstanceById(): ,-- fix -- | | Execution exec = execService.startProcessInstanceById (definitionId, processVars); | `------------- regards, Marko -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-2433) Review existing BI reports and enhance/add existing/new reports

by Joram Barrez (JIRA)

Review existing BI reports and enhance/add existing/new reports --------------------------------------------------------------- Key: JBPM-2433 URL: https://jira.jboss.org/jira/browse/JBPM-2433 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Joram Barrez Assignee: Joram Barrez Priority: Minor Fix For: jBPM 4.1 -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-2490) Inconsistency in user's guide: decide or select in DecisionHandler

by Sebastian Schneider (JIRA)

Inconsistency in user's guide: decide or select in DecisionHandler ------------------------------------------------------------------ Key: JBPM-2490 URL: https://jira.jboss.org/jira/browse/JBPM-2490 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0 Environment: does not need to be taken into account Reporter: Sebastian Schneider The user's guide tells you to implement a method called select when writing your own decision handler class by implementing DecisionHandler: String select(OpenExecution execution); Infact DecisionHandler makes you implement a method called decide: String decide(OpenExecution execution); So it seems there is a kind of inconsistency in the docs. -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2496) candidate-groups info lost

by Joram Barrez (JIRA)

candidate-groups info lost -------------------------- Key: JBPM-2496 URL: https://jira.jboss.org/jira/browse/JBPM-2496 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: GPD Affects Versions: jBPM 4.0 Reporter: Joram Barrez When manually adding 'candidate-groups="administrator" ' to a task in the XML, this field is lost after having saved, gone back to the diagram and back to the xml. Also the PNG is messed up. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1995) Provide a documented dev process that copes with database changes across releases

by Heiko Braun (JIRA)

Provide a documented dev process that copes with database changes across releases --------------------------------------------------------------------------------- Key: JBPM-1995 URL: https://jira.jboss.org/jira/browse/JBPM-1995 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Heiko Braun Assignee: Heiko Braun Fix For: jBPM 4.0.0 Alpha2 Make DB changes visible and provide a QA process to 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

14 years, 9 months

3
13
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues August 2009