JDO Concerns

JDO is largely a very impressive specification. Some issues remain troubling, however.

Firstly, and most importantly, I'm concerned about adopting JDO wholeheartedly. I know from experience that any successful database is going to attract users who may not use java. They may find it very difficult to plug their excel-ODBC or php web pages on a JDO-created database.

Secondly, the issue of byte-code enhancement. In theory, there's nothing wrong with byte-code enhancement. But the grim reality in the real world is that sometimes you have to deploy your code on less-then-perfect JVM's (HPUX anyone?) When the code falls over, you want to be sure it's your code, not the enhanced code.

Answers anyone?

Here's a good article on using JDO with legacy database.