Experiments with command-line and web flow adaptor

[Tom Zeller]

> I think we're in general agreement that we'd want an
> opensaml-profile-api module and friends, and that probably this is where
> the non-messaging code from -messaging-api belongs.

Sure.

> In fact, I think
> BaseContext itself belongs there. MessagingContext, et al. are really just
> specific subtypes and classes for messaging that would rely on
> -profile-api.

How about opensaml-context-[api|impl] ? If not, why ? I do not have
strong feelings here, but I have wondered for awhile, so the
conversation is more important than the outcome.

>>I think that WebFlowAdaptor should possibly have the word "Action" in
>>the name, maybe WebFlowActionAdaptor or WebFlowProfileActionAdaptor,
>>to make it clear that it is an Action adaptor.
>
> I left it out because of the standard we had of not putting Action in the
> names, though I suppose this is a special sort of action.

Fine.

> The next step in this area will be to really look at how the
> boilerplate in these actions should work.

Agreed. I consider most of that boilerplate to be hop-scotching nulls
while navigating the context hierarchy. Maybe a useful pattern will
fall out.