Do any of you remember JBoss JDO
What happened to that? What happened to that 2 year old announcement? The story is that at the time, we were heavily recruiting the Hibernate guys to join JBoss Inc. When they joined, we had a rethink on the JDO strategy. The Hibernate guys disliked the JDO specification for technical reasons. YOu'll have to talk to them, but I think they disliked the overall one-size-fits-all persistence architecture. There are other less obvious technical arguments, so please ask the HB crowd because I wouldn't be able to articulate it well. So that was one strike against going the JDO route.
Another one, was the business side of things. If you research the JDO market, you get a different picture of how healthy it is. 2 of the top 3 JDO vendors are public companies. Go take a look at their revenues. Strike Two.
Another thing to look at is number of downloads and forum/email traffic. We compared these to Hibernate and Hibernate dwarfed them(put together) by far. You don't want to enter a market that is much tinier than your current base. We then compared Hibernate downloads/forum/email traffic to our own CMP imp and found the traffic/downloads to be comparable. (We used to sell standalone CMP docs so we had a good solid comparison point). Strike Three, you're out!
Also remember, that the Oracle/Toplink guys had the same decision point. You'll have to ask them, but I bet they went through a similar exercise. Ask yourself this: Why would the top two POJO persistence solutions go the EJB 3.0 route? I think it boils down to (besides technical arguments) that there is a much better chance of adoption of our POJO persistence solution going the EJB 3.0 route and attaching to J2EE.
If you went to the EJB 3 BOF at JavaOne last year where Robin Roos tried to hijack our session, you would have heard customers like Goldman Sachs demand a clarification on the direction of persistence and that dual competing specifications were bad for Java.
All these arguments is why we take the position on promoting EJB3 and unifying the specifications. I know many of you think we do things just to piss people off, but, at least in this case, we thought things through before we decided on the EJB 3.0 route.
What I find *really* disturbing about the whole JDO/EJB3 debate is that the TSS Cause of the Month Club and the Bitter Bloggers are so quick to try and tear down the JCP. Proved to me how short thinking people can be sometimes.