Now you have a quality Object-Relational Mapping development tool and runtime, which also supports the JDO and EJB 3 standards.
The workbench includes tools for visual mapping of classes to relational tables, entity-relationships diagrams, db schema generation and migration tools, ad-hoc object query browser, performance profiling and monitoring, and full round-trip engineering between the Java object model and the DB schema.
And now it's all free and open source! You can download it from:
Versant was not able to sell this technology (ref: financial results are on public record). This was despite superior technology, being a public company so lowering the risk for corporate purchasers, and very resonable pricing (I've heard $3K).
The issue is that JDO has lost credibility. The high point was when Apache announced a JDO 2.0 project. It was a case of "wow" - this could mean that JDO finally takes off. THEN the first JCP vote... by mainly J2EE vendors.
After that, no amount of backtracking and revoting will recover from the fact that corporate
Versant is right to dump its JDO product - they still have great database techology so they should survive and prosper. If they can gain market momentum..
JDO is set to join betamax versus VHI, Windows versus Macintosh, etc as examples of how superior technology will always loose to market momentum...
Hi James Jdo has not lost its credibility.Still its a very good technology and is waiting for good implementors. EJB3 is very much similar to JDO2, if JDO would have lost its credibility then EJB 3 specification whould not be similar to it. Have you used JDO? Use it then put remarks. You can try open source implementations like JPOX. jpox.org
Failures are practice shoots for success.
What's happening with the JDO vendors is something very similar to what happened with the SOAP stack vendors (Cape Clear, Systinet, etc). The original implementations of the specification (JDO, SOAP, whatever) become less important as good open source implementation become available. In this case, Apache is producing a JDO implementation.
This means that JDO vendors are now entering the phase of the product lifecycle where then concentrate on other things (other data sources in the case of Xcalia, for example).
JDO certainly has enough critical mass to keep going ... even if the market momentum is now with Hibernate.
One intersting point.... if this open sourcing announcement had been made 18 months ago ... the future of Java persistence technologies would have been very different. It's a first class implementation of the best Java persistence specification available...