I added "hibernate.connection.autocommit=true" to my hibernate.properties and that fixed it...

So I assume Spring by default does no Session/TX handling, unless I use the HibernateTransactionManager or do programmatic transaction handling...
One last question, to get back to Tapestry - is Spring's OpenSessionInViewFilter going to work with Tapestry without limitations?
I see all these posts about Tapernate and others, but I'm not sure whether OpenSessionInViewFilter will work...

Thanks,

MARK



Mark wrote:
Lutz Hühnken wrote:
I asked for applicationContext.xml, and I get a mysql log... well,
near enough :)
Sorry, I thought what I had found in the mysql log (the "set autocommit=0, no "commit" call and explicit "Rollback" call issued by Hibernate at shutdown) changed things a lot, but maybe not.
From your last mail I understand you have the same problem if you use
the mysql command line client.
No, the command line INSERT does make it, the records just don't get picked up by Hibernate...
So generally, your sql statements never get committed... which is
weird, because by default, mysql starts new connections with
autocommit enabled.
No, only the ones coming from my webapp do not get committed.

If you connect to mysql from the command line and do
select @@autocommit;
what do you get?
I get "1"
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.
Ok, thanks, I changed that.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to