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.
4) In my opinion, it really doesn't matter whether Hibernate becomes a standard. The important thing is that it works and is an option among the variety of persistence framework out there. And the LGPL license is flexible. It might be prudent to create a layer that minimizes dependencies on a particular persistence product; so that your app is portable. XDoclet can do this very well. Pho
You could argue that Hibernate is the standard in real terms, if you accept that a standard is that which most people use. JDO may be Sun's prescribed way of doing things but Hibernate is much more mature, better supported and much more widely used. Since its inclusion into the JBoss group too its become more credible. Go with what works best - remember that Entity Beans, who's failings are very probably the reason why JDO and Hibernate are necessary, is a Sun standard too.
- Hibernate is a product and JDO is a specification - Hibernate is a VERY mature product - Hibernate is open source. - Hibernate is supported by JBoss Group. - Hibernate is well accepted by the community. - JDO is not so much mature in the O/R field. - JDO has mature and not so much mature implementations in the O/R field. - JDO is supported by many companies, SAP, Sun, bla bla bla. - JDO is at some level portable to any data store. - JDO has many open source O/R implementations. - JDO has ODBMS, File and XML data store implementations. It's probably that hibernate and Oracle Toplink support JDO in future, so working with JDO today will make easier to migrate at that time. [ March 20, 2004: Message edited by: Erik Bengtson ]
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com