[URGENT] TaskInstance.isCancelled()==TRUE after creation

[david.trattnig]

Could anybody an idea why my TaskInstance is set to isCancelled==true after creation. At the assignment-handler the method taskInstance.isCancelled() returns false.

Then the hibernate query:

DEBUG [AbstractBatcher: 344] update JBPM_TASKINSTANCE set NAME_=?, DESCRIPTION_=?, ACTORID_=?, CREATE_=?, START_=?, END_=?, DUEDATE_=?, PRIORITY_=?, ISCANCELLED_=?, ISSIGNALLING_=?, ISBLOCKING_=?, TASK_=?, TOKEN_=?, SWIMLANINSTANCE_=?, TASKMGMTINSTANCE_=? where ID_=?
Hibernate: update JBPM_TASKINSTANCE set NAME_=?, DESCRIPTION_=?, ACTORID_=?, CREATE_=?, START_=?, END_=?, DUEDATE_=?, PRIORITY_=?, ISCANCELLED_=?, ISSIGNALLING_=?, ISBLOCKING_=?, TASK_=?, TOKEN_=?, SWIMLANINSTANCE_=?, TASKMGMTINSTANCE_=? where ID_=?
DEBUG [AbstractBatcher: 413] preparing statement
DEBUG [EntityPersister:1811] Dehydrating entity: [org.jbpm.taskmgmt.exe.TaskInstance#3]
DEBUG [pe.NullableType: 60] binding 'Approve Resource' to parameter: 1
DEBUG [pe.NullableType: 53] binding null to parameter: 2
DEBUG [pe.NullableType: 60] binding 'approver1' to parameter: 3
DEBUG [pe.NullableType: 60] binding '2006-03-31 14:27:58' to parameter: 4
DEBUG [pe.NullableType: 60] binding '2006-03-31 14:27:56' to parameter: 5
DEBUG [pe.NullableType: 53] binding null to parameter: 6
DEBUG [pe.NullableType: 60] binding '2006-03-31 14:27:33' to parameter: 7
DEBUG [pe.NullableType: 60] binding '3' to parameter: 8
DEBUG [pe.NullableType: 60] binding 'false' to parameter: 9
DEBUG [pe.NullableType: 60] binding 'true' to parameter: 10
DEBUG [pe.NullableType: 60] binding 'true' to parameter: 11
DEBUG [pe.NullableType: 60] binding '9' to parameter: 12
DEBUG [pe.NullableType: 60] binding '3' to parameter: 13
DEBUG [pe.NullableType: 53] binding null to parameter: 14
DEBUG [pe.NullableType: 60] binding '5' to parameter: 15
DEBUG [pe.NullableType: 60] binding '3' to parameter: 16

So Hibernate seems to bind the value false to the parameter ISCANCELLED. But the result in the database is "TRUE" or rather "0".


???no idea..

[aguizar]

TRUE is 0?? Do you have a (wrong!) query substitution in your hibernate config files?

[david.trattnig]

TRUE is 01 of course ;)

hmm, query substitution - I have not defined such a configuration and I don't think that this is the problem, because parameter 9 and 10 for example are inserted/updated correctly. The SELECT works for all parameters.

DEBUG [pe.NullableType: 60] binding 'false' to parameter: 9
DEBUG [pe.NullableType: 60] binding 'true' to parameter: 10
DEBUG [pe.NullableType: 60] binding 'true' to parameter: 11

In the hibernate query-log there is no update after this one.

Thank you so far..

[david.trattnig]

No I've inserted

<prop key="hibernate.query.substitutions">true 1, false 0</prop>

into my hibernate-config, but no change with MySQL5.0.

In MySQL4.1 it works!

[indraneela]

can we use other substitutions than 1 and 0 for boolean variables

like
true -1, false 0

and store vlaues -1 for true and 0 for false in database .

i have been trying to do this because in my application, the client is insisting on using -1 for true and o for false in the database.

is it possible, can some one help me.I am using mysql 5

[kukeltje]

This is a hibernate issue, so better as ik the forums there. (My answer would be that you need to configure it the way the DB wants it, not what the customer wants)