Changes to web flow action proposal

[Cantor, Scott]

On 4/18/13 10:23 AM, "Marvin S. Addison" <marvin.addison at gmail.com> wrote:

>> 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.

It's certainly true that we could orchestrate a pre/exec/post sequence (or
more to the point to the pre/exec part) within the doExecute() method in
the actions. We don't have to expose that on an interface and make it
explicit, but I prefer having the interface impose some commonality on the
action design rather than making it implicit.

-- Scott