• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

JDO vs other persistence mechanism

 
Alok Sinha
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
can anybody let me know the pros and cons of using JDO over other persistence frameworks like hibernate?
 
Mike Farnham
Ranch Hand
Posts: 76
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
According to the authors, Hibernate is proprietary.
Proprietary meaning only supported by the makers of Hibernate.
Whereas, JDO, is interfaces that are currently being implemented by 14 different commercial vendors.
You can see this under the JDO thread.
Cheers,
mike
 
David Jordan
Author
Ranch Hand
Posts: 66
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
That's right.
Hibernate is proprietary from a single source.
JDO is a standard, gone through the Java Community Process, it is supported on relational databases by 15 or so vendors, so far.
O'Reilly has another book called Java Database Best Practices. It does not go into much depth, but it covers JDBC, EJB CMP, JDO, Castor, Hibernate. It was written by someone who has authored a SQL and MySQL book, so he comes from a primarily relational world. He actually is quite positive on JDO, especially compared to EJB CMP. The sections on Castor and Hibernate did not go into much depth, and I have not looked at Castor or Hibernate directly, but I did not see HUGE differences with JDO, except that it is a different interface, which is proprietary and specific to those implementations. I can also say that I have talked with people that felt they really got burned by Castor's level of support. They have switched to JDO and are happy about that decision.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic