Depends entirely on the NameService Implementation. In-process implementation *might* swap your object reference temporarily in-memory. Any out-of-process name service implementations will need to serialize your object and pass it on wire. Eventualy, though this object needs to be flushed for a persistent safekeeping. I don't know if this helps you any -harsh- > but I wanted > to know if there is anything in the JNDI spec that would make my code > non-portable. That is when I bind my object to a name in ejbPassivate what > happens the object...are they seriaized and stored on disk or are they kept > 'in memory' > Any ideas?? =========================================================================== 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".
