I posted the following on the Persistence/JBoss forum, but maybe it suits better here.
When trying to move to JBoss 4.0 I ran into a snag. ejb-deployer.xml in the deploy directory contains something that is probably not standard SQL: create table TIMERS ( TIMERID varchar(50) not null, TARGETID varchar(50) not null, INITIALDATE timestamp not null, INTERVAL bigint, INSTANCEPK other, INFO other, constraint timers_pk primary key (TIMERID) ) This causes errors at JBoss startup. First of all, INTERVAL is a reserved word and MySQL barfs on it. Secondly, 'other' is not a type known to MySQL. Changing INTERVAL into TIMER_INTERVAL and 'other' into 'text' (as I had no clue what to change it into) seems to fix the problem. Or did it? Now I get a "Hibernate lazy instantiation problem" when I try to fetch my objects from the database through Hibernate. I don't get that problem with JBoss 3.2.5. What I did notice was that JBoss 4.0 came with its own hibernate2.jar, so I didn't copy it into the lib directory. I did copy the others related to Hibernate though. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3849562#3849562 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3849562 ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
