Adena Galinksy wrote: > Also, I have a story and a related question: > The guy who designed our first round of Entity beans put JDBC code in every > set() method which calls a corresponding set-stored procedure in the > database. The ejbStore() method he left blank. His explanation for this was > that Oracle does everything faster and better (he's pretty db focused) He might be very db focused but he is not very db knowledgeable :-) Trust the transaction manager and the database to make a global update, such as one emitted in ejbStore(), as efficient as possible. Making JDBC calls in accessors is guaranteed to defeat all the careful optimizations that have been designed by transaction experts over the past ten years. Not a good sign :-) > He also has no session bean facade to the entity bean, > because he says that just wastes server time This should be substantiated by proof, but for the sake of argument, let's give him that. You are now exposing your underlying DB schema to your presentation layer, and that's usually considered a very bad design. Session beans are very good intermediates to isolate these two layers. >Also, I > heard a lot of arguments for CMP at the course, though since then I seem to > hear a lot of talk floating around to the effect that CMP is terribly slow. CMP is going to go the same way as compilers: it might be possible now for an individual to develop faster BMP implementations, but this is guaranteed not to hold true for much longer as the complexity increases (not even mentioning EJB 2.0 dependents and relationships). I'm fairly confident that the proportion of BMP is going to decrease dramatically over the next years. -- Cedric http://beust.com/cedric =========================================================================== 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".
