Theodore Casser
Code Poet
Theodore Casser
Code Poet
True. It is up to you (or your managers) to judge how important that is. Avoid knee-jerk choices, though: JDO object-relational mapping is not standardised, just the programming model, so your JDO applications are more locked-in than you might think. Hibernate has a momentum that isn't that much smaller than that of JDO, and it is in more powerful and flexible in a number of ways. Not coincidentaly, the tool has made a definite impact on the of JDO 2.0 and EJB 3 standards-in-progress.Originally posted by anitha lingam:
Moreover i learnt that JDO is a standard and it is portable while Hibernate is not.
JDO is standard, and supports object databases. Hibernate is more mature, has a query language (HQL) which is more powerful and quite intuitive if you know SQL, does not require bytecode processing, and allows you to disconnect an object graph, update it in another tier and later reconnect it to persist the update.What are the features available in Hibernate that is not available in JDO or vice versa.
They believe that JDO represents an inferior product, and I don't think Gavin King was very impressed with the way the JDO 2 expert group is going.Is it that developers started using Hibernate that they do not want to switch to JDO.
Peter den Haan | peterdenhaan.com | quantum computing specialist, Objectivity Ltd
Originally posted by anitha lingam:
Regarding the portability with datasources, my application requires data to be written from the database to flat files and vice versa. Can this be acheived by both Hibernate and JDO?
Originally posted by Peter den Haan:
[...] All three are quite similar.[...]
Co-Author of <a href="http://www.manning.com/bauer" target="_blank" rel="nofollow">Hibernate in Action</a>
Co-Author of <a href="http://www.manning.com/bauer" target="_blank" rel="nofollow">Hibernate in Action</a>