Hi,

just a question to see who is right ... I've judt read an article on jdocentral.com written by Marc Fleury about the adoption of JDO by JBoss.

.... (from jdocentral)
JBoss chooses Java Data Objects
...
According to Alexey Loubyansky, the author of JBossDO, At first, I planned to write our own framework for POJO persistence. I looked at Java Data Objects, Hibernate, OJB, a couple of others and decided to start with Java Data Objects. At least to have it as the base. And it is really a good spec. Thank you.
....

Last week at Javapolis and as I read somewhere else, Jboss seems to have adopted Hibernate as their persistence engine. (that's why Gavin joined Jboss Group).

Can someone clarify the situation ?

Thx

Alex was working on a JDO1 implementation, which has now been dropped. It is our intention to provide a JDO2 compatibility layer for Hibernate when JDO2 is adopted, assuming that the JDO2 spec satisfies our requirements.

We of course continue to concentrate upon our own APIs, since we still have much more flexible and elegant query facilities than JDO2 will have.

Gavin,

thx a lot for this fast answer. I'm now testing Hibernate inside a workshop. The purpose is to review and reengineer our persistence engine somewhere in 2004. I really appreciate hibernate (much more than the currently jdo implementation) but all my workshop participants claim that they prefer to start with jdo because of the possibility to change of vendor and that hibernate is not "standardized". My question is do I have to start with jdo now and swith to hibernate when it becomes jdo 2 compliant knowing that I want to minimize the code reengineering when passing from jdo 1 or current hibernate to jdo 2 ?

Thx for your opinion

This is our statement on Hibernate v JDO.

http://forum.hibernate.org/viewtopic.php?t=925411

Ask your friends:

If an open source project has an absolutely dominant "market share", and is the only solution supported by a major J2EE vendor, how is it not the standard? Struts is the standard web application framework for Java. log4j is the standard logging framework for Java. Hibernate is the standard ORM solution. Yes, there is JSF, JDK logging, JDO - but no-one uses that stuff, so they are not the real standards, are they?

Don't confuse the word "standard" with "Sun standard". I prefer de facto standards. ie. standards which came into common use because they worked in practice, not because some vendors sat down in a room together and produced a paper spec.

We built this project through collaboration with actual users, and continue to do so. This is in every way a superior approach, as you can see by the size of our userbase compared to the size of the JDO userbase.

Sorry if I sound a bit arrogant here, but I have been heavily burned by mindlessly adopting "standards" when they were not the right tool for the job (EJB, for example).

P.S. You can change "vendor" anytime you like, simply by forking the code.