entity beans should not be used for large amount of data retrieval as it increases the no of beans on the server, and performance is an issue... but only for updates and deletes... its better to use stored procedures for that kind of operation....
regards, uthiresh -----Original Message----- From: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED]]On Behalf Of Milind Kulkarni Sent: Friday, August 30, 2002 7:12 PM To: [EMAIL PROTECTED] Subject: When not to use entity beans HI All, Can anybody explain when one should not use entity beans? I can myself think of 2 reasons: 1. Entity EJB cannot be used in those table which does not have any primary key. 2. Entity EJB cannot be used in those applications where the database can be changed from some other applications as well.In this case the EJB is not in sync with the database. ie. Entity bean will not be refreshed with the changes made in the database by the other application. Are these valid reasons? Are there any other constraints in using entity beans? Regards, Milind =========================================================================== 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". =========================================================================== 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".
