Hi,
As far as I understood the issue, an automated mapping to *.xhtml shall
take place if nothing is configured within the web.xml?
And only if the user explicitly wants to disable this new feature, then
he shall add the context param?
Thus, the user needs to add
<context-param>
<param-name>javax.faces.DISABLE_FACESSERVLET_TO_XHTML</param-name>
<param-value>true</param-name>
</context-param>
with a value of true.
The default is false, which does not disable the new feature.
On the other hand
<context-param>
<param-name>javax.faces.ENABLE_FACESSERVLET_TO_XHTML</param-name>
<param-value>true</param-name>
</context-param>
looks like a new feature which has to be active enabled by the user.
This is not true, if the default is true.
Thus, I vote to disable the new feature if not needed.
I assume, most user define a mapping, thus this new context param is
only rarely needed.
Herzliche Grüße - Best Regards,
Michael Müller
Brühl, Germany
blog.mueller-bruehl.de <
http://blog.mueller-bruehl.de/>
it-rezension.de <
http://it-rezension.de/>
@muellermi
Read my books
"Web Development with Java and JSF":
https://leanpub.com/jsf
"Java Lambdas and Parallel Streams":
http://www.apress.com/de/book/9781484224861
"Visitors" a photographic image book:
https://leanpub.com/visitors
On 12/29/2016 07:53 PM, Neil Griffin wrote:
> Dear Friends of JSF,
>
> I recently added a comment to the following issue but Arjan thought that the EG mailing list was a better place for discussion:
> https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-1434
>
> The context-param name and default value for issue 1434 are as follows:
>
> <context-param>
> <param-name>javax.faces.DISABLE_FACESSERVLET_TO_XHTML</param-name>
> <param-value>false</param-name>
> </context-param>
>
> But rather than a double negative, would any of you prefer the following name and default value?
>
> <context-param>
> <param-name>javax.faces.ENABLE_FACESSERVLET_TO_XHTML</param-name>
> <param-value>true</param-name>
> </context-param>
>
>
> Best Regards to all,
>
> Neil
>
>