You make some points. But I nevertheless use a Dao layer, here’s why: Database accesses are calls to a remote system. In all such cases (also web-service, ajax etc…), the granularity of interaction need to be big enough. Many tiny calls would kill performance. This performance necessity requires often a different view of the system, … Read more
Some notes: JDO and JPA are both specifications, not implementations. The idea is you can swap JPA implementations, if you restrict your code to use standard JPA only. (Ditto for JDO.) Hibernate can be used as one such implementation of JPA. However, Hibernate provides a native API, with features above and beyond that of JPA. … Read more
Answers are directly available on documentation I realize it can help make my DAOs work with a plain JDO PersistenceManagerFactory. Yes. TransactionAwarePersistenceManagerFactoryProxy proxy allows DAOs to work with a plain JDO PersistenceManagerFactory reference, while still participating in Spring’s (or a J2EE server’s) resource and transaction management. You can surely use it in your app. But … Read more