On Mon, Mar 29, 2010 at 9:21 PM, Kito Mann <
kito.mann@virtua.com> wrote:
> I just ran into this while upgrading an application from MyFaces 1.1 to
> Mojarra 1.2. In MyFaces 1.1, empty strings were converted to null for Long
> properties in a backing bean. Now, they are converted to 0. I found several
> postings about this issue, culminating in this bug:
>
https://jsp-spec-public.dev.java.net/issues/show_bug.cgi?id=183.
>
> So, unless I'm missing something, this issue is really the same as
>
https://uel.dev.java.net/issues/show_bug.cgi?id=12. If everyone agrees, I'll
> go ahead and update the description accordingly, since the description
> currently mentions Booleans only, not number values.
>
> Are there any plans to address this issue in 1.2 branches of the
> implementations?
> ---
> Kito D. Mann | twitter: kito99 | Author, JSF in Action
> Virtua, Inc. |
http://www.virtua.com | JSF/Java EE training and consulting
>
http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info | twitter:
> jsfcentral
> +1 203-404-4848 x3
>
> Sign up for the JSFCentral newsletter:
http://oi.vresp.com/?fid=ac048d0e17
>
>
>
> On Thu, Mar 4, 2010 at 11:51 AM, Andy Schwartz <
andy.schwartz@oracle.com>
> wrote:
>>
>> On 3/4/10 3:01 AM, Martin Marinschek wrote:
>>>
>>> Optionally, we can try to solve this in the new spec-revision of the
>>> Unified-EL - for which work is already being started on. That would of
>>> course be the easier way out.
>>>
>>
>> One option might be to allow the JSF implementations to provide this
>> functionality in an implementation-specification way (eg. expose a context
>> parameter) as a short-term solution that can be exposed now independent of
>> any spec changes. Then, once the new revision of UEL is available (which I
>> am sure will address this issue), we can pick that up as our standard
>> solution.
>>
>> Andy
>>
>
>