[richfaces-issues] [JBoss JIRA] Reopened: (RF-6620) rich:orderingList does not update model with newly ordered list

[Scott Farley (JIRA)]

     [ https://jira.jboss.org/jira/browse/RF-6620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Farley reopened RF-6620:
------------------------------



I can readily reproduce this issue using the "orderingListDemo" that comes in the "samples" folder of the source code bundle.  It can be seen by changing the order of the items in the list containing, "First, Second, Third, Fourth" (upper right hand section of page.)  If "Second" gets moved to the first position in the list using the "Up" button and then the "Submit" button (further down the page) is pressed the org.richfaces.Bean managed bean "#{bean.simpleItems}" gets updated with the original, un-reordered list.  This was observed by placing a println statement in the Bean.setSimpleItems() method.

> rich:orderingList does not update model with newly ordered list
> ---------------------------------------------------------------
>
>                 Key: RF-6620
>                 URL: https://jira.jboss.org/jira/browse/RF-6620
>             Project: RichFaces
>          Issue Type: Bug
>    Affects Versions: 3.2.1, 3.3.0
>         Environment: RichFaces 3.3.0 GA on JSF 1.2 (SUN RI) with Facelets.
>            Reporter: Scott Farley
>            Assignee: Nick Belaevski
>
> When using <rich:orderingList> on a simple facelets page the the model object is not updated with the newly ordered list.  I can see this work with RichFaces 3.1.3 but NOT 3.2.1 or 3.3.0.  My scenario includes using a JSF managed bean with a value of List<MyDataType> which is referenced in the "value" attribute of the "rich:orderingList" element.  The model setter method does get called on the managed bean when a commandButton fires an action but the model still has the original list.  Also the value changed event is not fired.
> Debugging the code showed that only in version 3.1.3 did the UIOderingList.validate(FacesContext context) method "walk" over the newly submitted values to build a list with the new values.  Version 3.3.0 walks over the original values instead causing the newValue to be the old value but still calls the setSelection() and setActiveItem() allowing them to work correctly.

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