Interrupting/branching out of web flows

[Marvin Addison]

> The problem we have then is getting profile state communicated to
> something outside the view-state from the client end.

I guess I'm so used to flows pausing at view states that I simply
can't imagine what you're trying to do. What exactly are you trying to
communicate with? Another component?

> 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.

If you're just trying to stash state to pick up when the flow resumes,
then that's likely your only option. It's really a non-issue if you
have data that's compatible with flow storage (i.e. serializable);
otherwise you have to invent workarounds like accessing the
HttpSession directly.

> Happy to hand this off to somebody interested in experimenting.

I'd be willing if I understood the use case better.

M