[
https://issues.apache.org/jira/browse/MYFACES-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665082#action_12665082
]
Felix Becker commented on MYFACES-2134:
---------------------------------------
What the hell?!
@ 1. (Do nothing): Are you serious about that? It's a feature which seems to be
enabled by default. Its implemented in a normal release. So "Do nothing" is
definitly not the right way.
@2. That would be a improvement in trinidad, but that doesn't solve the core
problem in MyFaces.
@3. A message is already logged. Continue processing is the right way i think.
Felix
> 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.
