Spring Operator

**[Matt Benson](https://jira.spring.io/secure/ViewProfile.jspa?name=mbenson)** commented Will this also include support for Spring Security 3.x (http://forum.springsource.org/showpost.php?p=264465&postcount=7) ? Or should that go into a new issue?

**[Keith Donald](https://jira.spring.io/secure/ViewProfile.jspa?name=kdonald)** commented Yes, and we'll be addressing this in a 2.1 (evolutionary) and 3.0 (next generation) web flow series.

**[Rossen Stoyanchev](https://jira.spring.io/secure/ViewProfile.jspa?name=rstoya05-aop)** commented Removing 2.1 from the target versions as no further work will be done on it for Web Flow 2.1.

**[Erwin Vervaet](https://jira.spring.io/secure/ViewProfile.jspa?name=klr8)** commented I'm not sure about this. Using an on-exception transition seems to be pretty elegant and most people are happy with it.

**[Keith Donald](https://jira.spring.io/secure/ViewProfile.jspa?name=kdonald)** commented Using transition on-exception is no doubt elegant and powerful. However, it's arguably redundant when all you want to do is map the exception to an error message...

**[Keith Donald](https://jira.spring.io/secure/ViewProfile.jspa?name=kdonald)** commented This issue depends on enhancements to the RequestContext to expose an API for recording validation error messages.

**[Nate Margono](https://jira.spring.io/secure/ViewProfile.jspa?name=nmargono)** commented I was able to get past the serialVersionUID by hardcoding the value 507164007291131518 in the FlowExecutionImpl class (adapted from [SPR-4826](https://jira.spring.io/browse/SPR-4826)). But I'm not faced with a serialization...

**[Nate Margono](https://jira.spring.io/secure/ViewProfile.jspa?name=nmargono)** commented Can I get some help on this? It's a blocker for us and it requires us to modify the webflow JAR to get it to work, but...

**[Erwin Vervaet](https://jira.spring.io/secure/ViewProfile.jspa?name=klr8)** commented One problem I see with this is that in a normal SWF config the FlowExecutionRepository bean is not explicitly defined in the application context, so I'm not...

**[Erwin Vervaet](https://jira.spring.io/secure/ViewProfile.jspa?name=klr8)** commented Probably a better option is the make JMX monitoring and manipulation of the ConversationManager possible.