Subject:   JDO Is Awesome
Date:   2002-12-09 17:29:48
From:   anonymous2
As a user of an implementation of JDO specification from Sun (JSR-12), I'd have to say it is quite good. I am a little confused by all of the complaints about it in this thread. Can some one please explain why JDO is an inferior standard as it works very well for me? Has anyone done a real comparison of the two?

As a former Toplink user who watched Toplink prices go through the roof when sold to Webgain, I know the pain of using a proprietary persistence solution. Although Castor is free, I am not sure if I'll receive the same support levels as I have come to expect with Sun JDO where the standard provides me with many alternatives for getting support, training, etc.

Finally, the value of spec is seen in one last place - with where JDO vendors have brought the spec in the 8 months since it was released, it is amazing. The rate of innovation seems to be driven by a common spec and the many vendors (and open source projects) supporting the spec. It appears that Sun's JDO may have been late to the game but is catching up very quickly.

Full Threads Newest First

Showing messages 1 through 2 of 2.

  • Why Sun JDO is inferior
    2002-12-09 19:44:41  anonymous2 [View]

    I agree, JDO is awesome. It will solve business problems and will work very well for most users. However, the technology needed to modify the class files is a hack. This all relates the class mutilation (termed byte-code enhancement) in JSR-12. Again, most business users will not care, and the Sun JDO standard will work great as it does for you. However, most seasoned programmers will cringe over class mutilation (or implementing PersistenceCapable manually).
    • Why Sun JDO is inferior
      2002-12-10 13:47:43  chester8170 [View]

      Why would most seasoned programmers "cringe" over byte code enhancement?

      Solving business problems doesn't sound like a bad thing especially if I want to keep my job in this market.