Comments on: JDO is Deprecated http://blog.kischuk.com/2005/03/04/jdo-is-deprecated/ Just another WordPress.com weblog Wed, 19 May 2010 15:39:28 +0000 hourly 1 http://wordpress.com/ By: Anonymous http://blog.kischuk.com/2005/03/04/jdo-is-deprecated/#comment-48 Anonymous Mon, 07 Mar 2005 12:01:36 +0000 http://rkischuk.wordpress.com/2005/03/04/jdo-is-deprecated/#comment-48 JDO is far from dead, regardless of what JBoss and Oracle want. It will continue to be developed under Apache, and Sun has stated that there will be future revisions of the specification as needed. Given these facts, and the fact that JDO 2 already has features that won't be in EJB 3 until one or more spec versions down the road, I think JDO has a long and healthy future. In addition, you might want to rethink your opinion on ease of migration. I know at least two major JDO vendors -- SolarMetric and Versant -- have both stated that they will support concurrent access to both the JDO and EJB 3 APIs in the same application, even on the same object instances! That is as perfect a migration path as you can get. If I were recommending something to clients, I would put JDO at the front of my list. JDO is far from dead, regardless of what JBoss and Oracle want. It will continue to be developed under Apache, and Sun has stated that there will be future revisions of the specification as needed. Given these facts, and the fact that JDO 2 already has features that won’t be in EJB 3 until one or more spec versions down the road, I think JDO has a long and healthy future.

In addition, you might want to rethink your opinion on ease of migration. I know at least two major JDO vendors — SolarMetric and Versant — have both stated that they will support concurrent access to both the JDO and EJB 3 APIs in the same application, even on the same object instances! That is as perfect a migration path as you can get. If I were recommending something to clients, I would put JDO at the front of my list.

]]> By: rob kischuk http://blog.kischuk.com/2005/03/04/jdo-is-deprecated/#comment-47 rob kischuk Sat, 05 Mar 2005 10:49:28 +0000 http://rkischuk.wordpress.com/2005/03/04/jdo-is-deprecated/#comment-47 Notice I said POJO. EJB 2.1 is an option if and only if you're running in an app server with an EJB container. I was asked about containerless persistence, so EJB is out. Notice I said POJO. EJB 2.1 is an option if and only if you’re running in an app server with an EJB container. I was asked about containerless persistence, so EJB is out.

]]> By: Phillip Rhodes http://blog.kischuk.com/2005/03/04/jdo-is-deprecated/#comment-46 Phillip Rhodes Sat, 05 Mar 2005 01:07:58 +0000 http://rkischuk.wordpress.com/2005/03/04/jdo-is-deprecated/#comment-46 Just use EJB 2.1 CMP Entity Beans. They work, and there is a standardized specification, with multiple competing implementations that span every range of price, maturity and stability. And presumably there will be a clearly defined migration path from EJB 2.1 to EJB 3.0 when it comes out. Just use EJB 2.1 CMP Entity Beans. They work, and there is a standardized specification, with multiple competing implementations that span every range of price, maturity and stability. And presumably there will be a clearly defined migration path from EJB 2.1 to EJB 3.0 when it comes out.

]]> By: Patrick Peak http://blog.kischuk.com/2005/03/04/jdo-is-deprecated/#comment-45 Patrick Peak Fri, 04 Mar 2005 15:44:59 +0000 http://rkischuk.wordpress.com/2005/03/04/jdo-is-deprecated/#comment-45 I don't know too much about the JDO saga, having many years ago started to follow the Hiberante path. I do however well more Hiberante developers to the fold. :) Any, as Howard Lewis Ship says, "Results, not Standards". I don’t know too much about the JDO saga, having many years ago started to follow the Hiberante path. I do however well more Hiberante developers to the fold. :)

Any, as Howard Lewis Ship says, “Results, not Standards”.

]]>