Hi, I would suggest you to go for option 2. The main reason for this is Session Bean Methods allows declaring the transaction attributes and security constraints without touching the code. Hence it is easily maintainable
Varad --- Ashwani Kalra <[EMAIL PROTECTED]> wrote: > Hi, > > I am leading a short project which includes simple > inserts, deletes, > updates etc. and printing reports from the > database. > > I have few questions. > > 1. We are not using entity beans because of > performance reasons. But I > want to use session beans . How to convince my PM. > Is there any > reasons that I should use session beans or use DAO > only ie > > 1. Client(jsp)-->Java Beans--->DAO-->Database > 2. CLient(jsp)-->JavaBeans/Business Delegage--> > Session > Bean-->DAO-->Database > > Which option will be better if no of users are > moderate . > > We are using Websphere 4.0, Oracle8i > > TIA > Ashwani > > =========================================================================== > 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". > __________________________________________________ Do you Yahoo!? Yahoo! Web Hosting - Let the expert host your site http://webhosting.yahoo.com =========================================================================== 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".
