This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I've made some of the unedited content from my book available on my website. One of the most popular links is about "How Hibernate Works", and I think it does a pretty good job at explaining how Hibernate manages the lifecyle of persistent objects. Forward this link to your team and have them read it. It should help make sense of things:
Isn't the whole state-ori�nted approach part of the EJB 3.0 persistence specification? I mean, don't these "Hibernate object states" apply to JPA providers in general rather than Hibernate in particular?
Build a man a fire, and he'll be warm for a day. Set a man on fire, and he'll be warm for the rest of his life.
Cameron Wallace McKenzie
author and cow tipper
I think that what we have seen over the past few years is a merging of the minds with regards to data persistence and Java applications. So, yes, I'd say that many of these concepts cut across most of the dominant persistence mechanisms that are being promoted today.