This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.
No announcement yet.
Support for double submit handling?Page Title Module
AbstractFormController handles the "double submit" problem (in handleRequestInternal) if you are using a "sessionForm" (or an AbstractWizardFormController). Is there similar support in Spring Web Flow with the FormAction?
If a submit triggers a end state to enter when not using continuations, there is no possibility of duplicate submit -- the executing flow will be cleaned up and no longer accessible. So that's a built in feature there.
Now if that isn't the case or you're using continuations, other strategies must be used. The TransactionSynchronizer interface is there to allow you to demarcate application transactions. Right now there is one implementation: a token-based mechanism. See the 'itemList' sample that uses it.