Hi Robert, > > Greetings, > > I was wondering if there was a JDO implementation in the > planning stages.
OJB provides a plugin to the JDO reference implementation. By using this plugin you can write JDO compliant applications running against the OJB O/R mapping. See here for a sample application: http://jakarta.apache.org/ojb/tutorial4.html. The OJB projects is also planning to provide a clean room JDO transaction manager on top of the existing OJB layers. > I know, you are probably going to answer, "Go look at OJB." > However, to face reality, OJB was started and an OMG data > mapping implementation. That's not correct. OJB started to write a generic O/R mapping tool that provides multiple "personalities" or APIs. > It is far too big to be warped into a > world class JDO implementation. Not correct. Have a look at my OjbStore Plugin. It consists of 5 classes and 1 exception! And still provides full JDO functionality (by pluggin into JDORI)! > The code volume alone is > rather staggering. not correct. It has a cleanly designed layering. It is designed to build high level transaction managers like ODMG and JDO on top of its core API. It was build with JDO in mind! The existing ODMG layer is in fact quite thin! > Hence the reason I suggest that Jakarta > start a project into developing a clean, fast, and > �ber-compliant JDO implementation. Id rather suggest to join efforts with the OJB team. We have even started to talk with SUNs JDO team to join efforts... cheers, Thomas > Thoughts? > > -- Derisor > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
