[JBoss JIRA] Created: (JBPM-2475) sub-process name is not resolved upon deployment with Eclipse or ant-task
by Toshiya Kobayashi (JIRA)
sub-process name is not resolved upon deployment with Eclipse or ant-task
-------------------------------------------------------------------------
Key: JBPM-2475
URL: https://jira.jboss.org/jira/browse/JBPM-2475
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Console
Affects Versions: jBPM 3.2.5.SP5
Reporter: Toshiya Kobayashi
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.7
If you omit binding attribute for <sub-process> in <process-state> and deploy the process definition with Eclipse or org.jbpm.ant.DeployProcessToServerTask, resolving sub-process will fail. jbpm-console will show -- "org.jbpm.JbpmException" was thrown. The message is: can't create a process instance when processDefinition is null --
ProcessUploadServlet calls jbpmConfiguration.createJbpmContext() after parsing and before deploying. If jbpmContext is not created before parsing, sub-process won't be resoleved(the call to DbSubProcessResolver.findSubProcess returns null.). So the default behaviour of binding attribute(parse time resolving) will fail.
--
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
[JBoss JIRA] Created: (JBPM-2474) Process variables of type hibernate-long-id/hibernate-string-id don't work
by steven wang (JIRA)
Process variables of type hibernate-long-id/hibernate-string-id don't work
--------------------------------------------------------------------------
Key: JBPM-2474
URL: https://jira.jboss.org/jira/browse/JBPM-2474
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.0
Reporter: steven wang
In jbpm.variable.types.xml, the type bindings for hibernate types are as follows:
<type name="hibernate-long-id" class="hibernate" id-type="long" variable-class="org.jbpm.pvm.internal.type.variable.HibernateLongVariable" />
<type name="hibernate-string-id" class="hibernate" id-type="string" variable-class="org.jbpm.pvm.internal.type.variable.HibernateStringVariable" />
but in TypeBinding.java
the pasing logic is as follows:
if (element.hasAttribute("class")) {
String className = element.getAttribute("class");
// if type="serializable"
if ("serializable".equals(className)) {
matcher = new SerializableMatcher();
// if type="persistable"
} else if ("persistable".equals(className)) {
if (element.hasAttribute("id-type")) {
String idType = element.getAttribute("id-type");
if ("long".equalsIgnoreCase(idType)) {
matcher = new HibernateLongIdMatcher(hibernateSessionFactoryName);
} else if ("string".equalsIgnoreCase(idType)) {
matcher = new HibernateStringIdMatcher(hibernateSessionFactoryName);
} else {
parse.addProblem("id-type was not 'long' or 'string': "+idType, element);
}
} else {
parse.addProblem("id-type is required in a persistable type", element);
}
// otherwise, we expect type="some.java.ClassName"
} else {
matcher = new ClassNameMatcher(className);
}
} else { ...
maybe the configured class should be "persistable".
but if I changed jbpm.variable.types.xml from "hibernate" to "persistable", I still can not save a process variable with value of a persistent hibernate object .
--
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
[JBoss JIRA] Deleted: (JBPM-2481) sub-process name is not resolved upon deployment with ant-task(DeployProcessTask)
by Toshiya Kobayashi (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-2481?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi deleted JBPM-2481:
------------------------------------
> sub-process name is not resolved upon deployment with ant-task(DeployProcessTask)
> ---------------------------------------------------------------------------------
>
> Key: JBPM-2481
> URL: https://jira.jboss.org/jira/browse/JBPM-2481
> Project: jBPM
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Toshiya Kobayashi
> Assignee: Alejandro Guizar
>
> If you omit binding attribute for <sub-process> in <process-state> and deploy the process definition with org.jbpm.ant.DeployProcessTask, resolving sub-process will fail. When you run the parent process with jbpm-console after the deployment, jbpm-console will show -- "org.jbpm.JbpmException" was thrown. The message is: can't create a process instance when processDefinition is null --
> DeployProcessTask calls jbpmConfiguration.createJbpmContext() after parsing and before deploying. If jbpmContext is not created before parsing, sub-process won't be resoleved(the call to DbSubProcessResolver.findSubProcess returns null.). So the default behaviour of binding attribute(parse time resolving) will fail.
--
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
[JBoss JIRA] Created: (JBPM-2481) sub-process name is not resolved upon deployment with ant-task(DeployProcessTask)
by Toshiya Kobayashi (JIRA)
sub-process name is not resolved upon deployment with ant-task(DeployProcessTask)
---------------------------------------------------------------------------------
Key: JBPM-2481
URL: https://jira.jboss.org/jira/browse/JBPM-2481
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jBPM 3.2.5.SP5
Reporter: Toshiya Kobayashi
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.7
If you omit binding attribute for <sub-process> in <process-state> and deploy the process definition with org.jbpm.ant.DeployProcessTask, resolving sub-process will fail. When you run the parent process with jbpm-console after the deployment, jbpm-console will show -- "org.jbpm.JbpmException" was thrown. The message is: can't create a process instance when processDefinition is null --
DeployProcessTask calls jbpmConfiguration.createJbpmContext() after parsing and before deploying. If jbpmContext is not created before parsing, sub-process won't be resoleved(the call to DbSubProcessResolver.findSubProcess returns null.). So the default behaviour of binding attribute(parse time resolving) will fail.
--
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
[JBoss JIRA] Created: (JBPM-2468) Oracle scripts provided with jbpm4.0 do not work. Creating a Task node results in FK violation.
by Shekhar Vemuri (JIRA)
Oracle scripts provided with jbpm4.0 do not work. Creating a Task node results in FK violation.
-----------------------------------------------------------------------------------------------
Key: JBPM-2468
URL: https://jira.jboss.org/jira/browse/JBPM-2468
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jBPM 4.0
Reporter: Shekhar Vemuri
Creation of a ProcessInstance that has a Task node, results in a Hibernate Exception, with a FK Violation.
An Attempt is made to insert into JBPM4_HIST_ACTINST without an insert into JBPM4_HIST_TASK.
WARNING: SQL Error: 2291, SQLState: 23000
Aug 3, 2009 7:39:33 AM org.hibernate.util.JDBCExceptionReporter logExceptions
SEVERE: ORA-02291: integrity constraint (SVC_GGOV.FK_HTI_HTASK) violated - parent key not found
Aug 3, 2009 7:39:33 AM org.hibernate.util.JDBCExceptionReporter logExceptions
WARNING: SQL Error: 2291, SQLState: 23000
Aug 3, 2009 7:39:33 AM org.hibernate.util.JDBCExceptionReporter logExceptions
SEVERE: ORA-02291: integrity constraint (SVC_GGOV.FK_HTI_HTASK) violated - parent key not found
Aug 3, 2009 7:39:33 AM org.hibernate.event.def.AbstractFlushingEventListener performExecutions
SEVERE: Could not synchronize database state with session
org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:94)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66)
at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:275)
at org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher.java:114)
at org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher.java:109)
at org.hibernate.jdbc.AbstractBatcher.prepareBatchStatement(AbstractBatcher.java:244)
at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2252)
at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2688)
at org.hibernate.action.EntityInsertAction.execute(EntityInsertAction.java:79)
at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:279)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:263)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:167)
at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventLis
tener.java:321)
at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:50)
at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1027)
at org.jbpm.pvm.internal.tx.SpringTransactionInterceptor.execute(SpringTransactionInterceptor.java:
84)
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.ja
va:70)
at edu.apollogrp.taskengine.workflow.service.impl.ExecutionManagementServiceImpl.startProcessAndSig
nal(ExecutionManagementServiceImpl.java:54)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInv
ocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.
java:149)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor
.java:106)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.
java:171)
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationIntercept
or.java:89)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.
java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy17.startProcessAndSignal(Unknown Source)
at edu.apollogrp.taskengine.workflow.logic.impl.WorkflowServiceImpl.createNewProcessInstanceAndStar
t(WorkflowServiceImpl.java:400)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInv
ocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.
java:149)
at org.springframework.aop.framework.adapter.MethodBeforeAdviceInterceptor.invoke(MethodBeforeAdvic
eInterceptor.java:50)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.
java:171)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor
.java:106)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.
java:171)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor
.java:106)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.
java:171)
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationIntercept
or.java:89)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.
java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy22.createNewProcessInstanceAndStart(Unknown Source)
at edu.apollogrp.taskengine.logic.event.TaskEventLogicImpl.raiseEvent(TaskEventLogicImpl.java:45)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInv
ocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.
java:149)
at org.springframework.aop.framework.adapter.MethodBeforeAdviceInterceptor.invoke(MethodBeforeAdvic
eInterceptor.java:50)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.
java:171)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor
.java:106)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.
java:171)
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationIntercept
or.java:89)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.
java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy24.raiseEvent(Unknown Source)
at edu.apollogrp.taskengine.util.interpreter.commands.RaiseEventCommand.executeInternal(RaiseEventC
ommand.java:32)
at edu.apollogrp.taskengine.util.interpreter.commands.BaseInterpreterCommand.executeCommand(BaseInt
erpreterCommand.java:43)
at edu.apollogrp.taskengine.util.interpreter.WorkflowInterpreter.executeCommand(WorkflowInterpreter
.java:95)
at edu.apollogrp.taskengine.util.interpreter.WorkflowInterpreter.executeCommand(WorkflowInterpreter
.java:76)
at edu.apollogrp.taskengine.util.interpreter.BaseInterpreter.interpretCommand(BaseInterpreter.java:
110)
at edu.apollogrp.taskengine.util.interpreter.BaseInterpreter.rep(BaseInterpreter.java:91)
at edu.apollogrp.taskengine.util.interpreter.BaseInterpreter.runMain(BaseInterpreter.java:54)
at edu.apollogrp.taskengine.util.interpreter.BaseInterpreter.runMain(BaseInterpreter.java:47)
at edu.apollogrp.taskengine.util.interpreter.WorkflowInterpreter.main(WorkflowInterpreter.java:46)
Caused by: java.sql.BatchUpdateException: ORA-02291: integrity constraint (SVC_GGOV.FK_HTI_HTASK) vi
olated - parent key not found
at oracle.jdbc.driver.DatabaseError.throwBatchUpdateException(DatabaseError.java:343)
at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:10768)
at org.apache.commons.dbcp.DelegatingStatement.executeBatch(DelegatingStatement.java:294)
at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:70)
at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:268)
... 73 more
This happens when the script provided with jbpm is used to deploy the tables in an oracle database.
We work with Oracle 10g.
This does not happen when the hbm2ddl property is turned on, as it is in the examples distribution. The examples work fine as long as the create-drop is enabled, if that is taken out and the examples are run against the schema generated by the scripts, they start failing too.
--
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