jsr372-experts@javaserverfaces-spec-public.java.net

[jsr372-experts] Re: [jsr372-experts mirror] Re: Possibly rename javax.faces.DISABLE_FACESSERVLET_TO_XHTML

From: Kito Mann <kito.mann_at_virtua.com>
Date: Wed, 4 Jan 2017 07:30:45 -0500

To be clear, that's a +1 for Michael (i.e. keeping it the same).

On Tue, Jan 3, 2017 at 7:55 AM, Kito Mann <kito.mann_at_virtua.com> wrote:

> +1
>
> ___
>
> Kito D. Mann | @kito99 | Author, JSF in Action
> Web Components, Polymer, JSF, PrimeFaces, Java EE, and Liferay training
> and consulting
> Virtua, Inc. | virtua.tech
> JSFCentral.com | @jsfcentral | knowesis.io
> <http://knowesis.io/web/webcomponents> - fresh Web Components info
> +1 203-998-0403 <(203)%20998-0403>
>
> * See me speak at the Web Components Remote Conference, Feb 16th-17th:
> http://bit.ly/2iX1TeJ <http://bit.ly/LSPK52_Home>
> * Listen to the Enterprise Java Newscast: *http://
> <http://blogs.jsfcentral.com/JSFNewscast/>enterprisejavanews.com
> <http://ww.enterprisejavanews.com>*
>
>
> On Thu, Dec 29, 2016 at 3:15 PM, Bauke Scholtz <balusc_at_gmail.com> wrote:
>
>> +1 to Michael. I said pretty much the same to Arjan before.
>>
>> Cheers, B
>>
>> On Thu, Dec 29, 2016 at 8:22 PM, Michael Müller <
>> michael.mueller_at_mueller-bruehl.de> wrote:
>>
>>> 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
>>> it-rezension.de
>>> @muellermi
>>>
>>>
>>> Read my books
>>> "Web Development with Java and JSF": <https://leanpub.com/jsf>
>>> https://leanpub.com/jsf
>>> "Java Lambdas and Parallel Streams":
>>> <http://www.apress.com/de/book/9781484224861>
>>> http://www.apress.com/de/book/9781484224861
>>> "Visitors" a photographic image book: <https://leanpub.com/visitors>
>>> 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
>>>
>>>
>>>
>>>
>>>
>>
>