That's interesting. I don't get that error. I'm running Seam and JBoss from CVS, but I can't imagine anything that would have changed that would cause that.
Hmm... You wouldn't happen to be on Java 6, would you?
Interesting indeed: I was running JDK 6.
Changed JDK for JBoss to 1.5 and it deployed fine.
As a double check I changed back to 6 (simply restarting the server with the ear still in the deploy directory): The error reappeared
So I guess you should change the import.sql anyway. It's an easy workaround for JDK 6 compatibility,
Yeah - very interesting. I guess something in JDBC 4.0 isn't entirely backwards compatible. I just wanted to make sure that was the issue before checking a fix. Thanks for finding that!
note, this looks more like a hsqldb and java 6 "incompability" than hibernate/seam vs java 6 incompability.
Shane said he thought it was due to a change in java.sql.Timestamp.