[jira] Resolved: (MYFACES-2134) org.apache.myfaces.CONFIG_REFRESH_PERIOD != 0 causes a myfaces failure

["Leonardo Uribe (JIRA)" <de...@myfaces.apache.org>]

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

Leonardo Uribe resolved MYFACES-2134.
-------------------------------------

    Resolution: Fixed

Merged revision 698037 to 743106 from 1.2.x to 2.0 branch

> org.apache.myfaces.CONFIG_REFRESH_PERIOD != 0 causes a myfaces failure
> ----------------------------------------------------------------------
>
>                 Key: MYFACES-2134
>                 URL: https://issues.apache.org/jira/browse/MYFACES-2134
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 1.2.5
>         Environment: Linux, JDK 1.5, Tomcat 6
>            Reporter: Felix Becker
>            Assignee: Leonardo Uribe
>             Fix For: 1.2.7-SNAPSHOT
>
>         Attachments: MYFACES-2134.patch
>
>
> When the context param org.apache.myfaces.CONFIG_REFRESH_PERIOD is != 0 (which seems to be the default) the second page request causes a 
> javax.faces.FacesException: Undefined component type javax.faces.ViewRoot Exception.
> In FacesConfigurator.class method void update()  the method purgeConfiguration() is called. This method throws an NoSuchMethodException. In the catch block for this Exception there is a return; - so the configure(); below isn't called. 
> It looks like RenderKitFactory and / or CoreRenderKitFactory (trinidad) doesn't implement the purgeRenderKit method which is called by reflection from the purgeConfiguration() method - so the Exception rises up.
> Setting the context param org.apache.myfaces.CONFIG_REFRESH_PERIOD to 0 works because the purgeConfiguration() is never called then.
> Regards from Felix @itemis Bonn

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.