Unfortunately, Exolab's use of the JDO name has caused a lot of confusion in the industry. Many falsely assume Castor JDO supports the JDO standard. I recently heard the lead architects of several leading application server vendors make derogatory public remarks about JDO, only to discover they were referring to Castor. They thought that Castor supported the JDO standard defined in the Java Community Process. Vendors who have implemented the JDO standard are constantly encountering this market confusion. Many of their potential clients falsely assume that Castor JDO supports JDO.
Castor JDO does not support the JDO standard!
So true, so true. I now have the good fortune of working with a commercial JDO implementation that follows the Sun spec. I couldn't curse JDO loudly enough prior to this experience. Now that I'm using a stable, standard-compliant implementation, I am singing the praises of JDO.
My advice: spend the cash and buy a good JDO implementation. Hopefully after the Jakarta OJB project gets further along we'll have an OSS alternative.
1:04:18 PM 
|
