I don't know if there is a hard and fast rule about how the server implements entity beans or not, but I think that entity beans typically will access the database a lot, if not after every call. Entity beans must keep the database in sync with their internal state so that non-EJB processes can see up to date information if they query the same database.
Many people feel that entity beans are not very efficient for this very reason. When I attended last year's Java One conference I was surprised by how much anti-entity bean sentiment I saw. A lot of it was coming from Sun's own engineers. Obviously there are lots of people who like entity beans. I use them in some cases but when I want more direct control I will often do the database access directly from a session bean or from a local object accessed by the session bean. You lose some transaction management niceties this way but that doesn't always matter. Jeff Dingle wrote: >do entity beans call the db everytime you call methods on them? > > ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
