Newcomer added that Iona had made a negative vote more as a procedural response. "The nay vote on JSR-243 was done to cause Sun to decide which set of goals the JSR was supposed to be evaluated by," he said, noting that Sun was the specification lead on the JSR. "Now that the situation has been clarified we have voted in favor." Rod Johnson, a London-based enterprise Java architect, J2EE (Java 2 Enterprise Edition) consultant and author, expressed his dismay over the situation."I think the confusion [and politics] around JDO/JSR-220 is unfortunate for the cause of O/R [object-relational] mapping on the Java platform as a whole," Johnson said. "Its good to see that the EJB expert group finally recognizes the value of POJO persistence, and that persistence should be separate from the EJB container. So theres a degree of convergence."However, there already was a POJO persistence specificationJDOand I think it would have been better to work toward improving that to satisfy all users, rather than to begin a new effort. A lot of excellent work has been done on JDO 2.0, which is a big step forward and looks more mature than JSR-220. I think its in the interests of the Java community for JDO 2.0 to be ratified." "I hope the JCP executive committee reconsiders its no vote on JDO 2.0 in light of the nearly 1,000 developers supporting the JDOCentral.com petition," said Rick Ross, president of Javalobby.org. "The real problem, however, is the wholesale failure of Java developers to join the JCP, vote in Executive Committee elections, and hold EC members accountable for their choice through the democratic processes built into the JCP charter. Only 221 of 755 eligible JCP members voted in the 2004 JCP EC electionresulting in a 29.3 percent voter turnout that is even worse than American presidential elections. "[Each of] the 221 votes represent just one for every 13,500 Java developers, if we accept Suns estimate of 3 million Java developers. Its very difficult to regard these 221 votes a quorum that allows Java standards to be considered genuinely sanctioned by a community process. Id much prefer to see 10,000 or more developers chiming in to make choices that guide and bind the evolution of Java technology standards. Apathy in the democratic process leads to bad results. JDO 2.0 is in jeopardy largely because of apathy." Neelan Choksi, president of SolarMetric Inc., in Austin, Texas, said, "Since the vote was announced, the JCP EC, Sun and the EJB 3.0 and the JDO 2.0 expert groups have been doing the right things by communicating and working together to ensure that a positive vote takes place as soon as possible. I believe there will be a positive resolution to this issue." Check out eWEEK.coms for the latest news, reviews and analysis in programming environments and developer tools.