Skip to main content

Three votes no on JDO

Posted by daniel on May 5, 2004 at 9:24 AM PDT

The JDO 2.0 JSR has been approved despite no votes from BEA, Oracle, and IBM.

It is interesting to read some of the comments offered in support of votes for and against this JSR that describes an extension to the JDO specification. It is reminiscent of what Jim Waldo calls the Highlander principle. Although he was referring to a different technology dispute, Waldo said that like in the movie, only one technology can live so all other technologies must die. The dissenting votes cited the work on EJB 3.0 and their concern that having overlap would be confusing. Other developers have said that having alternate ways of performing some tasks is important.

Voting in support of the JSR, Sun's comment was that "there is space for both JDO and EJB. I hope the
expert groups can cooperate to minimize any unnecessary differences in areas where they overlap. Whether or not JDO should be included in J2EE is an issue for a future J2EE expert group to debate."

BEA explained their no vote saying they "don't see how having another release of JDO, whose market acceptance is essentially constrained to use with object databases, can be explained in conjunction to similar enhancements being made in the EJB3 expert group. We are also concerned about taking JDO into new areas such as disconnected data set support until we better understand how ball of these solutions fit together."

IBM agreed that "In a context where the Java community is working to simplify J2EE, it is undesirable to produce multiple overlapping ways of programming the same function." Oracle also agreed that "JDO 2.0 overlaps with the work being done by the EJB 3.0 expert group to provide a lightweight persistence model. Having 2 specifications address the same problem space with different APIs, persistence and transaction semantics, mapping definitions and query mechanisms does not contribute to the effort of simplifying J2EE and making it easier to use. The direction of lightweight persistence being taken by the EJB 3.0 group will have tremendous appeal to mainstream enterprise Java developers, even those who are critical of the current Entity Bean model. Given the evolution of EJB 3.0 persistence, another independent standard for persistence is unnecessary and will add confusion to those looking to adopt J2EE technology."

Macromedia countered this response with a yes vote and a comment that "While undesirable overlap does appear to exist between JDO and other JSRs, the feedback we have long heard on this particular subject is that Java application developers prefer to adjudicate the overlap themselves rather than have the decision enforced for them by platform vendors. The community appears to desire a choice between persistence technologies even at the expense of the additional platform complexity and fragmentation that the overlaps between those technologies can cause."

Sun acknowledges that "If JDO did not exist, it might be a worthy topic for debate as to whether the Java community should invest in this area.[..] Given that JDO exists and has attracted significant interest from the Java community, I think it is appropriate to allow it to continue to evolve, based on the feedback and requirements from its users."


In
Also in Java Today
, Much of the advice you get on methodologies applies best when you are starting a project from scratch. Very often you are inheriting a project and can benefit from Robert Simmons' Seven Low-Cost Ways to Improve Legacy Code . He suggests that you use a stronger compiler and adopt a code formatter. He thinks you should go back through your code and make as many parameters and variables final as you can. You know all of that code you have commented out throughout your source files? Simmons says get rid of them. While you're at it, he wants you to remove anonymous inner classes and to replace listeners with weak listeners.

JBoss remains one of the most popular open-source J2EE application servers on the market today. In The Unofficial JBoss Performance Tuning Guide, "Firedragon" describes a list of procedures that one can perform to tune the JBoss application server. He writes that this "article focuses on one major areas in deploying web applications on the JBoss application server: performance tuning. There isn't a lot of consolidated information in this area, and the information presented here is through trial and errors and bits and pieces of information found on the JBoss forums and weblogs of JBoss developers."


Rory Winston opints to the JDO vote and a ServerSide discussion on the topic in JDO 2.0 vs. EJB 3.0?
in today's Weblogs . "If people want this kind of functionality and make that known, the vendors will capitulate. What is basically comes down to is: would you like to be able to use the functionality of Hibernate and similar frameworks in a standard way? And would you wish to participate in a process that defines this for future J2SE inclusion?"

"Never tell people how to do things. Tell them what to do and they will surprise you with their ingenuity." Perhaps it's odd to see this Patton quote in Malcolm Davis' blog Feature Oriented Programming and Design. Davis is reporting back from a talk he attended given by Dr. Don Batory. "For Generative design to work properly, requirements must focus on 'what not how'. 'How' things are to be implemented is a task for design. Requirements should be thought of as a set of features that provide benefit to the consumer. Dr. Batory mentioned that requirements are a big problem in software engineering. Anyone who has dealt with a government or big IT shops can comment on the problem. Even techniques like Use Cases can contribute to the problem when it drives requirements to individual function points."


In Forums today, John Mitchell reponds to the comment "Whether the ultimate client is happy or not, I don't know." Mitchell replies ". That's the saddest thing that I've heard so far in this forum. From at least the client's perspective, the purpose of a project is to fulfill their needs and desires and yet here is arguably a large system with lots of people involved but there's been no (clear) feedback about the success or not of the project."

"Know who you are" is the message on technical interviewing from invalidname. "Too often I've seen companies make hiring mistakes by not being honest with themselves about who they are and how they do things. For example, let's say your company is deadline-driven and subverts any process to make those dates. If an interviewee comes in and stresses that he or she values process, whether it be waterfall or XP, then that's not going to be a good match".

What happens when a company is over its head? In http://www.java.net/cs/user/forum/cs_disc/1158#4000"> Non-bargain companies bblfish reports " dealing with people immersed in problem above their current abilities. But there was an arrogance preventing them from acknowledging that. Perhaps the arrogance had got them into a situation where they could not but act that way, for fear of losing face or something similar."


In today's Projects and Communities , the JavaPedia explains GUI layout by a Layout Manager which will set your GUI "based on the rules the programmer has given combined with the amount of screen-space the user has given the application."

The JMCI project in the jddac incubator " provides a set of APIs for representing measurements about the physical world and for performing operations on these measurements."


In today's java.net News Headlines
:

Registered users can submit news items for the href="http://today.java.net/today/news/">java.net News Page using
our news submission
form
. All submissions go through an editorial review by news director
Steve Mallet before being posted to the site. You can also subscribe to
thejava.net
News RSS feed
.


Current and upcoming
Java Events
:

Registered users can submit event listings for the href="http://www.java.net/events">java.net Events Page using our href="http://today.java.net/cs/user/create/e"> events submission
form. All submissions go through an editorial review before being
posted to the site.


Archives and Subscriptions: This blog is delivered weekdays as the
Java
Today RSS feed
. All java.net members can subscribe to the email
updates for the site at the href="https://java-net.dev.java.net/servlets/ProjectMailingListList">
java-net Mailing Lists page. You must be logged in to subscribe
to
the javanet_Daily and javanet_Weekly lists. Also, once this page
is no longer featured as the front page of
java.net
it will be archived along with other past issues in the href="http://today.java.net/today/archive/">java.net Archive.