You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Val Blant (JIRA)" <de...@myfaces.apache.org> on 2009/02/05 00:29:02 UTC
[jira] Updated: (MYFACES-2134)
org.apache.myfaces.CONFIG_REFRESH_PERIOD != 0 causes a myfaces failure
[ https://issues.apache.org/jira/browse/MYFACES-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Val Blant updated MYFACES-2134:
-------------------------------
Status: Patch Available (was: Open)
> 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
>
> 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.