This post originated from an RSS feed registered with Java Buzz by Marc Logemann. Original Post: Hibernate or KodoJDO Feed Title: Marc's Java Blog Feed URL: http://www.logemann.org/day/index_java.xml Feed Description: Java related topics for all major areas. So you will see J2ME, J2SE and J2EE issues here. Latest Java Buzz Posts Latest Java Buzz Posts by Marc Logemann Latest Posts From Marc's Java Blog

I am on the way developing a very small J2SE Application for a customer which has potential to grow and to be sold to some more customers in the future. I started this thing some time ago and will continue with it these days. Back then i used plain SQL which should be replaced because i dont like to see this low-level stuff anymore.

I have recently done some JDO based projects and now the big questions appears. Should i stick with a JDO Implementation like KodoJDO or should i try out Hibernate. There is one requirement for the persistence solution, it should be cheap, because this project is not a multi million dollar one. Of course hibernate is free, but Kodo also only costs about 600 (price for referencing being a Solarmetric customer) bucks, so this is not the point.

I dont want to reanimate the JDO vs everything else debate here, its just about the product capabilities. I know Kodo is quite complete when it comes to mapping and it has some neat Frontend tools for developers. I am wondering if Hibernate can compete here. Another issue is documentation, i dont know how good Hibernate is here. I was burned by open source documentations several times before and the 150 pages of PDF documentation of Hibernate is ok, but doesnt impress me too much. Kodo documentation is about 3x times as big.

I think both projects are quite up-to-date when it comes to adhere to recent specs, because both of them have seats in the JCP groups. Hard decission and i will need some time to think about it.