This week's book giveaway is in the Agile and Other Processes forum.
We're giving away four copies of The Little Book of Impediments (e-book only) and have Tom Perry on-line!
See this thread for details.
Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

JDO's Future Versions and Standardization.

 
Gregg Bolinger
Ranch Hand
Posts: 15304
6
Chrome IntelliJ IDE Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am usually a little bit leary 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...
 
Craig Russell
Author
Greenhorn
Posts: 28
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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...
 
Gregg Bolinger
Ranch Hand
Posts: 15304
6
Chrome IntelliJ IDE Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Craig Russell:
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.



That's good to hear. Thanks for the info.
 
David Jordan
Author
Ranch Hand
Posts: 66
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I was going to say essentially the same as Craig. Since JDO 2.0 mainly is standardizing the OR mapping, which is info only in the XML metadata files, and we are adding new query capabilities, I doubt any code compliant with JDO 1.0.1 will not work with JDO 2.0.
As Craig stated, JDO was not a fresh new spec, new idea that had not been dealt with before. We learned quite a bit from past APIs like ODMG and also some of the other OR APIs. We also did not rush a spec out in a year, we took 2 years to work on the spec and a year of implementation work both inside and outside Sun. JDO 1.0.1 mainly provided some clarifications and fixed a few specification bugs, but I cannot recall anything that got broken between 1.0 and 1.0.1.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic