Not sure it helps, but it is the container that MAY serialize the state - not the bean provider. The bean provider should just make sure that all objects representing the state at the point of passivation, should be serializable, i.e. their respective class class should implement the Serializable marker interface.
/Johan 17 jun 2005 kl. 13.01 skrev Karen:
Hi, I have read the EJB 2.1 spec, at 7.4.1 Instance Passivation and Conversational State, it states, "The Bean Provider is required to ensure that the ejbPassivate method leaves the instance fields ready to be serialized by the container. The objects must be one of the following: [A serializable object]" If the bean provider successfully serialized all the Serializable POJOs in my stateful session bean during passivation, will the values in those POJOs be retained during activation? I've been testing all day and I have not been able to get back those values after activation. I've been trying to search for a solution of how to keep the conversational state of the Serializable POJO in the stateful bean and somehow I'm stuck. What I do to get around now is I've changed the cache policy in the standardjboss.xml to NoPassivationCachePolicy. I hope there's someone could advise me of how to get around with this instead of changing the cache policy. Thank you. Regards, Karen ====================================================================== ===== 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".
=========================================================================== 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".
