Hi,
Lets say you have a *Customer* Class in your problem domain.
And in the Database you have a *Customer Table* where you store information
about Customers.
Now with the DAO Pattern you will have a *CustomerDAO* class where you will
have all Database access related code from the Customer Table. For example
fetching data from Customer table , updating Customer Table etc.(All SQL
queries for Customer Table will come in CustomerDAO class.)
With the help of DAO you access the Database and then collect data in
Customer objects.
Here you can treat Customer class as *DTO* as whatever information for a
Customer is fetched from the Database cal be collected in an Customer
Object.
Regards,
Nirmal :)
\\\///
/ \
| \\ // |
( | (.) (.) |)
----------o00o--(_)--o00o-------------------
Stand up,be bold,be strong.
Take the whole responsibility on
ur own shoulders and know that
U are the creator of ur own destiny.
------ooo0-------------------------------------
( ) 0ooo
\ ( ( )
\_) ) /
(_/
On Fri, Jul 31, 2009 at 11:43 AM, Ashok A V <[email protected]> wrote:
> The DAO(Data Access Objects) is the Java Design Pattern that governs
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/javaprogrammingwithpassion?hl=en
-~----------~----~----~----~------~----~------~--~---
