design « DAO « JPA Q&A





1. Hibernate DAO    stackoverflow.com

Can anyone suggest me a DAO implementation for a web application? What will be the problem if I create a transaction for fundamental operation (e.g. findByID(), findALL(), creatObject(), deleteObject(), etc.)? Please suggest me ...

2. DAO vs ORM(hibernate) pattern    stackoverflow.com

i read in some articles DAO is not mandatory with hibernate and its implementation is by "it depends", in other words, we can choose between ORM vs DAO pattern. Ok, let's assume ...

3. Generic DAO pattern in Hibernate    stackoverflow.com

While working on hibernate we are following generic Hibernate DAO pattern as mentioned in Hibernate Doc also. So as per this we are currently maintaining two parallel hirarchies 1) for interfaces 2) for Implimentation ...

4. DAO design with Hibernate    forum.hibernate.org

Hi, Im new to Hibernate - and to ORM. In the past I've used the DAO pattern in combination with DTOs to abstract data access. It worked nicely for me, but I hated the feeling that I was loosing an object oriented domain model. So, on my new project, even though my domain model is relatively simple, I've decided to go ...

5. Generic DAO design feedback    forum.hibernate.org

Hello, I have been working on a DAO design focusing primarily in maximizing the quality of the client code (maintainability, portability, etc) and trying to overcome many of the design issues (from the Software Engineering prospective) I found in many other attempts e.g. - Possibility to have a pure JPA DAO base implementation that can be extended to provide non-JPA features ...