Hey guys, I noticed in the EJB 1.1 spec that the container is responsible for preserving the following types across ejbStore/ejbLoad calls: serializable objects primitives references to EJB objects references to home objects I also noticed that the container is responsible for preserving the following types across ejbPassivate/ejbActivate: serializable objects nulls references to EJB objects session contexts environment naming contexts Why are the rules different for these two cases? IMHO the container should be able to passivate, activate, store, and load the following types: primitives serializable objects nulls references to EJB objects references to home objects session contexts entity contexts environment naming contexts If not, then the bean provider needs to do leg work to aid the container, which seems anti-RAD. -Ed _______________________________________________________________ Get Free Email and Do More On The Web. Visit http://www.msn.com =========================================================================== 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".
