Experiments with command-line and web flow adaptor

[Marvin Addison]

> I checked in some preliminary work so we can talk about it Friday or next
> week.

I wanted to provide some feedback on this work before the call today.
While there's nothing wrong with WebFlowAdaptor, you could accomplish
the same invocation with EL:

<action-state id="StaticResolver">
  <evaluate expression="StaticResolverBean.doExecute(conversationScope['org.opensaml.messaging.profile.ProfileRequestContext'])"
/>
  <transition to="OutputAttributes" />
</action-state>

Not as pretty, but it cleans up nicely with a shorter key name for
ProfileRequestContext:

<action-state id="StaticResolver">
  <evaluate expression="StaticResolverBean.doExecute(conversationScope.profileRequestContext)"
/>
  <transition to="OutputAttributes" />
</action-state>

I would argue that's much more natural and even axiomatic for a flow,
and it accomplishes the goal removing SWF dependencies just the same.

I can imagine WebFlowAdapter would have tangible value wrapping an
action that defines multiple outcomes. Note in the case above there's
only one output, so it's safe to assume a transition to
OutputAttributes in all cases.

M