Webflow Style Conventions

[Marvin Addison]

> My plan for the adaptor class is to have it just mechanically:
>
> - populate Spring and Servlet context children
> - call execute() on a POJO
> - catch any exceptions and translate to Events using some algorithm we
> define
> - look for an EventContext afterward with String or Event typed content
> and return a webflow Event

Interesting. I can see the benefit for the CLI use case, but I can
imagine it may be awkward to configure the EventContext in the flow
XML. I'm eager to see how this would look in terms of configuration.
If it works out to be natural and allows expressive flows, then you've
got a gem.

I have noted that there are two fairly different classes of flow actions:

- The action performs a fair bit of logic that determines one of
possibly multiple outcome events.
- Simple action state that produces a single result, where the only
natural outcome is "proceed" (or perhaps also an "error" event if an
exception is thrown).

I've found that the latter maps much more naturally to a simple bean
invocation using Spring EL. It keeps with your goal of removing SWF
dependencies on core components and it has a natural style in terms of
flow XML. Perhaps there's room in the conventions for both styles.

M