[ 
https://issues.apache.org/jira/browse/MYFACES-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14381609#comment-14381609
 ] 

Chris Kulinski commented on MYFACES-3967:
-----------------------------------------

Thanks!  We confirmed that ViewScoped beans are now correctly restored in 
static structure views. 

> View Pooling - ViewScope missing for Static Structure Views
> -----------------------------------------------------------
>
>                 Key: MYFACES-3967
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3967
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 2.2.0, 2.2.7
>            Reporter: Chris Kulinski
>            Assignee: Leonardo Uribe
>            Priority: Minor
>             Fix For: 2.2.8
>
>
> See myfaces-users thread on the topic. 
> http://markmail.org/thread/3enmbvaf47cm2zdn 
> We needed to disable view pooling for certain views because we noticed issues 
> with "static structure" views when using ViewScope.  Our ViewScope beans are 
> available in our controller code, but are no longer available during the 
> RenderResponse phase in our xhtml pages - via expression language lookups.    
>  
>    - On the very first request to the view (before its placed in the pool), 
> the
> state is applied correctly - but then every subsequent request to the pooled
> view doesn't have the correct view state.   
>    - It looks like the view state hasn't been correctly applied on the view
> after its retrieved from the pool.
> Ways we've been able to work around this issue:   
>    - If we disable view pooling for these views, then the beans are correctly
> available in ViewScope.   
>    - We don't see this issue on any of our "dynamic structure" views - in 
> fact,
> if we convert the static structure view to a dynamic structure view (via an
> extra ui:include with EL, etc), then the view state is mapped correctly and 
> the viewscope beans are available.    



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to