[ http://issues.apache.org/jira/browse/MYFACES-428?page=all ]
Sharath Reddy updated MYFACES-428:
----------------------------------
Attachment: inputdate
When an inputDate (or ANY component) is used within a dataTable, the dataTable
creates a single instance of the component. When the dataTable iterates through
its rows, it uses the same instance of the component, only saving/restoring the
submittedValue/value/isValueSet between each row. The inputData was attemping
to cache its value (userData). However, since the same instance of the
component was used for iteration, the cached value was being updated by each
consecutive record, and finally all the rows would have the value assigned to
the last row. Hope this explanation is clear!
> InputDate(s) within dataTable submitting incorrect dates
> --------------------------------------------------------
>
> Key: MYFACES-428
> URL: http://issues.apache.org/jira/browse/MYFACES-428
> Project: MyFaces
> Type: Bug
> Versions: 1.0.9m9
> Environment: JDK 1.4.2_08, win XP, Jetty 5
> Reporter: Colin Chalmers
> Priority: Minor
> Attachments: inputdate
>
> Using InputDate within a dataTable to accept birthDates of clients. The dates
> are rendered correctly on screen afterwhich one may select the individual
> dates. After submitting to server all date objects in the individual customer
> objects are set to the *last* date that was selected.
> A workaround I'm using at the moment is to use inputText fields in
> conjunction with a date pattern which works correctly.
> Using the InputDate out with the datatable to accept (for example) a
> departure date works no problem.
--
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
