<Tr> <Td> </Td> <Td> This section does not cite any sources . Please help improve this section by adding citations to reliable sources . Unsourced material may be challenged and removed . (February 2015) (Learn how and when to remove this template message) </Td> </Tr> <P> The advantage of using data access objects is the relatively simple and rigorous separation between two important parts of an application that can but should not know anything of each other, and which can be expected to evolve frequently and independently . Changing business logic can rely on the same DAO interface, while changes to persistence logic do not affect DAO clients as long as the interface remains correctly implemented . All details of storage are hidden from the rest of the application (see information hiding). Thus, possible changes to the persistence mechanism can be implemented by just modifying one DAO implementation while the rest of the application isn't affected . DAOs act as an intermediary between the application and the database . They move data back and forth between objects and database records . Unit testing the code is facilitated by substituting the DAO with a test double in the test, thereby making the tests non-dependent on the persistence layer . </P> <P> In the non specific context of the Java programming language, Data Access Objects as a design concept can be implemented in a number of ways . This can range from a fairly simple interface that separates the data access parts from the application logic, to frameworks and commercial products . DAO coding paradigms can require some skill . Technologies like Java Persistence API and Enterprise JavaBeans come built into application servers and can be used in applications that use a JavaEE application server . Commercial products like TopLink are available based on Object - relational mapping (ORM). Popular open source ORM products include Doctrine, Hibernate, iBATIS and JPA implementations such as Apache OpenJPA . </P> <P> Potential disadvantages of using DAO include leaky abstraction, code duplication, and abstraction inversion . In particular, the abstraction of the DAO as a regular Java object can hide the high cost of each database access, and can also force developers to trigger multiple database queries to retrieve information that could otherwise be returned in a single operation with normal SQL set operations . If an application requires multiple DAOs, one might find oneself repeating essentially the same create, read, update, and delete code for each DAO . This boiler - plate code may be avoided however, by implementing a generic DAO that handles these common operations . </P>

What is meant by dao class in java
find me the text answering this question