[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
15 years, 4 months
[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
15 years, 4 months
[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
15 years, 4 months
[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
15 years, 4 months