getPrincipals() typing

[Klingenstein, Nate]

> I don't think so, no. Those are in general likely two different flows that are
> themselves subflows and not meant to be run directly at all. You should
> never see that path anywhere in a URL.

I shouldn't, but I can't prevent it.  This is why I asked about entrance points and why those seemingly meaningless checks are meaningful.  I'm very thankful that things bomb out by default, actually.

> Then I'll assume you've read the entire webflow documentation, because
> you're not going to get far without doing that. It also isn't all that long
> actually.

I obviously haven't.  I got through the first ten pages before I glazed over and I resorted to searching.  The Elvis operator had left the building by then.

If you're not a developer -- and I appreciate the inherent irony of me writing that here -- that is one heck of a reference manual.  The example they have makes some of the assumptions that I did, for instance.  It's all "typically", but it's not really bounded in any ways.

http://docs.spring.io/spring-webflow/docs/current/reference/html/defining-flows.html#flow-makeup

> Everything under the ProfileRequestContext object is state. Occasionally
> there's state in the usual Java Session/Request attribute places, and there's
> the StorageService state. Only the latter is persistent across flow executions.

But it could be persisted entirely by the client, and that's an assumption that I need to retain.

> There's some word for whatever just short of that is, and that's what I have. But only for code and other text.

Speaking of irony... (and I didn't notice this on my first read -- someone else here did)

> I have a photographic memory without really having a photographic memory.

It's more of a curse than a blessing, I guess.  I've obviously got my own problems or I wouldn't be here, but that's not amongst them.