IIRC, if it got to the actual execution it was fine, this particular case was when you had bits of work queued up and then the add to batch failed in entity validation it ended up not throwing a SQLException at the time. I'm trying to see if that would still be the case. I'll concede that it's a bit of an unsupported use of things but we had a use case where we wanted to have oracle savepoint support.