Changes to web flow action proposal

[Marvin S. Addison]

> Using scope="prototype" enables the first option without making much
> impact on how Web Flow works. It just creates a lot of objects and they
> get GC'd instead of creating one and reusing it for every flow request.

I think the use of prototype is the killer feature here. For little 
expense it achieves a natural style that allows you to use instance 
variables for communicating internally; the context tree is still 
available to communicate between components. I think the use of 
pre/postExecute methods may provide for clearer actions, but that seems 
orthogonal to the use of prototype beans.

M