On 9/25/06, Gerald Müllan <[EMAIL PROTECTED]> wrote:
Shale supports a similar pattern if your session-scoped beans extend AbstractSessionBean. The passivate() method will be called when the bean is about to be swapped out (perhaps to be transferred to another server) so you can release references to resources that cannot be serialized. Later, the activate() method is called once the bean is re-created. This is where you would go look up the appropriate Spring beans again, and recreate them.
JSF does implement the Hollywood Principle ("don't call us, we'll call you"), but it does so only once :-).
Craig
Maybe there are also other solutions. We did it and it works very fine
in combination
with t:saveState.
Shale supports a similar pattern if your session-scoped beans extend AbstractSessionBean. The passivate() method will be called when the bean is about to be swapped out (perhaps to be transferred to another server) so you can release references to resources that cannot be serialized. Later, the activate() method is called once the bean is re-created. This is where you would go look up the appropriate Spring beans again, and recreate them.
JSF does implement the Hollywood Principle ("don't call us, we'll call you"), but it does so only once :-).
Craig
