Interrupting/branching out of web flows

[Cantor, Scott]

I've been playing around a little with implementing some kind of
ExternalAuthn flow and running into the problem that I don't think you can
actually break out of a web flow except by fully rendering a view-state
and then linking to something else (or redirecting client-side) from that
resulting page.

Any time I do anything else, it gets confused, tries to send a response
after the servlet stream is closed, or internally continues the web flow
sequence and bubbles out of the subflow.

The problem we have then is getting profile state communicated to
something outside the view-state from the client end. The V2 handler uses
a request attribute and does a servlet forward, but you can't do that
client-side.

So I'm not sure if this is really implementable. SWF really wants you to
implement your logic with, surprise, SWF.

About all I can think to use is a regular session-scoped attribute in the
container to stash off the ProfileRequestContext so that it can be picked
up after redirecting on the client side.

Happy to hand this off to somebody interested in experimenting.

-- Scott