Advantages Discussed DAO Data Access Object J2EE Design Patterns Example

\| Interview Questions on Java \|	\| Coding Tips on Java \|	\| Your Questions on Java \|	\| EJB \|	\| Servlet and JSP \|	\| Hibernate Tutorial \|	\| Spring Tutorials \|	\| Java Design Patterns \|	\| J2EE Design Patterns \|	\| Apache ANT \|
\| Apache DBCP \|	\| Struts Struts 2 Example Tutorial \|	\| Apache Beehive JdbcControl \|	\| Apache Log4j \|	\| Apache Axis \|	\| Open Source Project Ideas \|	\| Web Technology \|	\| J2EE Technology \|	\| Java News \|	\| Spring Hibernate Example \|
\| JavaScript Tips \|

Struts Tutorials: Struts2 Tag CheckBoxList
, Checkbox, Iterator, IF Struts2 Tag Library Example Struts2 Tiles Example Struts2 Tiles I18N Example Struts2 Questions Struts Tiles I18N Example Struts Eclipse MVC Struts2 Tags Struts2 Example and Tutorial Struts MVC Struts2 Validation
Hibernate Tutorials: Hibernate Case Study Class Hierarchy Persist Example Using Hibernate Interceptor Hibernate Questions with Answer Hibernate Many-to-Many Mapping Example Hibernate one-to-many Mapping Example Hibernate and ORM tools Spring Hibernate Example Hibernate SessionFactory Example Hibernate Mapping Class Hierarchy Hibernate Questions Hibernate SessionFactory Questions Spring Hibernate Example: Spring Hibernate Case Study

Tags/Keywords : Advantages-Discussed - DAO-Data-Access-Object - J2EE-Design-Patterns Example
Author : ISHTEK
Date (Year/Month/Date): 2009-05-26 Advantages or Benefits of Data Access Object J2EE Design Pattern What are the benefits or advantages of Data Access Object (DAO) J2EE Design Pattern ? Data access, be it database, or webservices or LDAP, JMS, RMI, or anything else, requires ways to de-couple business layer from database access. I think, 1. Data Access Object (DAO) Design Pattern can de-couple data access related code like java.sql package api, webservices apis etc from business/client layer/code. 2. Data Access Object (DAO) Design Pattern can be stateless for concurrency and scalable system. 3. Data Access Object (DAO) Design Pattern can encapsulate datastore related exception handling from client / caller code. 4. Data Access Object (DAO) Design Pattern can be easy to mock up data access for early in developement, and unit testing to happen. 5. Data Access Object (DAO) Design Pattern can provide simple to use abstraction to the data acess API. These are my own understanding only, If you are interested in adding or contracting any of these, you are most welcome to do so just by writing or commenting on this Page.

Terms of Use and Disclaimer : This web site provides some of the information about various technologies, example code, tips, tutorials etc. Like any printed materials, content of these pages may become out of date over a period of time. Therefore all visitor/users of this web site are requested/advised to refer to the originating parties/sources for the latest changes and happenings for detailed information. This information is not intended to be a substitute for the original reference provided by the originating parties/sources. By accessing and using this website in any ways, including, without limitation, browsing the website pages, using any information, using any content and/or downloading any materials, you agree to and are bound by the terms of use described in this page and Usage Terms and Conditions. If you do not agree to all of the terms and conditions contained in the terms of use described in this page and Usage Terms and Conditions, do not use this website in any manner. If you are using the website on behalf of your employer, you represent that you are authorized to accept these Terms of Use on your employer's behalf. All Trademarks are property of their respective owner. Appropriate measure is being taken for providing accurate and up-to-date information but like any printed materials, these blog(s)/contents may eventually be outdated one day, so if you are using any of these information, please refer original content/documentation from respective sources. And under no circumstances shall the Author of these contents and/or this web site be liable for any loss, damage, expense incurred or suffered which is claimed to have occurred because of usage of the contents of this web site. If you have any questions/queries/feedback/suggestions then please write to this web site owner at contact.