November 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2616) clean up JpdlDeployer

by Tom Baeyens (JIRA)

clean up JpdlDeployer --------------------- Key: JBPM-2616 URL: https://jira.jboss.org/jira/browse/JBPM-2616 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.3 still quite some dead code in there. i think about most of 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

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-2491) Deleting a ProcessInstance having a running Sub-ProcessInstance fails

by Flavio Donzé (JIRA)

Deleting a ProcessInstance having a running Sub-ProcessInstance fails --------------------------------------------------------------------- Key: JBPM-2491 URL: https://jira.jboss.org/jira/browse/JBPM-2491 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0 Reporter: Flavio Donzé When trying to delete a ProcessInstance using ExecutionService.deleteProcessInstance() an SQLException is thrown if the ProcessInstance has a running Sub-ProcessInstance. Trying to delete the Sub-ProcessInstance first doesn't work either. The problem here are the foreign key constraints: Deleting the super process: org.postgresql.util.PSQLException: ERROR: update or delete on table "jbpm4_execution" violates foreign key constraint "fk_exec_superexec" on table "jbpm4_execution" Detail: Key (dbid_)=(176) is still referenced from table "jbpm4_execution". Deleting the sub process: org.postgresql.util.PSQLException: ERROR: update or delete on table "jbpm4_execution" violates foreign key constraint "fk_exec_subpi" on table "jbpm4_execution" Detail: Key (dbid_)=(179) is still referenced from table "jbpm4_execution". Maybe loosen up the sub>super constraint? -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2649) HistoryActivityInstanceQueryImpl references wrong property for processDefinitionId

by Bryce Harward (JIRA)

HistoryActivityInstanceQueryImpl references wrong property for processDefinitionId ---------------------------------------------------------------------------------- Key: JBPM-2649 URL: https://jira.jboss.org/jira/browse/JBPM-2649 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0, jBPM 4.1, jBPM 4.2 Reporter: Bryce Harward Calling HistoryActivityInstanceQuery.processDefinitionId(processDefinitionId) results in a Hibernate exception. Looking at the source, the HQL in HistoryActivityInstanceQueryImpl is incorrect. HistoryActivityInstanceQueryImpl line 57 (jbpm 4.2): appendWhereClause(" hai.historyActivityInstance.processDefinitionId = '"+processDefinitionId+"' ", hql); should read: appendWhereClause(" hai.historyProcessInstance.processDefinitionId = '"+processDefinitionId+"' ", hql); -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2291) Process project creation wizard in JBDS 2.0 fails to create a complete sample project a jBPM runtime as provided in SOA-P 4.3CP01

by Tom Baeyens (JIRA)

Process project creation wizard in JBDS 2.0 fails to create a complete sample project a jBPM runtime as provided in SOA-P 4.3CP01 --------------------------------------------------------------------------------------------------------------------------------- Key: JBPM-2291 URL: https://jira.jboss.org/jira/browse/JBPM-2291 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Alejandro Guizar Fix For: SOA 4.3 CP02 Koen: "The jBPM designer and the runtime have one integration point: a configuration file called 'version.info.xml'. This file contains the version info of the runtime and the jar files that need to be on the classpath of a jbpm project in the gpd. If one of the jar files is not necessary anymore for various reasons, and it is removed from the runtime than it should also be removed from the file (if it is referenced in the file of course). " -- 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, 1 month

3
8
0 / 0

[JBoss JIRA] Created: (JBPM-2415) add declaration of process variables

by Tom Baeyens (JIRA)

add declaration of process variables ------------------------------------ Key: JBPM-2415 URL: https://jira.jboss.org/jira/browse/JBPM-2415 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 -- 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, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (JBPM-2638) Upgrade from 3.2.6.GA to 3.2.8 gives problem with the table JBPM_DELEGATION

by Sand Lee (JIRA)

