Il 04/12/2014 15:15, Mark Thomas ha scritto:
That we can fix. Indeed, reading section 1.23 of the EL spec we should
fix it. My reading of the spec is that we should always give the
ELResolver a chance to convert this before applying the defaults.
I've raised https://issues.apache.org/bugzilla/s
On 04/12/2014 09:21, mauromol wrote:
> Violeta Georgieva-2 wrote
>> Hi,
>>
>> This is incompatible change in EL 3.0.
>> Check EL 3.0 Spec 1.23.1 and 1.23.2 the Rule for null String is to coerce
>> to "".
>>
>> and
>>
>> A.4 Incompatibilities between EL 3.0 and EL 2.2
>>
>> Regards
>> Violeta
>
> T
Violeta Georgieva-2 wrote
> Hi,
>
> This is incompatible change in EL 3.0.
> Check EL 3.0 Spec 1.23.1 and 1.23.2 the Rule for null String is to coerce
> to "".
>
> and
>
> A.4 Incompatibilities between EL 3.0 and EL 2.2
>
> Regards
> Violeta
This is causing big problems with JSF, indeed. There
f EL3
In other words is there any way to revert to the old behavior using tomcat8 icw
JSF?
-Original Message-
From: Violeta Georgieva [mailto:miles...@gmail.com]
Sent: woensdag 15 oktober 2014 10:57
To: Tomcat Developers List
Subject: Re: Tomcat8 coercing behavior
Hi,
2014-10-15 11:38 G
Hi,
2014-10-15 11:38 GMT+03:00 Koen Serneels :
>
> Hi,
>
>
>
> When binding a JSF input text to a String property of a JSF ManagedBean, I
> want that an empty value is mapped to null and not "" (empty string).
>
> So, on tomcat7 (7.0.56) with JSF(2.2) I can get this to work nicely by
> controlling
