Comments on: Hibernating with WebSphere and a non-journaling DB2/400 system

By: Daniel

Daniel — Tue, 12 May 2009 22:21:04 +0000

I enclosed it by <h;code> tags!

..anyway, properies like these:

hibernate.connection.isolation=0
connection.autocommit=true

By: Daniel

Daniel — Tue, 12 May 2009 22:16:56 +0000

Oh sorry, maybe the XMl snippet was parsed by the renderer.
I meant these two XMl entries:
0 true

I see your point now, it is DS configuration as set by WebSphere, not Hibernate.

By: Mike

Mike — Mon, 11 May 2009 16:48:58 +0000

Your XML tags didn’t show up, so I’m not sure exactly what tags you are asking about. Setting the isolation level and auto-commit in the hibernate properties files don’t affect what settings you have when using an application server datasource. The datasource is configured in WebSphere and it wouldn’t get along with Hibernate from the perspective of agreeing on how transactions should ( or shouldn’t in my case) be handled.

I thought it was odd, too, but had many conversations on the mailing lists and forums and found that it just wouldn’t work ‘out of the box’.

There might be a much more simple way now.

By: Daniel

Daniel — Mon, 11 May 2009 03:23:47 +0000

Thanks Mike, it certainly helped me as I am in the same situation you were in before.

I am a newbie to Hibernate so please excuse my naievity; one thing I couldn’t understand is why you felt you need to override the default behavior ( extending DB2AS400DataStoreHelper) in order to set the isolation level and auto-commit properties when you could’ve achieved this – I think!- by having the following XML in the config file:

true
0

Wouldn’t that achieve the same? What I am missing here?

Thanks again..

-Dan

By: Mike

Mike — Wed, 21 May 2008 22:56:00 +0000

I simply made a jar with my helper and added it to the classpath of the application server instances that needed access to it.