[richfaces-issues] [JBoss JIRA] Updated: (RF-11060) onselectionchange working incorrect with two extendedDataTable on same page

[Jay Balunas (JIRA)]

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

Jay Balunas updated RF-11060:
-----------------------------

      Fix Version/s: 4.1.0.Milestone2
                         (was: 4.1.0.Final)
    Forum Reference: http://community.jboss.org/thread/167554  (was: http://community.jboss.org/thread/167554)


> onselectionchange working incorrect with two extendedDataTable on same page
> ---------------------------------------------------------------------------
>
>                 Key: RF-11060
>                 URL: https://issues.jboss.org/browse/RF-11060
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects, component-tables
>    Affects Versions: 4.0.0.Final
>         Environment: GlassFish 3.0.1, Firefox
>            Reporter: Tom Giberius
>            Priority: Critical
>             Fix For: 4.1.0.Milestone2
>
>
> If you put two extendedDataTable A en B on the same page then the following goes wrong:
> If you selected record one of Table A en then select record one from table B then the onselectionchange trigger does not fire. The same counts for record two, three, etc. 
> This prevents me for building a Master-Detail data entry screen where both the master and the detail are multirecord. E.g.
> Step 1) Select records one in master and show it details.
> Step 2) Select record three in details, then go back to record 3 of master and then the onselectionchange trigger does not fire. The master tables "thinks" that record three is the selected record while actually it should be record one which was the selected record in the master table.
> The correct behaviour should be that each table should "rember" it selected record. E.g.
> Step 1) Select records one in master and show it details.
> Step 2) Select record three in detail, then go back to record 3 of master and the onselectionchange of the master should fire so that details of master record 3 can be shown. If you would have go back to record one of the master then not firing the onselectionchange would be correct.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira