Client specific session!!
posted 14 years ago
The container assigns an identity to the session bean instance when it is created and that identity is set in the client's remote stub so it comes across with each method call. The container then can look up the right bean instance to use for that call (and activate it if it has been passivated, etc).