myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tamietto Claudio (JIRA)" <myfaces-...@incubator.apache.org>
Subject [jira] Commented: (MYFACES-277) using a button with immediate on a form with a dataTable component
Date Fri, 12 Aug 2005 07:27:55 GMT
    [ http://issues.apache.org/jira/browse/MYFACES-277?page=comments#action_12318594 ] 

Tamietto Claudio commented on MYFACES-277:
------------------------------------------

I have downloaded the night build (2005-11-08) and retested the application and all is functional
.
Are you sure that the patch was reverted ? i haven't added the navigation case suuggested
and the behaviour 
is the same of teh RI

> using a button with immediate on a form with a dataTable component
> ------------------------------------------------------------------
>
>          Key: MYFACES-277
>          URL: http://issues.apache.org/jira/browse/MYFACES-277
>      Project: MyFaces
>         Type: Bug
>     Reporter: Tamietto Claudio
>     Assignee: Mathias Broekelmann
>      Fix For: Nightly Build

>
> i'm using a form that contain a dataTable component . There is also a button that modify
the model of the table with
> an array of only one element with the single fields initialized to "" (String fields)
and has the attribute immediate set
> to true. When the form is rendered after i have pressed the button with the immediate
attribute set  to true ,the value that i obtain is the value submitted and not the value of
the model.
> I have found the following workaround that i have put on a properties of the row of the
table that is called on the rendering phase:
> if (component.getSubmittedValue() != null &&
>     arrayOfRecord[model.getRowIndex()].getCodice() != null &&
>     !component.getSubmittedValue().equals(arrayOfRecord[model.getRowIndex()].getCodice()))
{
>       component.setSubmittedValue(arrayOfRecord[model.getRowIndex()].getCodice());
> }
> I have used the value of the model  and not the component.getValue() because also this
was not the same
> of the value of te model.
> I can try to create a simple case if it is necessary o the problem is not clear.
> The problem seems the same of the issue 187  (that it is closed) but i i have tested
the night builds and nothing
> changed. However in the release notes of the night builds the issue is not reported as
solved.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message