RE: Startup logging question for MyfacesConfig
one possible reason: Your app-config is in faces-config.xml and is placed in /WEB-INF/ AND you have configured the config-file-parm in web.xml to look for /WEB-INF/faces-config.xml The spec says to look for - /META-INF/faces-config.xml in all jar-files in /WEB-INF/lib - /WEB-INF/faces-config.xml - the configured files in web.xml = /WEB-IND/faces-config.xml is processed twice... another possible reason: misconfiguration of you logging... hth Alexander -Original Message- From: Joey Geiger [mailto:[EMAIL PROTECTED] Sent: Thursday, May 11, 2006 5:22 PM To: MyFaces Discussion Subject: Startup logging question for MyfacesConfig I'm wondering why I'm seeing the following things *twice* in my logs when the application starts up. INFO MyfacesConfig - No context init parameter 'org.apache.myfaces.ADD_RESOURCE_CLASS' found, using default value org.apache.myfaces.renderkit.html.util.DefaultAddResource INFO MyfacesConfig - No context init parameter 'org.apache.myfaces.CHECK_EXTENSIONS_FILTER' found, using default value true INFO MyfacesConfig - No context init parameter 'org.apache.myfaces.ADD_RESOURCE_CLASS' found, using default value org.apache.myfaces.renderkit.html.util.DefaultAddResource INFO MyfacesConfig - No context init parameter 'org.apache.myfaces.CHECK_EXTENSIONS_FILTER' found, using default value true
Re: Startup logging question for MyfacesConfig
Thanks for the response. I'm aware of the doubling of the faces-config.xml file and it is only being used once. The error messages I'm seeing only started after I upgraded to myfaces 1.1.3 and tomahawk 1.1.2 releases. I was using the 1.1.3-1.1.2 snapshots from 3/27/06, which didn't give me the same warnings. I will look into the logging as well, but again, I didn't change anything there after upgrading. Jesse Alexander (KSFD 121) wrote: one possible reason: Your app-config is in faces-config.xml and is placed in /WEB-INF/ AND you have configured the config-file-parm in web.xml to look for /WEB-INF/faces-config.xml The spec says to look for - /META-INF/faces-config.xml in all jar-files in /WEB-INF/lib - /WEB-INF/faces-config.xml - the configured files in web.xml = /WEB-IND/faces-config.xml is processed twice... another possible reason: misconfiguration of you logging... hth Alexander -Original Message- From: Joey Geiger [mailto:[EMAIL PROTECTED] Sent: Thursday, May 11, 2006 5:22 PM To: MyFaces Discussion Subject: Startup logging question for MyfacesConfig I'm wondering why I'm seeing the following things *twice* in my logs when the application starts up. INFO MyfacesConfig - No context init parameter 'org.apache.myfaces.ADD_RESOURCE_CLASS' found, using default value org.apache.myfaces.renderkit.html.util.DefaultAddResource INFO MyfacesConfig - No context init parameter 'org.apache.myfaces.CHECK_EXTENSIONS_FILTER' found, using default value true INFO MyfacesConfig - No context init parameter 'org.apache.myfaces.ADD_RESOURCE_CLASS' found, using default value org.apache.myfaces.renderkit.html.util.DefaultAddResource INFO MyfacesConfig - No context init parameter 'org.apache.myfaces.CHECK_EXTENSIONS_FILTER' found, using default value true
Re: Startup logging question for MyfacesConfig
On 5/12/06, Joey Geiger [EMAIL PROTECTED] wrote: Thanks for the response. I'm aware of the doubling of the faces-config.xml file and it is only being used once. The error messages I'm seeing only started after I upgraded to myfaces 1.1.3 and tomahawk 1.1.2 releases. I was using the 1.1.3-1.1.2 snapshots from 3/27/06, which didn't give me the same warnings. Myfaces core parses the config file once as normal. Then Tomahawk parses it a second time (although it's only looking for some fairly simple config options).
Re: Startup logging question for MyfacesConfig
Thanks. I just wanted to make sure the messages weren't a hint of a much larger problem. Mike Kienenberger wrote: On 5/12/06, Joey Geiger [EMAIL PROTECTED] wrote: Thanks for the response. I'm aware of the doubling of the faces-config.xml file and it is only being used once. The error messages I'm seeing only started after I upgraded to myfaces 1.1.3 and tomahawk 1.1.2 releases. I was using the 1.1.3-1.1.2 snapshots from 3/27/06, which didn't give me the same warnings. Myfaces core parses the config file once as normal. Then Tomahawk parses it a second time (although it's only looking for some fairly simple config options).
Re: Startup logging question for MyfacesConfig
On 5/12/06, Joey Geiger [EMAIL PROTECTED] wrote: Thanks. I just wanted to make sure the messages weren't a hint of a much larger problem. No, it's simply the result of needing to access Tomahawk config options even if you're running with JSF RI 1.1, thus MyFaces core and tomahawk both need access to the configuration. And we've added a few more configuration error checks into the system so we can report and detect common configuration issues.
