[
https://issues.apache.org/jira/browse/MYFACES-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15282931#comment-15282931
]
Leonardo Uribe commented on MYFACES-4045:
-----------------------------------------
I can also confirm that the current flowScope implementations does not support
to have more than one flowScope of the same flow at the same time. So, in the
hypothetical case, when the user exit from A and B, the first flow A does not
contain any previous values.
> Review Faces Flow reentrant condition
> -------------------------------------
>
> Key: MYFACES-4045
> URL: https://issues.apache.org/jira/browse/MYFACES-4045
> Project: MyFaces Core
> Issue Type: Task
> Components: JSR-344
> Reporter: Leonardo Uribe
> Assignee: Leonardo Uribe
>
> Checking some documentation of JSF 2.3, I noticed the following text:
> "... Because Flow instances are immutable, yet the flow stack is per-user,
> implementations must make allowance for flow scoped data (managed beans
> declared to be FlowScoped and data stored in the Map returned by
> getCurrentFlowScope()) to be fully re-entrant. For example, consider an
> application with two flows, A and B, each with a single FlowScoped bean
> MyBeanA and MyBeanB, respectively. Entry into flow A causes MyBeanA to become
> active. Calling from A into B causes MyBeanB to become active. Calling back
> into A causes a new instance of MyBeanA to become active, rather than
> reactivating the earlier instance of MyBeanA. ..."
> I remember this condition was discussed at some point in time, but I'm not
> sure if the current implementation supports that scenario, so it is better to
> take a look at the code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
