This post originated from an RSS feed registered with Java Buzz by Michael Cote. Original Post: Thoughts on Specs: Feed Title: Cote's Weblog: Coding, Austin, etc. Feed URL: https://cote.io/feed/ Feed Description: Using Java to get to the ideal state. Latest Java Buzz Posts Latest Java Buzz Posts by Michael Cote Latest Posts From Cote's Weblog: Coding, Austin, etc.

We were switching from hand coded DAOs and had to pick a framework. We could have chosen EJB or JDO, but we chose Hibernate because it WORKS. Not only that, I don't have to worry about the implementation in different containers or licensing models. I made this point at the JDJ advisory board panel discussion at JavaOne and Ajit Sagar warned me I should be careful of choosing a single vendor implementation and that standards will protect my upgrade path and options. I asked him if I would have been better of implementing it the first time with EJB 1.1 Entity beans. EJB 2.0 Entity beans are the same as EJB 1.1 by name alone, and from what we're hearing about EJB 3.0, things are going to change radically again. Sorry, but I'll put my trust in the Hibernate team instead.