Blogging Roller

Carlos says that, right now, the Hibernate persistence framework is a better choice than Jakarta OJB. He also criticizes Jakarta OJB for it's emphasis on JDO.  I have to agree with his assessment of Hibernate vs. Jakarta OJB, but I don't agree 100% with Carlos on JDO.

Carlos does not like JDO, but like it or not JDO is the standard Java persistence API.  Currently, there are only a few small vendors supporting JDO (SolarMetric, SignSoft, and PrismTech to name a couple), but someday JDO could become the defacto standard.  If that happens, then support for the JDO API will a very important feature.  For that very reason, I wanted to use Jakarta OJB in my WROX JSP chapter on database access.  However, I found that the Jakarta OJB implementation of JDO was just not ready for prime-time. I wanted to use an open source framework, so I decided to use Hibernate instead. Plus, the Hibernate docs are very nice.

Now, it has come out that (apparently) the Jakarta OJB implementation of JDO contains some stolen code.  I guess that means than an open source version of JDO is not going to happen, at least not in the near future.

I can't speak about the technical merits of JDO.  I don't know enough about JDO to compare JDO vs. any other persistence API.  Perhaps somebody who does (Carlos?) can break it down for us.