[jbpm-issues] [JBoss JIRA] Commented: (JBPM-2018) StringInstance hbm configuration column length of 4000
[
https://jira.jboss.org/jira/browse/JBPM-2018?page=com.atlassian.jira.plug...
]
Thomas Diesler commented on JBPM-2018:
--------------------------------------
Julian says:
Just to confirm, if I modify the SOA bpm_orchestration1 sample to have a
270 character message, I see:
org.h2.jdbc.JdbcSQLException: Value too long for column STRINGVALUE_
exceptions, so I will be able to verify a fix. Unfortunately, the "easy
way for projects to build/test the SOA platform" is still a few weeks
away (at least).
StringInstance hbm configuration column length of 4000
------------------------------------------------------
Key: JBPM-2018
URL: https://jira.jboss.org/jira/browse/JBPM-2018
Project: JBoss jBPM
Issue Type: Bug
Affects Versions: jBPM 3.2.2
Reporter: Kevin Conner
Assignee: Alejandro Guizar
Fix For: jBPM-3.2.5.SP1, jBPM 3.2.6 GA
The reason for the discrepancy in the generated DDL files appears to be a conflict
between the hibernate definitions for HibernateStringInstance.hbm.xml,
StringInstance.hbm.xml and (potentially) JcrNodeInstance.hbm.xml.
Each of these VariableInstance subclasses map entries onto the JBPM_VARIABLEINSTANCE
using the same field, STRINGVALUE_, but only StringInstance.hbm.xml specifies the length.
The length is obviously being ignored when the DDL files are created as the
HIbernateStringInstance.hbm.xml is being loaded first.
--
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