This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Originally posted by Simon Lee: Hi David, JDO appears to be targeted as those people who are reacting against EJBs, be it because an EJB implementation is seen as overkill, or simply because of the learning curve. If this is the case do you think that coders will adopt an 'Arts & Crafts' reaction? i.e. handcrafting DAO's rather than adopting (another) xml based persistence layer? Simon
The kind of transparent persistence technology in JDO has existed since the mid-1980s in C++. JDO has the sole purpose of providing transparent persistence for Java object models. It was not developed as a reaction to EJB. We started JDO in 1999, based on earlier Java persistence efforts in the ODMG, long before EJB existed.