Prashant 1. A DAO is used to do BMP, and is a regular Java class. Instead coding JDBC calls directly in your EJB (find, create, store, remove), you put them in a DAO which you call from your EJB.
2. A DAO can contain multiple SQL statements, including various SELECT, INSERT, UPDATE, DELETE. For a find*() you perform SELECTs; for a create() you perform an INSERT and so on. 3. Sun has published a paper that includes use of DAOs. I think it is one of the J2EE blueprints. HTH I don't have time to be more specific. I hope you get the idea of DAOs, and I hope you can get a hold of the blueprints. James -----Original Message----- From: Prashant Gaikwad [mailto:[EMAIL PROTECTED]] Sent: 28 September 2001 12:17 To: Orion-Interest Subject: DAO design.. Hi, I want to use DAO to access data in design. I have the following doubts and need to understand the concept :- Requirement is that session beans encapsulating business logic needs to access access database through DAO object/objects. 1.) What is DAO object suppose to be ? session/entity bean or a java class 2.) Can I pack multiple SQL select queries in a single DAO class 3.) Any specific design approach for DAO Can I know any links for more information Thanks prashant
