myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leonardo Uribe (JIRA)" <>
Subject [jira] Updated: (MYFACES-2910) Allow non-String submitted values
Date Mon, 13 Sep 2010 18:42:42 GMT


Leonardo Uribe updated MYFACES-2910:

        Status: Resolved  (was: Patch Available)
    Resolution: Fixed

Yes, I think it is ok to call toString from that method too. Thanks to Martin Kočí for provide
this patch

> Allow non-String submitted values 
> ----------------------------------
>                 Key: MYFACES-2910
>                 URL:
>             Project: MyFaces Core
>          Issue Type: Improvement
>          Components: JSR-314
>    Affects Versions: 2.0.2-SNAPSHOT
>         Environment: myfaces trunk
>            Reporter: Martin Kočí
>            Priority: Minor
>         Attachments: MYFACES-2910.patch
> Myfaces are too strict and always assume submitted value as String. Comparing with Mojarra
and Trinidad:
> 1)org.apache.myfaces.shared.renderkit.RendererUtils.getStringValue(FacesContext, UIComponent):
> myfaces: IllegalArgumentException ("Submitted value of type String expected")
> mojarra, trinidad: call EditableValueHolder.getSubmittedValue().toString() in this situation
> 2) org.apache.myfaces.shared_impl.renderkit.RendererUtils.getConvertedUIOutputValue(FacesContext,
UIOutput, Object)
> myfaces: IllegalArgumentException("Submitted value of type String expected")
> mojarra: CastClassExpection if sumbittedValue is not String
> trinidad: class submittedValue.toString in this situation
> toString() solution will handle all situations and will allow submitted values other
type than String 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message