Some app servers permit the deployer to choose the commit option, as discussed in section 9.1.10 of the EJB 1.1 spec. Websphere Application Server 4.0 (WAS 4.0), for example, allows the deployer to choose commit option A, B, or C on an entity bean-by-bean basis. In the case of a shared database, what are good guidelines for choosing between option B (stale entity beans w/ identity) and option C (pooled entity beans)? The WAS 4.0 documentation points out that option C might use less memory. (It seems to me, however, that the app server should be managing the memory and releasing option B entity beans as needed to optimize performance.) If ejbActivate()/ejbPassivate() are expensive operations (e.g., resources are obtained/released and this process is time-consuming), then perhaps option C is better. If ejbActivate()/ejbPassivate() are not expensive operations (say they are no ops), does it matter? Anyone have any guidelines? Laurel =========================================================================== 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".
