Eric D Nielsen on 26/03/08 15:31, wrote:
Adam Hardy on 26/03/08 00:28:43
Eric D Nielsen on 25/03/08 14:29, wrote:
Its a Struts2/Spring2/JPA(Hibernate) based project. I'm using a slightly
modified version of the Generic DAO pattern shown in the Java persistence
with Hibernate book and/or the IBM
Adam Hardy on 26/03/08 00:28:43
>Eric D Nielsen on 25/03/08 14:29, wrote:
>> Its a Struts2/Spring2/JPA(Hibernate) based project. I'm using a slightly
>> modified version of the Generic DAO pattern shown in the Java persistence
>> with Hibernate book and/or the IBM ThoughtWorks very similar example.
The other benefit of the DAO / Manager / Action layers is that you can
use spring to wire up the Manager/Service methods as the transaction
boundaries. Sets of changes you want to all succeed or fail atomically?
Put it in the manager. Managers are where business logic belongs,
DAO's where DB
Eric D Nielsen on 25/03/08 14:29, wrote:
Its a Struts2/Spring2/JPA(Hibernate) based project. I'm using a slightly
modified version of the Generic DAO pattern shown in the Java persistence with
Hibernate book and/or the IBM ThoughtWorks very similar example. (Modified to
allow Spring Based Injecti
Eric D Nielsen wrote:
I'm starting to get some rather stinky code in one of my projects and wanted to
ask for some advice. (
Its a Struts2/Spring2/JPA(Hibernate) based project. I'm using a slightly
modified version of the Generic DAO pattern shown in the Java persistence with
Hibernate book and/
I'm starting to get some rather stinky code in one of my projects and wanted to
ask for some advice. (
Its a Struts2/Spring2/JPA(Hibernate) based project. I'm using a slightly
modified version of the Generic DAO pattern shown in the Java persistence with
Hibernate book and/or the IBM ThoughtWorks
6 matches
Mail list logo
