JBPM Schema Doesn't Reflect Hibernate Mapping

[julian_k]

Hi,

I recently tried to set a string variable in my process instance, but the string of 500 characters was unable to insert due to a SQL exception regarding the column length being too short. I am using PostgresQL and the jbpm_variableinstance table indicates that the stringvalue_ column can only be 255 characters long. I then reviewed the hibernate config for the class and found the following:

<hibernate-mapping default-access="field">
 <subclass name="org.jbpm.context.exe.variableinstance.StringInstance"
 extends="org.jbpm.context.exe.VariableInstance"
 discriminator-value="S"
 lazy="false">
 <property name="value" type="string" column="STRINGVALUE_" length="4000"/>
 </subclass>
</hibernate-mapping>

Anyone have an idea why my table is showing a length of varchar((255) instead of varchar(4000)? I have created the db via the ant task found in the jBPM 3.0 download.

Thanks,
Julian

[kukeltje]

maybe the ddl created by hibernate limits this to 255 characters. Look at the hibernate site and see if there is a known issue with these kinds of things.

Ronald

[julian_k]

I looked into, but could not find much. Strange thing is that the other columns with a length of 4000 were created properly. As a workaround I will run the following patch on the Postgresql DB for those interested:

ALTER TABLE jbpm_variableinstance ALTER stringvalue_ TYPE varchar(4000);