Domain « DAO « JPA Q&A

  1. JPA Q&A
  2. DAO
  3. Domain




1. dao or domain model    forum.hibernate.org

Hi I am trying to get my feet wet with OR mapping coming from a background of using straight sql. Most people on this forum seem to suggest using hibernate with the DAO pattern. here's an excerpt from core j2ee patterns "when there is little or no business logic in a business operation applications will typically let clients access business data ...

2. Hibernate, DAOs, Domain model...    forum.hibernate.org

Hello. I'm currently evaluating Hibernate as a replacement of Entity beans in EJB-based applications, and I'm quite pleased with it. I have some architecture questions, though. Hibernate has the same advantage as entity beans: it offers a way to deal with a persistent domain model. Once a POJO is loaded, Hibernate will do everything needed to load the ...

3. Strong Domain Model and DAO amortization    forum.hibernate.org

We make use of a very strong domain layer. By strong I mean we it incorporates both data, persisted via Hibernate, and behavior (or business logic). We use the DAO pattern and abstract factory strategy to determine what DAO implementation we are using at runtime. Until recently the Domain objects new nothing of the DAOs. The reason for this is that ...