Humm.. I always knew that tools like hibernate would come along with lot of problems. I mean, for the enterprise solution. I wouldn’t deny it for using in small projects, but for the serious ones the Udi Dahan’s article Object Relational Mapping Sucks must be considered. Also Brian Pontarali article series’ Hibernate Pitfalls should be reviewed and google would be consulted. 
I saw a friend working with hibernate and his loves for the tool was convincing. So I’ve learned something, did some test and I was horrified about how dare it make uses of Reflection
So, if your arguments doesn’t include the words “low, budget, small, tiny, quickly project solution” don’t come to me and say that this is the best thing in the world, probably you will be the most hated.
For the enterprise I don’t recommend it even if I’m keen on the hibernate’s idea and this doesn’t mean that I don’t recognize the professional job of this tool.
I’m not against Object Relational Mapping tools at all, for the application I architect I always build something similar. I think that people should take into account that any generic thing has a side effect to put on and people should always consider alternatives and be prepared to build your personalized mechanisms for enterprise solutions. If you got methodologies, spit on technologies!
I like to say that because if you don’t have a tool on your belt, why should you despise the skills that miss. Not every company will demand you solutions with Hibernate staff, not very project you demand you to build things from the scratch.
