Tom Davies said:
No, JDO allows you to specify the mapping between the DB schema and your object model. It is more work,
That work would be necessary for our applications, and for any application that is starting from a fixed schema. If there is a performance or extensibility benefit to JDO over an Entity Bean solution, JDO may still be a better choice, but in our situation, I think that the work required is going to be about the same- you're going to have to do the R to O mapping somewhere.
Further, Tom Davies asked:
What properties of the default mapping which your JDO implementation uses do you see as making the schema inappropriate for use from other languages?
I don't know - I am using Entity Beans right now :)
However, I don't see the database people letting their expertise be replaced by an algorithm written somewhere else.
Thanks for your informative response - I'll watch this carefully and 'embrace change' if it's appropriate.