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 implementation
| protected boolean supports(Class clazz) {
| return (Date.class==clazz);
| }
|
The Timestamp is not recognized as Date from jbpm. So the implementation must
be changed to
| protected 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.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3920872#3920872
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3920872
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