Upgrade from 3.2.6.GA to 3.2.8 gives problem with the table JBPM_DELEGATION --------------------------------------------------------------------------- Key: JBPM-2638 URL: https://jira.jboss.org/jira/browse/JBPM-2638 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.8, jBPM 3.2.7 Environment: Hibernate 3.3.1.GA Postgresql 8.3.x Seam 2.2.0 JBPM 3.2.8 Reporter: Sand Lee The enviroment was running with jBPM 3.2.6.GA, but JBPM-2036 forces us to upgrade. After the upgrading to 3.2.8 we have faced problem during deployment: Caused by: java.lang.RuntimeException: could not deploy a process definition at com.app.dev.Jbpm.installProcessDefinitions(Jbpm.java:367) at com.app.dev.Jbpm.startup(Jbpm.java:94) 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.jboss.seam.util.Reflections.invoke(Reflections.java:22) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:144) at org.jboss.seam.Component.callComponentMethod(Component.java:2249) at org.jboss.seam.Component.callCreateMethod(Component.java:2172) at org.jboss.seam.Component.newInstance(Component.java:2132) ... 114 more Caused by: org.hibernate.MappingException: Could not determine type for: longstring, at table: JBPM_DELEGATION, for columns: [org.hibernate.mapping.Column(CLASSNAME_)] at org.hibernate.mapping.SimpleValue.getType(SimpleValue.java:292) at org.hibernate.mapping.SimpleValue.isValid(SimpleValue.java:276) at org.hibernate.mapping.Property.isValid(Property.java:207) at org.hibernate.mapping.PersistentClass.validate(PersistentClass.java:458) at org.hibernate.mapping.RootClass.validate(RootClass.java:215) at org.hibernate.cfg.Configuration.validate(Configuration.java:1135) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1320) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:867) at org.jbpm.persistence.db.DbPersistenceServiceFactory.getSessionFactory(DbPersistenceServiceFactory.java:104) at org.jbpm.persistence.db.DbPersistenceService.getSessionFactory(DbPersistenceService.java:84) at org.jbpm.persistence.db.DbPersistenceService.getSession(DbPersistenceService.java:89) at org.jbpm.persistence.db.DbPersistenceService.getGraphSession(DbPersistenceService.java:320) at org.jbpm.JbpmContext.getGraphSession(JbpmContext.java:604) at org.jbpm.JbpmContext.deployProcessDefinition(JbpmContext.java:165) at com.app.dev.Jbpm.deployProcess(Jbpm.java:383) at com.app.dev.Jbpm.installProcessDefinitions(Jbpm.java:361) ... 124 more When I look to the at the files I see: (files from http://repository.jboss.org/maven2/org/jbpm/jbpm3/jbpm-jpdl/) diff jbpm-jpdl-3.2.6.GA-sources/org/jbpm/instantiation/Delegation.hbm.xml jbpm-jpdl-3.2.8-sources/org/jbpm/instantiation/Delegation.hbm.xml 11,12c11,12 < <property name="className" column="CLASSNAME_" type="string" length="4000" /> < <property name="configuration" column="CONFIGURATION_" type="string" length="4000" /> --- > <property name="className" column="CLASSNAME_" type="longstring" length="4000" /> > <property name="configuration" column="CONFIGURATION_" type="longstring" length="4000" /> 18,19c18 Why was this changed and how can I make hibernate and postgres accepting this "longstring"? -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-2403) Fork Activity FIX. PVM trunk.

by Mark Kedzierski (JIRA)

Fork Activity FIX. PVM trunk. ------------------------------ Key: JBPM-2403 URL: https://jira.jboss.org/jira/browse/JBPM-2403 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 Reporter: Mark Kedzierski Fix For: jBPM 4.x Fork activity is broken in the jbpm4 pvm module under the svn trunk. This is caused by a recent commit to org.jbpm.pvm.internal.model.DefaultIdGenerator. My patch is included. The hibernate save happens before the execution.id is set, resulting in a UniqueConstraintException on the commit. -- 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, 1 month

4
8
0 / 0

[JBoss JIRA] Created: (JBPM-2606) Process files not suffixed with .jpdl.xml are not loaded correctly

by Paul Smith (JIRA)

Process files not suffixed with .jpdl.xml are not loaded correctly ------------------------------------------------------------------ Key: JBPM-2606 URL: https://jira.jboss.org/jira/browse/JBPM-2606 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.1 Environment: Windows XP using JBPM4.1 Reporter: Paul Smith If you try to deploy a process definition in a file that is not suffixed with .jpdl.xml then then the process is not deployed correctly. I have demonstrated this with the code in the attached jar file. There are two identical processes one called helloWorldOK and one called helloWorldBroken. One is in a file suffixed as .jpdl.xml and the other suffixed as _jpdl.xml. Both files seem to deploy correctly but when one tries to perform a startProcessInstanceByKey the process contained in the file suffixed by _jpdl.xml cannot be located. I have tried this with other file suffixes but it seems the file MUST be suffixed with .jpdl.xml. The name of the file should be irrelevant as all information is contained in the xml. -- 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, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-2595) introduce an attribute "description" for transitions and show it in the process diagram

by Sebastian Schneider (JIRA)

introduce an attribute "description" for transitions and show it in the process diagram --------------------------------------------------------------------------------------- Key: JBPM-2595 URL: https://jira.jboss.org/jira/browse/JBPM-2595 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Sebastian Schneider Priority: Minor Fix For: jBPM 4.3 Normally I prefer to use short "kind of technical" names for the transitions but I would rather have a long name or a description in the process diagram which is shown by the console. So my suggestion is to add an attribute description to transitions and to display the transitions' descriptions instead of their names in the diagram. If the description is not set or empty the name could be displayed instead. By the term description I don't mean a long text but rather a long user friendly name for the transition in contrast to a short technical one. -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2381) SQLException while deploying process into ORACLE 9.0.5i database

by Ralf Edmund Stranzenbach (JIRA)

SQLException while deploying process into ORACLE 9.0.5i database ---------------------------------------------------------------- Key: JBPM-2381 URL: https://jira.jboss.org/jira/browse/JBPM-2381 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0.CR1 Reporter: Ralf Edmund Stranzenbach Deploying a new process into the repository using the source-code below leads to an SQL-Exception: {code} RepositoryService service = getBean("repositoryService", RepositoryService.class); Deployment deployment = service.createDeployment(); deployment.addResourceFromClasspath("de/reswi/jbpm/Registration.jpdl.xml"); deployment.deploy(); {code} Detail Message: could not insert: [org.jbpm.pvm.internal.lob.Lob] SQL: insert into JBPM4_LOB (DBVERSION_, BLOB_VALUE_, BINARY_VALUE_, CLOB_VALUE_, TEXT_VALUE_, DBID_) values (?, ?, ?, ?, ?, ?) Cause: SQLException detailMessage: Vorgang nicht zulässig: streams type cannot be used in batching vendorCode: 17090 May be, it is not a good idea to directly INSERT large objects on Oracle 9.0.5? I've checked this using drivers ojdbc14.jar and ojdbc6.jar. -- 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, 1 month

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues November 2009