I have an email service that I need to run as part of a transaction.

i.e. modify object, save, send email, (if all is good) commit transaction.

If the email fails however I don't want to commit the transaction; but I also want to be sure the db transaction will commit correctly.

can you do something like:

myPojo.save()
session.flush ??
// at this point any HibernateExceptin would have happened ??
doEmail() // if email fails.. throw exception so commit does not occur.. and rollback
session.commit();



Is this correct? Or is there someother way to do this?

Thanks

Troy

in short. Will the flush effectively allow you to verify the success of the model changes to that point.. while still allowing for a commit/rollback to follow.

yes after a flush you can continue and choose to commit or rollback.

Note that flush is automatically executed, you generally don't need to call it...

I want to manually do the flush so I can verify that the updates/deletes/inserts etc of the transaction thus far will execute correctly (similar to committing), but still allowing for a rollback of the datbase changes if the email service fails. I am not sure if I have this right in thinking the flush will 'throw' as would a commit if some constraint failed or something