-
1. Re: Process Variables stored as Date have problems...here's
camunda Feb 1, 2006 3:56 AM (in response to costeen)OK, I have the same problem but has not fully understand this message.
After some investigation I understand the problem:
Some Hibernate Dialects (HSQL, Oracle9, ...) return a java.sql.Timestamp, instead of a java.util.Date. That's OK, because Timestamp is a subclass of Date.
But because of the DateInstance implementationprotected boolean supports(Class clazz) { return (Date.class==clazz); }
The Timestamp is not recognized as Date from jbpm. So the implementation must be changed toprotected boolean supports(Class clazz) { // fixed Bug with jbpm and Oracle // see http://www.jboss.com/index.html?module=bb&op=viewtopic&t=70042 return (Date.class.isAssignableFrom(clazz)); }
Then it works fine. -
2. Re: Process Variables stored as Date have problems...here's
camunda Feb 1, 2006 3:57 AM (in response to costeen)But I have wondered how this Bug made it into 3.0.2....
I hope, it will be fixed with 3.1? -
3. Re: Process Variables stored as Date have problems...here's
koen.aers Feb 3, 2006 7:25 AM (in response to costeen)It is fixed in 3.1. Thanks for reporting anyway.
Regards,
Koen -
4. Re: Process Variables stored as Date have problems...here's
kukeltje Feb 3, 2006 2:16 PM (in response to costeen)I'm pretty sure I once changed this, but It could have been on the trunk and not the 3.0 branche. In that case this bug has been there from the start of 3.0. If it was not even on the 3.1 branche than I'm totally flabbergasted
-
5. Re: Process Variables stored as Date have problems...here's
tom.baeyens Feb 3, 2006 3:10 PM (in response to costeen)today, i checked head and there the fix was applied.
regards, tom.