This week's book giveaways are in the Refactoring and Agile forums. We're giving away four copies each of Re-engineering Legacy Software and Docker in Action and have the authors on-line! See this thread and this one for details.
EJB spec 2.0 on page 79 says "If a client invokes a session object whose session bean instance has been passivated, the container will activate the instance. To activate the session bean instance, the container restores the instance�s state from secondary storage and issues ejbActivate on it."
1. What happens when client calls remove on a passivated session bean? Does the container activates the bean and then calls ejbRemove on it or it just removes the bean without activating it and calling ejbRemove?
2. Also, is it true as mentioned in HEAD First EJB that when client calls remove on passivated entity beans, they are first activated and then ejbRemove is called.