MyFaces context init parameters

[Robert Liguori]

Why am I getting these warnings?

No context init parameter 'org.apache.myfaces.PRETTY_HTML' found, using default value true
No context init parameter 'org.apache.myfaces.ALLOW_JAVASCRIPT' found, using default value true
No context init parameter 'org.apache.myfaces.READONLY_AS_DISABLED_FOR_SELECTS' found, using default value true
No context init parameter 'org.apache.myfaces.RENDER_VIEWSTATE_ID' found, using default value true
No context init parameter 'org.apache.myfaces.STRICT_XHTML_LINKS' found, using default value true
No context init parameter 'org.apache.myfaces.CONFIG_REFRESH_PERIOD' found, using default value 2
No context init parameter 'org.apache.myfaces.DETECT_JAVASCRIPT' found, using default value false
No context init parameter 'org.apache.myfaces.AUTO_SCROLL' found, using default value false
No context init parameter 'org.apache.myfaces.ADD_RESOURCE_CLASS' found, using default value org.apache.myfaces.renderkit.html.util.DefaultAddResource
No context init parameter 'org.apache.myfaces.RESOURCE_VIRTUAL_PATH' found, using default value /faces/myFacesExtensionResource
No context init parameter 'org.apache.myfaces.CHECK_EXTENSIONS_FILTER' found, using default value true

Where is the spec that states I must define them in the web.xml configuration file? And where can I find definitions of each parameter?

Thanks!

[Cameron Wallace McKenzie]

Not to worry. These are just warnings. It's actually good that a record of the fact that default values are being used for these parameters.

I think simply tinkering with the log settings will stop the output of these warnings. I always find that to be the best way to get rid of problems - just don't have the log include any information about them.

These are myfaces context parameters, so the best place to go would be the myfaces documentation. The myfaces wiki might be a good start:
http://wiki.apache.org/myfaces/FAQ

-Cameron McKenzie

[Tim Holloway]

Cameron Wallace McKenzie wrote:
I think simply tinkering with the log settings will stop the output of these warnings. I always find that to be the best way to get rid of problems - just don't have the log include any information about them.

Yeeps! I don't want a look inside your fusebox! The problem with that idea is that if the defaults change, you won't see the changes. And specifically, if options are added or deleted, you won't have a clue in the log when things start acting funny.

I just set the parameters to explicit values in the web.xml file. Then when things change, I'll still have logfile entries telling me about new/removed options and the behavior of existing options will be my own fault.