You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org> on 2017/02/22 23:31:44 UTC

[jira] [Resolved] (MYFACES-4100) Default view pool is enabled for all views by default when cache mode is alwaysRecompile only

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

Leonardo Uribe resolved MYFACES-4100.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.2.13

> Default view pool is enabled for all views by default when cache mode is alwaysRecompile only
> ---------------------------------------------------------------------------------------------
>
>                 Key: MYFACES-4100
>                 URL: https://issues.apache.org/jira/browse/MYFACES-4100
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 2.2.12
>            Reporter: Leonardo Uribe
>            Assignee: Leonardo Uribe
>             Fix For: 2.2.13
>
>
> There is an small bug in the activation of the default view pool in ViewPoolFactory class.
> When org.apache.myfaces.CACHE_EL_EXPRESSIONS is set to "alwaysRecompile". ViewPool feature is enabled, but the default view pool applies to all views that does not have any view pool mapping in faces-config.xml, but only when oamEnableViewPool is set. 
> What's happening right now is view pool is automatically enabled for all views by default, and this should be changed to the opposite.
> The reason is "alwaysRecompile" is a EL caching feature by itself that does not require the view pool to work, but the view pool only works well when "alwaysRecompile" is set.
> This part is quite confusing, but the fix needs to be done. It was discovered looking for a solution for  MYFACES-4099



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)