Meaningless Drivel is fun!*
The moose likes Object Relational Mapping and the fly likes Best Practices for JPA Generated Keys Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCA/OCP Java SE 7 Programmer I & II Study Guide this week in the OCPJP forum!
JavaRanch » Java Forums » Databases » Object Relational Mapping
Bookmark "Best Practices for JPA Generated Keys" Watch "Best Practices for JPA Generated Keys" New topic
Author

Best Practices for JPA Generated Keys

Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 16160
    
  21

I've been working with Apache OpenJPA and a lot of what I do involves tables with generated integer keyfields. One of the problems with them is that since they're only generated when the backing store object has been created, the actual identity of the record is only available by retrieving the generated key.

For brute-force batch, I've been doing this:


However, I'm trying to use Spring, and the Spring equivalent goes something like this:


The problem here is that Spring is wrapping the entire method as a transaction, so the record hasn't been committed until after the return and thus no key is retrievable from within the method.

I want the save() method to be totally self-contained, but I'd rather not have to make it work by writing manual transaction code if I can avoid it.

Does anyone know a nice clean solution?


Customer surveys are for companies who didn't pay proper attention to begin with.
 
Don't get me started about those stupid light bulbs.
 
subject: Best Practices for JPA Generated Keys