This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
C. When a session is moved from one JVM to another, any session attribute implmenting the HttpSessionActivationListener interface will be notified.
D. When a session is moved from one JVM to another, attribute values that implement java.io.Serializable will be transferred to the new JVM.
C and D are given as correct answers. Isn't B correct as well? When a session migrates to a different JVM, isn't the attributes going to unbind from the session?
Thanks in advance.
session is needed to be migrated to a different JVM because that JVM need to process a request from same client which the session is attached to. So those attributes bound to the session should be shipped with the session. Isn't it? They can't be unbound from the session. This is what I fell about it... [ December 15, 2008: Message edited by: Vijitha Kumara ]