Hi Manfred,
+1 for the EL expert group fixing this issue.
Ciao Frank
> Am 17.08.2015 um 19:47 schrieb manfred riem <manfred.riem_at_oracle.com>:
>
> Hi Ed, and the rest,
>
> I am of the opinion that EL 3.0 broke backward compatibility and
> it should deliver a fix so pre-3.0 behavior can be re-established.
>
> We should not try to do that in our runtime as javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL
> is already a source of enough confusion.
>
> Thoughts?
>
> Thanks!
>
> Kind regards,
> Manfred Riem
>
>
> On 8/17/15, 12:25 PM, Edward Burns wrote:
>>>>>>> On Mon, 17 Aug 2015 10:08:06 -0500, manfred riem<manfred.riem_at_oracle.com> said:
>> MR> Hi all,
>> MR> I like to propose that we close JAVASERVERFACES_SPEC_PUBLIC-1203 as
>> MR> "Won't fix".
>>
>> MR> The rationale behind this is that the current specification already has
>> MR> a context-param dealing with null handling.
>>
>> MR> Introducing this proposed ELResolver would make the runtime not backward
>> MR> compatible.
>>
>> But what about the reporter's assertion that the
>> javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL parameter is
>> simply not effective in 2.2?
>>
>> Ed
>>