Bean Passivation

[Rahul JG]

Given that the conversational state of the bean is passivated and the bean evicted from memory to conserve resources, if the client calls a method on the passivated bean instance, how does the container pick up the correct conversational state for the client.
How does the EJBObject help in this, if at all?

[padhu Vinirs]

EJB servers must follow the rules of Java serialization to do passivation. All instance fields must be serializable. There are other objects types that can be passivated.
Here is a list of objects held by the bean that will be passivated ( from a ejb book ):
1. Serializable object
2. Null
3. Reference to ejb's component interface
4. Reference to ejb's home interface
5. Reference to SessionContext
6. Reference to environment-naming context
7. Reference to UserTransaction object
8. Reference to resource manager connection factory
9. Other objects that are not serializable but acquire the ability to be serializable

[Rahul JG]

I think I didn't make myself clear enough.
I just want to know the exact mechanism of how the container is able to track which passivated bean instance belongs to which client.