]
Ronald van Kuijk commented on JBPM-443:
---------------------------------------
It can be solved by jbpm afaict by adding an explicit type in the hibernate files to force
hibernate to use a specific sql type and not have it be dependent on the dialect. But I
might be wrong and that adding this type only works for MySQL and makes other db's
behave worse. Only option is testing
JPBM does not work with MySQL 5.0
---------------------------------
Key: JBPM-443
URL:
http://jira.jboss.com/jira/browse/JBPM-443
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM 3.0, jBPM 3.1, jBPM 3.0.1, jBPM 3.0.2, jBPM 3.0.3, jBPM 3.2
alpha 1, jBPM 3.1.1, jBPM 3.1.2, jBPM 3.0.4
Environment: Windows XP, Mysql 5.0 beta2, JBPM 3.0
Reporter: Ravi Prakash Reddy Ummadi
Assigned To: Tom Baeyens
When JBPM is used with MySQL 5.0, the process is skipping the intermediate steps in the
process definition.
The behaviour is unpredictable. The same works fine with MySQL 4.1 and other databases.
The problem may be in DB scripts ( DB scrips run fine though) or .hbm.xml files .
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: