Experiments with command-line and web flow adaptor

[Tom Zeller]

> Is "ProfileRequestContext" the right name for the
> thing that the actions are presumed to operate on? If so, it seems like
> -profile is appropriate.

Yes, I think so. But I also think we should re-define the word
"profile" in a non-SAML specific way, e.g. Marvin wondered to me
"should I be operating on profiles?" What would that definition be ?

> Maybe this is a place where Optional<FooContext> works. That becomes the
> way to express "could be missing" on the return side, so it's obvious from
> the local variables which contexts are required or not.
>
> FooContext foo = lookup1();
> Optional<BarContext> bar = optlookup2();

Possibly.

The experience I had with the Action boilerplate code was : look for
@Nonnull, check code to make sure it was implemented, decide which to
fix ;-)