On Sun, 23 Nov 2003, Jeremy Boynes wrote:
> This most definitely does *not* support changing the stack on the fly. 
> In Geronimo, the stack is built when the container is started and 
> remains constant until it stops. This avoids the need to synchronize on 
> getNext(), and eliminates the potential for the stack changing part of 
> the way through an invocation.
> 
> I would look at your usecase in Castor _really_ hard and see if you can 
> take the stack offline to do the switch. We will be doing that in 
> Geronimo with versioned containers.

	Couldn't we construct the new stack "next to" the old one, and
then "swap it in" at the beginning of the next invocation?  That way the
old invocation completes against the complete old stack, getNext() has no
problems, etc. but new invocations complete against the complete new
stack.

Aaron