On Mon, Mar 29, 2010 at 7:57 PM, Martin Marinschek <span dir="ltr"><<a href="mailto:mmarinschek@apache.org">mmarinschek@apache.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi Kito,<br>
<div class="im"><br>
> Actually, it is -- it's related to the end user issue that I ran into, where<br>
> there's a backing bean with a Number of Boolean property associated with an<br>
> input control. I think my workaround is simply to write a PhaseListener to<br>
> do this. It doesn't address the issues you're seeing from a component<br>
> developer's perspective, though.<br>
<br>
</div>I donīt see why. The value-expression for the value-attribute should<br>
be created with type java.lang.Object, and should hence do no<br>
coercion. So you should see no issues for the value-attribute, only<br>
for everything else... I might as well be missing a link here,<br>
however.<br></blockquote><div><br>Hmm... that's not what I'm seeing. Interesting point, though.<br><br>Just to make things more complicated, take a look at this issue: <a href="https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=672">https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=672</a>. Looks like Mojarra handles this the way we'd expect, but only when performing injection on newly created managed beans, so we have inconsistent behavior...<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div class="h5"><br>
best regards,<br>
<br>
Martin<br>
<br>
>> On Mon, Mar 29, 2010 at 9:21 PM, Kito Mann <<a href="mailto:kito.mann@virtua.com">kito.mann@virtua.com</a>> wrote:<br>
>> > I just ran into this while upgrading an application from MyFaces 1.1 to<br>
>> > Mojarra 1.2. In MyFaces 1.1, empty strings were converted to null for<br>
>> > Long<br>
>> > properties in a backing bean. Now, they are converted to 0. I found<br>
>> > several<br>
>> > postings about this issue, culminating in this bug:<br>
>> > <a href="https://jsp-spec-public.dev.java.net/issues/show_bug.cgi?id=183" target="_blank">https://jsp-spec-public.dev.java.net/issues/show_bug.cgi?id=183</a>.<br>
>> ><br>
>> > So, unless I'm missing something, this issue is really the same as<br>
>> > <a href="https://uel.dev.java.net/issues/show_bug.cgi?id=12" target="_blank">https://uel.dev.java.net/issues/show_bug.cgi?id=12</a>. If everyone agrees,<br>
>> > I'll<br>
>> > go ahead and update the description accordingly, since the description<br>
>> > currently mentions Booleans only, not number values.<br>
>> ><br>
>> > Are there any plans to address this issue in 1.2 branches of the<br>
>> > implementations?<br>
>> > ---<br>
>> > Kito D. Mann | twitter: kito99 | Author, JSF in Action<br>
>> > Virtua, Inc. | <a href="http://www.virtua.com" target="_blank">http://www.virtua.com</a> | JSF/Java EE training and<br>
>> > consulting<br>
>> > <a href="http://www.JSFCentral.com" target="_blank">http://www.JSFCentral.com</a> - JavaServer Faces FAQ, news, and info |<br>
>> > twitter:<br>
>> > jsfcentral<br>
>> > +1 203-404-4848 x3<br>
>> ><br>
>> > Sign up for the JSFCentral newsletter:<br>
>> > <a href="http://oi.vresp.com/?fid=ac048d0e17" target="_blank">http://oi.vresp.com/?fid=ac048d0e17</a><br>
>> ><br>
>> ><br>
>> ><br>
>> > On Thu, Mar 4, 2010 at 11:51 AM, Andy Schwartz<br>
>> > <<a href="mailto:andy.schwartz@oracle.com">andy.schwartz@oracle.com</a>><br>
>> > wrote:<br>
>> >><br>
>> >> On 3/4/10 3:01 AM, Martin Marinschek wrote:<br>
>> >>><br>
>> >>> Optionally, we can try to solve this in the new spec-revision of the<br>
>> >>> Unified-EL - for which work is already being started on. That would of<br>
>> >>> course be the easier way out.<br>
>> >>><br>
>> >><br>
>> >> One option might be to allow the JSF implementations to provide this<br>
>> >> functionality in an implementation-specification way (eg. expose a<br>
>> >> context<br>
>> >> parameter) as a short-term solution that can be exposed now independent<br>
>> >> of<br>
>> >> any spec changes. Then, once the new revision of UEL is available<br>
>> >> (which I<br>
>> >> am sure will address this issue), we can pick that up as our standard<br>
>> >> solution.<br>
>> >><br>
>> >> Andy<br>
>> >><br>
>> ><br>
>> ><br>
>><br>
>><br>
>><br>
>> --<br>
>><br>
>> <a href="http://www.irian.at" target="_blank">http://www.irian.at</a><br>
>><br>
>> Your JSF powerhouse -<br>
>> JSF Consulting, Development and<br>
>> Courses in English and German<br>
>><br>
>> Professional Support for Apache MyFaces<br>
><br>
><br>
<br>
<br>
<br>
</div></div>--<br>
<div><div></div><div class="h5"><br>
<a href="http://www.irian.at" target="_blank">http://www.irian.at</a><br>
<br>
Your JSF powerhouse -<br>
JSF Consulting, Development and<br>
Courses in English and German<br>
<br>
Professional Support for Apache MyFaces<br>
</div></div></blockquote></div><br>