[prev in list] [next in list] [prev in thread] [next in thread] 

List:       myfaces-dev
Subject:    [jira] [Resolved] (MYFACES-4045) Review Faces Flow reentrant condition
From:       "Leonardo Uribe (JIRA)" <dev () myfaces ! apache ! org>
Date:       2016-05-13 22:39:12
Message-ID: JIRA.12968183.1463027077000.188471.1463179152883 () Atlassian ! JIRA
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/MYFACES-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Leonardo Uribe resolved MYFACES-4045.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.2.11

> 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
> Fix For: 2.2.11
> 
> 
> 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)


[prev in list] [next in list] [prev in thread] [next in thread]