Prashant,
The way we implemented DAO was through
general classes. I don't think you need to use EJB's
for that. It works quite well. You can do all the
queries in one class but I suggest that you separate
queries into different classes based on functionality.
In that way your code would be more cleaner and
maintainable.
Hope it helps.
-Sanjeev
--- Prashant Gaikwad <[EMAIL PROTECTED]> wrote:
> Hi,
> Can a data access object be session, entity
> bean or a general class.
> The DAO is suppose to perform database query
> operations on behalf of all the
> other session beans that encapsulate business logic.
> Can I have all the
> query operations in single DAO or should have
> multiple DAO from
> effeciency/performance point of view
>
> Thanks
> Prashant
>
>
===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED]
> and include in the body
> of the message "signoff EJB-INTEREST". For general
> help, send email to
> [EMAIL PROTECTED] and include in the body of the
> message "help".
>
__________________________________________________
Terrorist Attacks on U.S. - How can you help?
Donate cash, emergency relief information
http://dailynews.yahoo.com/fc/US/Emergency_Information/
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
