This post originated from an RSS feed registered with Java Buzz
by Marc Logemann.
Original Post: No-Votings for JDO2 on JCP
Feed Title: Marc's Java Blog
Feed URL: http://www.logemann.org/day/index_java.xml
Feed Description: Java related topics for all major areas. So you will see J2ME, J2SE and J2EE issues here.
I resisted some days now but i cant stand it any longer and i have to comment on that issue. Especially on some of the zillion comments on TSS.
First, i find it very funny how Bill Burke, JBoss Chief Propoganda Officer, tries to do good for the reunion of the two persistence specs. He does it in such a subtle way, that even hello-world java programmers get his intentions quickly. Basically he is saying that JDO2 spec is not good for the merger of the two persistence specs (JDO2 and EJB3) and we JDO users should simply wait about 30-67 months for EJB3, a spec that will not be a superset of JDO2 but a subset for a lot of scenarios. In the meantime, we JDO users will stop programming at all. Remember, its for the good of the java community.
Another interessting note from Bill is that JDO2 has no users yet, so why complaining? It seems that Bill knows the JDO market as good as he knows the AOP area (he was corrected by AOP experts in some TSS threads about 200 times). The point that the migration from EJB2 to EJB3 will be a rewrite, whereas the migration of JDO1 to JDO2 will be technically a refinement doesnt bother him too much.
Everyone trying to argue that this whole No-Voting is not political, will most likely also believe that IRAQ had weapons of mass destruction. The whole things is so funny, lets recap a little history of JDO and EJB specs.
- a few years ago, we had EJB1 and a lot of proprietary persistence specs
- then JDO1 was created as first standardized POJO Persistence spec
- a lot of users joined JDO because EJB1 and EJB2 totally failed in persistence
- most vendors, mainly the ones with appServers, tried to boykott JDO from the beginning
- 2 years ago, even the most fanatic EJB supporters understood that EJB persistence was and is crap
- a lot of people created a new EJB persistence spec, based on ... POJO.
- now the vendors try to kill JDO again, this time with the argument that there will be a POJO persistence soon (of course they dont say it this way, they use political slang)
This is a very roughly summary but thats how it is. Now everyone including me is wondering why on earth should JDO2 violate the agreement to work together on one persistence spec. The migration to one spec will be offered by most JDO vendors. Most of them, including Solarmetric, Signsoft and others, announced to support both specs in the future. So the JDO users will get a chance to migrate smoothly (more or less).
I am sure that the big players can easily kill JDO2 inside the JCP, but if this will happen, the java community will loose the faith in the JCP and will considering other standard bodies in the future. Especially Sun should be aware of the possible reputation damages of the JCP. At this point, noone answered the simple question how JDO2 will be counterproductive for the java community. And if you look at the comments on TSS, it seems that a big majority of the community thinks exactly the same way.
Previous Topic
