July 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2297) Fork activities don't save child executions

by Alexis Seigneurin (JIRA)

Fork activities don't save child executions ------------------------------------------- Key: JBPM-2297 URL: https://jira.jboss.org/jira/browse/JBPM-2297 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0.0.Beta2 Reporter: Alexis Seigneurin When you create a fork activity, child executions are not saved in the session. The consequence is that, at some point, an execution with ID 0 is searched in the database: Exception in thread "main" org.hibernate.ObjectNotFoundException: No row with the given identifier exists: [org.jbpm.jpdl.internal.model.JpdlExecution#0] at org.hibernate.impl.SessionFactoryImpl$1.handleEntityNotFound(SessionFactoryImpl.java:375) at org.hibernate.proxy.AbstractLazyInitializer.checkTargetState(AbstractLazyInitializer.java:79) at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:68) at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:111) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:140) at org.jbpm.jpdl.internal.model.JpdlExecution$$EnhancerByCGLIB$$9a4d98d.createTask(<generated>) at org.jbpm.jpdl.internal.activity.TaskActivity.execute(TaskActivity.java:49) at org.jbpm.pvm.internal.model.op.ExecuteActivity.perform(ExecuteActivity.java:57) at org.jbpm.pvm.internal.model.ExecutionImpl.performAtomicOperationSync(ExecutionImpl.java:589) at org.jbpm.pvm.internal.model.ExecutionImpl.performAtomicOperation(ExecutionImpl.java:562) at org.jbpm.pvm.internal.model.ExecutionImpl.take(ExecutionImpl.java:444) at org.jbpm.pvm.internal.model.ExecutionImpl.take(ExecutionImpl.java:448) at org.jbpm.jpdl.internal.activity.ForkActivity.execute(ForkActivity.java:61) at org.jbpm.pvm.internal.model.op.ExecuteActivity.perform(ExecuteActivity.java:57) at org.jbpm.pvm.internal.model.ExecutionImpl.performAtomicOperationSync(ExecutionImpl.java:589) at org.jbpm.pvm.internal.model.ExecutionImpl.performAtomicOperation(ExecutionImpl.java:562) at org.jbpm.pvm.internal.model.ExecutionImpl.start(ExecutionImpl.java:201) at org.jbpm.pvm.internal.cmd.StartProcessInstanceInLatestCmd.execute(StartProcessInstanceInLatestCmd.java:63) at org.jbpm.pvm.internal.cmd.StartProcessInstanceInLatestCmd.execute(StartProcessInstanceInLatestCmd.java:39) 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.startProcessInstanceByKey(ExecutionServiceImpl.java:72) To fix the issue, in the ForkActivity class, the childExecution instances which are created must be saved. I attached a patch (though I guess there is another way to perform the save by using commands). -- 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, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-2425) Completing task with nonexistent outcome silently does nothing

by Vladimir Kulev (JIRA)

Completing task with nonexistent outcome silently does nothing -------------------------------------------------------------- Key: JBPM-2425 URL: https://jira.jboss.org/jira/browse/JBPM-2425 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0 Reporter: Vladimir Kulev Try to complete "get approval" task in "subprocess/outcomeactivity" example, but with nonexistent outcome. Task will be closed, but task activity will be still active. -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2343) completeTask with submitting variables

by Bernd Ruecker (JIRA)

completeTask with submitting variables -------------------------------------- Key: JBPM-2343 URL: https://jira.jboss.org/jira/browse/JBPM-2343 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Bernd Ruecker Priority: Minor Fix For: jBPM 4.x These two methods should be invoked in one method: taskService.setVariable(task.getDbid(), "problem", "Out of stock"); taskService.completeTask(task.getDbid()); Maybe there should be a similar task where you set process variables as weill? -- 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, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPM-2407) Join multiplicity FIX

by Mark Kedzierski (JIRA)

Join multiplicity FIX ----------------------- Key: JBPM-2407 URL: https://jira.jboss.org/jira/browse/JBPM-2407 Project: JBoss jBPM Issue Type: Patch Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.x Environment: Windows, JBoss 5.1.0.GA, Microsoft SQL Server 2008 Reporter: Mark Kedzierski Fix For: jBPM 4.x Attachments: JoinBinding.java the JPDL JoinBinding is broken. the string multiplicity is spelled wrong, i.e. "multiplicicty". This causes the multiplicity to never be set in the JoinActivity, so it always has a default value. To reproduce this, simply create a process which has a join which has several possible incoming transitions, and set the multiplicity to something. -- 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, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-2392) review duedate in jpdl3 converter

by Tom Baeyens (JIRA)

review duedate in jpdl3 converter --------------------------------- Key: JBPM-2392 URL: https://jira.jboss.org/jira/browse/JBPM-2392 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Fix For: jBPM 4.1 i saw this in the Jpdl3Converter: String duedateText = taskElement.attributeValue("duedate"); if (duedateText == null) { duedateText = taskElement.attributeValue("dueDate"); } i believe this is a typo. the second dueDate should be duedate, i think. -- 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, 11 months

3
8
0 / 0

[JBoss JIRA] Created: (JBPM-2014) Provide equivalent activities as in jBPM3

by Heiko Braun (JIRA)

Provide equivalent activities as in jBPM3 ----------------------------------------- Key: JBPM-2014 URL: https://jira.jboss.org/jira/browse/JBPM-2014 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Core Engine Reporter: Heiko Braun Assignee: Heiko Braun jBPM4 should have at least the same functional scope then jBPM3. -- 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, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-1968) Console integration for jbpm3 doesn't write start instance logs

by Heiko Braun (JIRA)

Console integration for jbpm3 doesn't write start instance logs --------------------------------------------------------------- Key: JBPM-1968 URL: https://jira.jboss.org/jira/browse/JBPM-1968 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: jBPM 3.3.2 GA -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2424) tidy up installer

by Alejandro Guizar (JIRA)

tidy up installer ----------------- Key: JBPM-2424 URL: https://jira.jboss.org/jira/browse/JBPM-2424 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 3.2.5.SP5 Reporter: Alejandro Guizar Assignee: Alejandro Guizar Fix For: jBPM 3.2.7 Several things are broken in the installer: * JBoss home directory is set to the builder's jboss.home property * JBoss home panel should immediately follow JBoss version panel * Eclipse download only works for linux * izpack globalization support is not leveraged -- 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, 11 months

1
4
0 / 0

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

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-165?page=com.atlassian.jira.plugi... ] Tom Baeyens reassigned JBPM-165: -------------------------------- Assignee: Koen Aers (was: Tom Baeyens) > process instance versioning > --------------------------- > > Key: JBPM-165 > URL: https://jira.jboss.org/jira/browse/JBPM-165 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Runtime Engine > Reporter: Tom Baeyens > Assignee: Koen Aers > Fix For: jBPM 4.1 > > > 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, 11 months

1
0
0 / 0

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

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-165?page=com.atlassian.jira.plugi... ] Tom Baeyens commented on JBPM-165: ---------------------------------- @see also http://calebpowell.blogspot.com/2009/06/jbpm-migrations-our-approach.html > process instance versioning > --------------------------- > > Key: JBPM-165 > URL: https://jira.jboss.org/jira/browse/JBPM-165 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Runtime Engine > Reporter: Tom Baeyens > Assignee: Tom Baeyens > Fix For: jBPM 4.1 > > > 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, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues July 2009