Meanwhile, an anonymous post to the Web log of Richard Monson-Haefel, an analyst for the Burton Group Inc. and enterprise Java expert, spelled out the frustration some developers are feeling regarding the vote. "The implications of a negative vote are much more far reaching," the anonymous post said. "Can any company trust the JCP to not screw them? Numerous companies, like mine, have invested millions of $s into JDO because the JCP voted it as a standard. My political capital in my company is currently shot because of this negative vote."Whats worse is that the features in the update were all driven from end user requests. If EJB 3 was here today and covered all of the features that were in JDO 2, that would be understandable. However, EJB 3 as it currently stands is a shell of a standard when compared to JDO 2 and it likely wont be available till 2006." Java creator James Gosling sounds off on Java futures. Click here to read the interview. Further, the anonymous poster said: "Microsoft shows you what the world would be like if there was only one standard for each technology. Why is the JCP insisting that there should only be one standard for persistence?" The anonymous poster ended the post saying dissatisfaction with the Java community could lead developers to Microsoft. "If the Reconsideration Ballot is not approved for JDO 2 or if JDO 2 is changed dramatically to meet the needs of biased vendors, this may be the straw that breaks my back. Java may very well be dead to me and where financially viable, I will start moving my development to .Net." Meanwhile, others said they expect the reconsideration vote to right the situation. Eric Newcomer, chief technology officer at Iona, said, "The controversy arose when the JDO committee submitted a specification draft that did not appear to align with the committees previously stated goals. Some might have interpreted this as an attempt by the committee to go beyond its charter, since the original charter stipulated the result to be a maintenance release, not a major functionality upgrade, as the draft appeared to be." And in some respects the confusion appears to have been interpreted as a POJO versus EJB situation, "but to me it seems like people were reading this into the situation based on their previous disposition toward one or the other," Newcomer said. Next Page: A procedural response.
"I am incredibly frustrated because the JCP implied that JDO would be a supported standard. In fact, the JCP approved the Early Release Draft of JDO 2 right before my company made a decision to purchase and I was happy that it passed. As such I approved the purchase of JDO technologies for my company. Then magically, a letter from Sun suddenly comes out changing the charter of both JDO 2 and EJB 3. Now, the JCP can take a minor update to an existing, popular standard and simply get rid of it because it is not in the best interest of biased vendors like Oracle and JBoss.