EJB vs JDO battle heats up, again
All three major application server vendors (BEA, IBM and Oracle) said "NO" to JSR 243 intended for JDO 2.0. All these vendors support EJB 3.0 with a simplified persistence model and think another persistence model is uncessary for J2EE. I mostly agree with this argument that we do not need several persistence options with J2EE to make this compelling for developers. Look at the persistence need from the actual customers and developers and provide that need in the persistence model. Be it either JDO or EJB .. To many half baked things in the J2EE menu does not look attractive .. let's decide on one that is fully cooked and serve's everybody's purpose ..
Here is an interesting serverside thread with all JDO supporters echoing their comments .. All EJB bashers are also active .. Hopefully the expert committee members for EJB 3.0 have kept their ears and minds open for these comments and I think they can turn these comments(EJB's current weakness) to EJB 3.0's strenghths ..
JDO has never taken off .. I'm not sure whether this will take off ever without the support from three major players. Atleast Oracle has shown some interests on JDO and has an early JDO 1.0 implementation but the big two (BEA, IBM) hate JDO.
It will be like the Object oriented databases .. always popular but very few usage in the real life. The main problem is the JDO folks does not fully understand the relational technology that many enterprise has invested. However JDO will probably remain as a niche technology in its own world with its niceties and limitations like the object oriented databases.