Back button Jira issue

[Cantor, Scott]

On 1/15/16, 6:39 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:



>Something that popped into my head just now: I believe that the cause of the SWF behavior I'm having the most angst over is that *after a flow completes*, it sees the resumption of a missing flow execution, and actually produces a new execution of the flow, which I find really incomprehensible as a default. I wonder if it's possible to inject a sort of minimally extended version of the built-in session-backed repository for state but have it behave in a special way if it's asked to resume a missing flow.

Turns out this highly suspect behavior is because of the default exception handler inside the Spring MVC FlowHandlerAdapter, the main MVC / SWF crossover. So it seems like what we may have gotten wrong is not overriding that exception handler somehow.

I'll take this finding to the "smaller" issue I opened on the back button for further exploration, but this might be a way to attack this I hadn't realized existed. If nothing else, I know we can subclass the handler adaptor and install our version if we had to.

Guess I know what I'm doing this weekend. Yay.

-- Scott