Originally posted by Roger Goerke:
This JDO seems a little too good to be true. There must be some price to pay for all the flexibility listed in the requirements.
Is JDO a performance killer? How does JDO get access to the private persistable attributes and how does JDO know that an object is dirty?
Any background info provided will be helpful for me to understand why I might consider using them over EJB.