Hi, > Can anybody explain when one should not use entity beans?
(see end of email) > 1. Entity EJB cannot be used in those table which does not have any primary > key. I dont consider this a valid reason. Where do you not have a primary key? This sounds like a very dangerous situation to me. > 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. not true. Using the appropriate commit option will overcome this problem. > Are these valid reasons? no. > Are there any other constraints in using entity beans? The real constraint is the thread constraint. Avoiding deadlocks is probably the biggest issue I've encountered. This then comes down to the application server and how they implement locking. cheesr dim > > 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".
