Stores exactly one flow execution per conversation, where each
continuation represents the current state of an active conversation.
It is important to note use of this repository does not allow for
duplicate submission in conjunction with browser navigational buttons (such
as the back button). Specifically, if you attempt to "go back" and resubmit,
the continuation id stored on the page in your browser history will not
match the continuation id of the FlowExecutionEntry object and access
to the conversation will be disallowed. This is because the
continuationId changes on each request to consistently prevent
the possibility of duplicate submission.
This repository is specifically designed to be 'simple': incurring minimal
resources and overhead, as only one FlowExecution is stored per
user conversation. This repository implementation should only be used
when you do not have to support browser navigational button use, e.g. you
lock down the browser and require that all navigational events to be routed
explicitly through Spring Web Flow.
It is important to note use of this repository does not allow for duplicate submission in conjunction with browser navigational buttons (such as the back button). Specifically, if you attempt to "go back" and resubmit, the continuation id stored on the page in your browser history will not match the continuation id of the FlowExecutionEntry object and access to the conversation will be disallowed. This is because the
continuationIdchanges on each request to consistently prevent the possibility of duplicate submission.This repository is specifically designed to be 'simple': incurring minimal resources and overhead, as only one FlowExecution is stored per user conversation. This repository implementation should only be used when you do not have to support browser navigational button use, e.g. you lock down the browser and require that all navigational events to be routed explicitly through Spring Web Flow.