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

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" /> --- 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