Hibernate as an example is much easier imho, facade it through and application service that takes only pojos and your done.
--------------------------
Sent from my BlackBerry Wireless Handheld
----- Original Message -----
From: An interest list for Sun Java Center J2EE Pattern Catalog [J2EEPATTERNS-INTEREST@java.sun.com]
Sent: 05/12/2005 12:15 PM
To: J2EEPATTERNS-INTEREST@java.sun.com
Subject: DAO - question about
Hi,
I am thinking about using DAO for our project for doing database calls and transactions. While we implement this pattern , shall I need to use factory pattern ?
I was reading in Core J2Ee patterns :
The DAO pattern can be made highly flexible by adopting the Abstract Factory [GoF] and the Factory Method [GoF] patterns.
Is this a true statement ?
My datasource is Oracle and I will be having couple of DAO classes specific to actions.
Please advice,
Yahoo! Mail Mobile
Take Yahoo! Mail with you! Check email on your mobile phone.
====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@java.sun.com
====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@java.sun.com
