I need to do some custom JDBC code after I call save on an object (since I'm implementing my own type of lazy load).

I'm within a session bean transaction.

I then call session.save(obj);

After that call, I then use the session.connection() to execute some update statements using JDBC. The updates update fields of the table that obj is mapped to.


Once the transaction completes, I see the SQL log from Hibernate, but my custom JDBC statements are not being sent! I've put my own logging to make sure my JDBC code is being executed, and it is.

I've doing a connection commit and a session close after my custom statements, but that just causes errors.

Why would Hibernate ignore my statements? Any ideas on how to force my SQL to be executed?

session.flush seems to be doing it for me, if I call it right after my SQL code

I don't understand this though since I do call session.flush later in the method...

as you said, you're getting the connection and doing your statement alone... so please don't say hibernate is not doing your job.

What you should try is doing it in 2 times:
1- getting session, start transaction, getting mapped object, modifying or instanciating a new one + commit (then maybe discard this first session)
2- (getting another clean session if you have discarded the 1rst) + getting jdbc connection + prepared statement + commit.


try it