[
https://jira.jboss.org/jira/browse/JBPM-2018?page=com.atlassian.jira.plug...
]
Alejandro Guizar resolved JBPM-2018.
------------------------------------
Fix Version/s: jBPM-3.2.5.SP1
jBPM 3.2.6 GA
Resolution: Done
Solution committed to 3.2.5.SP branch in r3792, and merged into trunk by Thomas in r3795.
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