Subject:   JDO thoughts
Date:   2002-12-18 01:29:47
From:   anonymous2
Response to: JDO thoughts


Well, of course I don't really know much about what really went on behind the scenes during the specification process for JDO. From checkin the JCP page for JDO, it seems like you were on the Expert Group panel, so I'd be curious to hear what that was like, from you.

Again, from the the JDO JCP page on, the JDO expert group includes the following list of large software companies, (many with pre-existing data persistence tools) forming the majority of the JDO Expert Group membership.

Ericsson Inc.
Informix Software
Rational Software
Sun Microsystems, Inc
Silverstream Software
IONA Technologies PLC
Objectivity, Inc.
Secant Technologies, Inc.
Software AG
Versant Corporation

David Jordan, author of the above article, was Ericcson's representative.

A quick overview of the JDOCentral Vendors include:

FastObjects, Inc - "wholly owned subsidiary of Poet Software GmbH, Hamburg, founded in 1993"
products include fully ODMG/OQL support in C++ and Java, as well as JDO - seem like mature products

ObjectFrontier, Inc. - "ObjectFrontier was founded in 1997 with offices in Atlanta, USA and an R & D Lab in Chennai, India."
They say " ObjectFrontier specializes in persistence management for enterprise applications, providing persistence engines, O/R mapping and caching solutions."
Their earlier product: FrontierSuite J2EE version 3.0, new product: in FrontierSuite JDO

SolarMetric Inc. - "is a global company with corporate headquarters in Washington, D.C., USA. [..] founded Solarmetric in 2001. The core technology team has been together since 1997"

Versant, Inc. - "Since the company’s founding in 1988, Versant Corporation (NASDAQ: VSNT) has led the industry in providing highly scalable and reliable object management solutions for complex, enterprise-level systems."
Previous product: Versant Developer Suite (VDS) 6.0, "is a 6th generation object database."

Hemisphere Technologies and Libelis were founded in 1999 and 2000, respectively. I couldn't figure out when Object Industries was founded.

Clearly, it is desireable to have a specification written by people who are experienced in the appropriate domain, and those people will often be involved in other, related businesses. The above list of Expert Group companies, however, seems like overkill with respect to simply ensuring that experienced viewpoints are part of the process, and seems dangerous with respect to the potential for biased architectural decisions.

Again, it would be great to hear from you, Robin, your impressions of the JDO spec development process, in particular, why is it that the JDO reference implementation isn't as useful an implementation of the JDO spec as, for example, Apache Tomcat, the Servlet spec R.I. is a useful form of the Servlet spec. One hopes that it's just a matter of time, but...

-David F.

Full Threads Oldest First

Showing messages 1 through 1 of 1.

  • JDO thoughts
    2002-12-20 03:16:15 [View]

    Hello again David,

    Yes, I am a member of the JDO Expert Group. However my membership was only ratified about 6 months before JDO was submitted to JCP for final approval, at which stage the first Proposed Final Draft was already published. I had input on usability, from a non-Vendor's perspective, but the key architectural decisions had been bedded down by that stage. Someone who could give a better impression of any "undue influence" on these decisions would be David Jordan, author of the "Castor JDO - Simply False Advertising" article, as he was there from the beginning.

    Versant and FastObjects were the vendors I had in mind as having pre-existing products in the space. I'm not sure what FrontierSuite for J2EE comprised. The rest are companies which may, I suppose, have had experience implementing aspects of the ODMG spec in some past life!

    To be approved a JSR must provide the specification, the Toolset Compatibility Kit (TCK) tests, and a Reference Implementation (RI). The RI needs to be functionally correct so that it can be used by Vendors to identify the correct behaviour of an implementation.

    It happens that Tomcat is a reference implementation that is so good it is also widely used as a servlet container in real web applications. Unfortunately Sun Microsystems was going through the pain of the current downturn in IT revenues at the time that the JDO RI was being implemented. As a result the amount of resource dedicated to that project was significantly reduced. Finally, the presence of so many commercial implementations in Beta at the time the RI was under development meant that there was no scope for the RI to become the de-facto standard, even if additional resource had been made available.

    Hence we have an RI that is used by JDO Vendors to verify the functionality of their products, but which is generally not employed by JDO Users.

    Happy Christmas!

    Robin M. Roos