I asked for applicationContext.xml, and I get a mysql log... well, near enough :)
From your last mail I understand you have the same problem if you use
the mysql command line client. Makes me wonder why you thought the problem had to do with Hibernate in the first place (let alone Tapestry, for this Tapestry mailing list this has been OT for a while now...). So generally, your sql statements never get committed... which is weird, because by default, mysql starts new connections with autocommit enabled. If you connect to mysql from the command line and do select @@autocommit; what do you get? About your Hibernate configuration, since you use Spring anyway, I would recommend you use Spring for the datasource setup, makes it easier to switch, plus it makes sense (to me, anyway) to have it in the same place as the SessionFactory. Oh, and although the classname you use for the jdbc driver still works, since the mysql connector/j provides backwards compatibility in this respect, nowadays people tend to use "com.mysql.jdbc.Driver" because of a name change four years ago. lutz --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
