Fix "embedded" mode to be flow session local.

The "embedded" mode flag, which is used to suppress redirects so
that a flow can be embedded on a surrounding page, was previously
stored as a flow execution attribute. The idea was that a flow can
be launched in embedded mode simply by passing a flow input rather
than having that decision fixed through a static flow definition.

However flow execution attributes are not a suitable place to store
the embedded mode flag since they are globally shared. Instead this
information is now stored a flow session attribute, which means that
each individual session (including subflows) can have be in embedded
mode or not without affecting others
This commit is contained in:
Rossen Stoyanchev
2012-02-28 17:59:57 -05:00
parent df649084ab
commit d616e6bed8
10 changed files with 60 additions and 30 deletions

View File

@@ -7,6 +7,7 @@ Changes in version 2.3.1.RELEASE
Upgrade JSF Mojarra version to 2.1.7
Modify Jsf2FlowFacesContext.isValidationFailed() to check Web Flow's MessageContext for errors
Recognize class-level bean validation messages in BindingResult.getGlobalErrors()
Fix "embedded" mode to be flow session local, i.e. specific to a specific flow or subflow.
Changes in version 2.3.0.RELEASE (Feb 28, 2011)
-----------------------------------------------