One of the principles that we adhere to in the JDO expert group and Java in general is backward compatibility. We don't want major changes to invalidate what users have already implemented.
The fact that we're just releasing JDO 1.0.1 speaks for the fact that we mostly got it right in 1.0. No major changes were needed to make a highly portable, scalable, and usable spec. In fact, you might consider JDO 1.0 to be at a 4.0 level because all of the lessons learned by the authors of ODMG 3.0 were incorporated into JDO.
What we're considering for JDO 2.0 are usability improvements especially in the container/server environments and a specification for object/relational mapping. So if you start with JDO now, your code will still work with JDO 2.0 except you can change your metadata to the standard form when you like.
Originally posted by Gregg Bolinger:
I am usually a little bit leery of Specifications in such early stages. I know JDO has been worked on for several years now but it is only in Version 1.0. And in todays world where specifications are only standard until the next version, it's hard to commit to something.
STRUTS did it a little when they went from V1 to V2 (from what I could see with my limited knowledge of the technology). Hell, the Java Virtual Machine isn't even 100% backwards compatable.
I was wondering if anyone would care to comment on the possibilties of the JDO Specification having dramatic changes between now and Version 2. I realize that a lot of changes are for the better. But that even more so makes me just want to wait...